bspranger/xiaomi

my Xiaomi Device Handlers for Smartthings

xiaomi's Issues

Original Xioami Button always pushed IOS

Would you please look at the problem with the Original button where it shows always pushed. It works with the original code on the other thread.

Need to correct most recent version of the non-Aqara button dth

Just missing a " on one line. Please see my pull request.

Temperature Humidity Sensor doesn't have pressure in REST API response

I'm trying to use SmartThings REST API to access Xiaomi Aqara Temperature Humidity Sensor.
But the response does not include pressure.

{
    "components": {
        "main": {
            "relativeHumidityMeasurement": {
                "humidity": {
                    "value": 42,
                    "unit": "%"
                }
            },
            "healthCheck": {
                "checkInterval": {
                    "value": 7320,
                    "unit": "s",
                    "data": {
                        "protocol": "zigbee",
                        "hubHardwareId": "000E"
                    }
                },
                "healthStatus": {
                    "value": null,
                    "data": {}
                },
                "DeviceWatch-DeviceStatus": {
                    "value": null,
                    "data": {}
                }
            },
            "temperatureMeasurement": {
                "temperature": {
                    "value": 19.9,
                    "unit": "C"
                }
            },
            "sensor": {},
            "battery": {
                "battery": {
                    "value": 83,
                    "unit": "%"
                }
            }
        }
    }
}

Would it be possible to add atmospheric pressure to the response?

IDEA: Multiclick on both buttons

Documentation from Zigate implies that both buttons have multiclick - with value of 1 to 4. Maybe we should look at parsing that.

(PS - thanks @veeceeoh for pointing me at these pages - I'd only found a more generic one from this guy before)

Alec

http://zigate.fr/xiaomi-bouton-switch-cluster/

ZiGate <- 01 81 02 00 0E F3 0B C0 E1 01 00 06 80 00 00 20 00 01 02 F0 03

Type: 0x8102 (Attribute Report)
SQN: 0x0B
Src Addr: 0xC0E1
Src Ep: 0x01
Cluster ID: 0x0006 (General: On/Off)
Attribute ID: 0x8000
Attribute Size: 0x0001
Attribute Type: 0x20 (UINT8)
Attribute Data: 0x02
Status: 0x00

0x02 = nombre de clics (max 4)

http://zigate.fr/xiaomi-bouton-switch-aqara-clusters/

Multi clics
ZiGate <- 01 81 02 00 0E E5 06 82 97 01 00 06 80 00 00 20 00 01 03 DE 03

Type: 0x8102 (Attribute Report)
SQN: 0x06
Src Addr: 0x8297
Src Ep: 0x01
Cluster ID: 0x0006 (General: On/Off)
Attribute ID: 0x8000
Attribute Size: 0x0001
Attribute Type: 0x20 (UINT8)
Attribute Data: 0x03
Status: 0x00

0x03 = nombre de clics (max 4)

Aqara Wall Switch QBKG04LM (one button, NO neutral)

Hello, I made some dirty, but functional code for the Aqara Wall Switch QBKG04LM.

Is it possible to check it please? And integrate here?
Im not programmer.
As I know, fingerprint is not ok, but everything is working.
Thank you,
J.
Aqara.txt

Button preferences update - comments?

Hello,

I've already done a pull on this (to @tmleafs) standardisation branch - hope I got it right.

1. On the old button - still had a 'how many seconds is held' preference - as far as I can tell that functionality has been deprecated for now. I removed it until/unless we decide to reinstate it.
   Notice - if you had a previous version and had entered some 'held' value - it still shows down below as a "ghost" in preferences. If you click the little 'x' it disappears.
   (sorry - forgot to take screenshot before it went away)

2. On both buttons, was just seeing "Which?" for the Momentary/Toggle preference. Switched "description" to "title". While I was in there I changed the language to simply "Momentary or toggle? " and I switched the default to "Momentary". I think for the first time user the way it works as a "momentary" push button is more intuitive. Default "toggle" has led me to think it's getting stuck until I realized it was on toggle. Hope that's ok - please push back if you disagree.

Xiaomi Aqara Button

When I press button I am getting this error

12:20:24 PM: error java.lang.ArrayIndexOutOfBoundsException
5cebbeea-07cc-4210-8ee1-07df7d511b20 12:20:24 PM: debug Thing: Parsing 'read attr - raw: DA3C0100120A5500210100, dni: DA3C, endpoint: 01, cluster: 0012, size: 0A, attrId: 0055, encoding: 21, value: 0001'

Can it be due I have new model wxkg12lm?

does not update..

hi there
i sucessfully paired my xiaomi temperature and humidy sensor, it even got 1 reading of temp and humid (altough batt level is stated as 0)

after 1 hour i have no more reading. is there anyway to force readings?
how can i fix it?
thanks

Temp sensor showing as unavailable

Temp sensor status shows as unavailable, but the temp, humidity and battery are all displayed correctly.

Using the Aqara Temperature sensor. Its been working okay for a long time, this behaviour started only recently.

782fecac-2d5d-4196-ba8c-a574e450541e 11:01:40 AM: debug Temperature Sensor: Parse returned [name:battery, value:100, unit:%, isStateChange:true, descriptionText:Temperature Sensor Battery at 100% (3.025 Volts)] 782fecac-2d5d-4196-ba8c-a574e450541e 11:01:40 AM: debug SmartShield(clusterId: 0x0000, command: 0x0a, data: [0x01, 0xff, 0x42, 0x25, 0x01, 0x21, 0xd1, 0x0b, 0x04, 0x21, 0xa8, 0x43, 0x05, 0x21, 0x05, 0x00, 0x06, 0x24, 0x01, 0x00, 0x00, 0x00, 0x00, 0x64, 0x29, 0xf4, 0x07, 0x65, 0x21, 0x34, 0x1d, 0x66, 0x2b, 0x39, 0x88, 0x01, 0x00, 0x0a, 0x21, 0x00, 0x00], destinationEndpoint: 0x01, direction: 0x01, isClusterSpecific: false, isManufacturerSpecific: false, manufacturerId: 0x0000, messageType: 0x00, number: null, options: 0x0100, profileId: 0x0104, senderShortId: 0x7ded, sourceEndpoint: 0x01, text: null) 782fecac-2d5d-4196-ba8c-a574e450541e 11:01:40 AM: debug Temperature Sensor: Parsing description: catchall: 0104 0000 01 01 0100 00 7DED 00 00 0000 0A 01 01FF42250121D10B0421A84305210500062401000000006429F4076521341D662B398801000A210000

Aquara Motion sensors strange behavior

I bought two Motion sensors connect them to SmartThings using handler.
First one works ok, (however it seems it reports more frequent than 60 seconds)

Second one reports only illuminance but not motion event as soon as it connected. After couple of minutes of illuminance it stops to send events at all. it reports only when I click the button.

What are the chances that second sensor is not configured properly? I have not connected one of them (do not remember which) to the Xiaomi hub. Does Hub send configuration on first connect?

xiaomi zigbee outlet

hi
could you please add the option to keep the plug on after electricity failure (keep the state as before the failure) as can be done with the xiaomi gateway?
thank you very much
Yoni

Idea: Humidity Background Colors

A while ago I made myself a Humidity prioritized version of @4refillpad s Temp/Humidity sensor - and came up with these background colors for humidity based on ASHRAE Standard 62-2001 "Ventilation for Acceptable Indoor Air Quality"

https://buildingscience.com/documents/reports/rr-0203-relative-humidity/view14

        backgroundColors:[
			[value: 0, color: "#FFFCDF"],
			[value: 4, color: "#FDF789"],
			[value: 20, color: "#A5CF63"],
			[value: 23, color: "#6FBD7F"],
			[value: 56, color: "#4CA98C"],
			[value: 59, color: "#0072BB"],
			[value: 76, color: "#085396"]                                    
		]

I'd like to update the 2 x 2 tile beneath temperature to use these color values. And, if we manage to get to where we can pick what is shown in the main - I'd like to use these values for that.

The 2 x 2 tile would look like this (the one in the center below the temp - and btw it's 80 degrees in temp because I just breathed on my sensor :-) ). I'm not too thrilled about the font size versus the icon, but whatever - doesn't seem to be any other way to get color and an icon - correct me if I'm wrong - and we really need the icon.

Here are most of the colors (I used simulator to preview)

Thoughts? I'll do a pull request if people agree.

Idea - background color values for lux/ illuminance measurement

Hello all,

Didn't find a "standard" per se - but found this chart floating around for CCTV ratings in lux that made basic sense to me

I roughly based myself on it, given that the xiaomi only does integers, etc etc

Here's the colors I went with

Here's some screen shots (using last "published" Xiaomi Aqara DTH - before all the current open pulls)

This is in my living room on the mantlepiece - there's a sconce above the sensor - daytime - cloudy day

• Holding my thumb over sensor - still let in a bit of light

• Normal light - it's a darkish room and the sconces are not that bright
  

Shining my flashlight into the sensor

I have a value for full daylight too - I took it outside and it only went to 1000 - on the other hand it's pretty cloudy here. Has anyone gotten values above 1000 on this?

if not, then I could maybe switch the brightest yellow down to 1000.

Thanks!

PS Here's the current code I'm using - in case anyone wants to test before I do a pull...

valueTile("illuminance", "device.illuminance", decoration:"flat", inactiveLabel: false, width: 2, height: 2) {
state "default", label:'${currentValue} \nlux', unit:"lux",
backgroundColors:[
[value:0, color:"#000000"],
[value:10, color:"#52523A"],
[value:100, color:"#A3A22E"],
[value:1000, color:"#CFD43C"],
[value:10000, color:"#F5F433"]
]

DH version

Not sure if we could pull it off but I am so tempted to try and place a version in the DH so when ppl submit an issue they can refer to the version of DH they are using and a screenshot would automatically capture the version..

Issue: 510% humidity report

I am using the humidity reports for a custom Smart Home Monitor rule. When Humidity goes under 40% or over 60%.

Only the last couple of days I got multiple 510% reports. Everytime it's the same extreme high value: '510'. SmartThings can also report 51% als a correct value.

Event report
description | Bedroom Sensor Humidity is 510%
name | humidity
rawDescription | humidity: 51%
translatable | false
unit | %
value | 510

Xiaomi Aqara Temperature Doesnt Show Connected in Smartthings App (not classic)

Smarthub V3 (US edition)
2 x Xiaomi Aqara Temperature Humidity Sensors
Androind Smartthings App latest version

Right so on to the issue. I added the correct device handler and after a night of mucking around got the 2 sensors finally installed by forcing the hub to look for a different sensor - no probs there and the data being reported back to the hub is correctly.

However, when it comes to clicking on the device in the app all I get is “Cannot connect to device. Check device and try again.”

I know from watching logs that the sensors are working like a charm in terms of reporting and according the IDE are connected to the hub, hwoever the one difference I have seen is that “Execution Location” is set to cloud. Dont know if that matters.

Thanks in advance.
Jared

Minor UI Issue on Iphone - Temp (and Humidity) Offset + or - - cant write +

I started testing the updated version of the Temp/ Humidity sensors
There's a small UI issue with both the temperature and the humidity offset preferences at least on iPhone. The keyboard that comes up has a little + and - at top and the numbers under it. All cool. But you can't actually type a +3 the plus key is inactive. You can, however, type a '-' sign. Unless someone knows a way to 'activate' the plus key - I suggest we change the instructions to say '3' or '-3' rather than '+3' or '-3'.

Plus does nothing - doesn't type a +

Minus actually changes the value to a negative and put in '-' character

Just got a new Xiaomi Aqara Button with mode id: lumi.sensor_switch.aq3

This is what I get, the current DH do not work properly, just let me know if you need some testing.

8:42:07: debug Thing: Parse returned [name:Model, value:lumi.sensor_switch.aq3, unit:%, isStateChange:true, descriptionText:device model, displayed:true, linkText:Thing]

8:42:07: debug Thing: Parse returned [name:battery, value:100, unit:%, isStateChange:true, descriptionText:Thing Battery at 100% (3.055 Volts), displayed:true, linkText:Thing]

8:42:07: debug Thing: [name:battery, value:100, unit:%, isStateChange:true, descriptionText:Thing Battery at 100% (3.055 Volts)]

8:42:07: debug cluster: 0000, attrId: 0005, value: 6C756D692E73656E736F725F7377697463682E61713301FF42260121EF0B0328230421A8130521620006240100030000082102010A2100009821080099210000, model:6C756D692E73656E736F725F7377697463682E617133, data:42260121EF0B0328230421A8130521620006240100030000082102010A2100009821080099210000

8:42:07: debug Thing: Parsing 'read attr - raw: B73F01000088050042166C756D692E73656E736F725F7377697463682E61713301FF42260121EF0B0328230421A8130521620006240100030000082102010A2100009821080099210000, dni: B73F, endpoint: 01, cluster: 0000, size: 88, attrId: 0005, encoding: 42, value: 6C756D692E73656E736F725F7377697463682E61713301FF42260121EF0B0328230421A8130521620006240100030000082102010A2100009821080099210000'

Thanks for the great work.

Hub timezone not set results in DTHs not working at all

Just opening this as an official issue, even though we're all well aware of it.

It looks like one or maybe two users just today were at their wits' end with frustration over their ST mobile app not displaying their sensor's reported values correctly or not at all - and it turns out their hub's timezone wasn't set yet.

So there must be some way, as @bspranger has attempted to code, to check whether the timezone setting is null and if it is, use a default timezone to avoid all the null errors that make the device handler not work correctly.

Reference to community page

I think it would be a good idea to add a link in the comments at top of all the DHs to the reference the Community thread + Git Source (not everybody has the linked code).

Next time Samsung do a major update and break everything it may help people get to the right place quicker.

Im assuming that an actual clickable link in the preference is not possible (I've not checked).

Minor issue - Xiaomi original temp humidity reporting unformatted lastCheckinDate

Hello,

If you take a look at reports from the current Xiaomi original temp humidity you're getting

If I'm correct - "lastCheckinDate" doesn't need to be there anymore.

Is that right ?

Alec

Motion reset has no effect

A user has an issue with the motion reset. Sounds like we need to change the parameter that is being used in the DH.

README.md

Good idea to rewrite the README.md. Add more information, screenshots optional and new url.

Idea: Automatic identification of Test/Normal Mode in Xiaomi Aqara Motion Sensors

Yesterday I was exploring something which I wasn't able to get too far on before I had to leave the house.

There is a cluster which as far as I can tell , after the sensor has been paired, is always and only sent when the reset button is pressed - cluster 0000, attrib 0005 which gives the model (see bolded below). As we've identified - initial pairing and resetting sends the sensor into test mode - during which time it responds to motion every 5-6 seconds instead of the default 60.

I've only tested after pairing - but I have a hunch it would also be shown at initial pairing (or there would be another way to identify pairing).

This is already parsed out by the existing DTH.

Thinking it could be a tile that automatically indicates Test Mode this cluster is reported - sets a 2 hour timer, then resets to normal.

Thoughts? Anyone else have other experiences w/ this cluster?

Alec

d5b99a48-1ec2-4624-b142-435eac76f60a 2:09:20 PM: debug Bathroom Door Motion Sensor III reported: cluster: 0000, attrId: 0005, model:lumi.sensor_motion.aq2
d5b99a48-1ec2-4624-b142-435eac76f60a 2:09:20 PM: debug Bathroom Door Motion Sensor III parsing: read attr - raw: 9CD401000034050042166C756D692E73656E736F725F6D6F74696F6E2E617132, dni: 9CD4, endpoint: 01, cluster: 0000, size: 34, attrId: 0005, encoding: 42, value: 6C756D692E73656E736F725F6D6F74696F6E2E617132

Aqara devices disconnecting after a few minutes/hours

Hi,

I am about to give up on these. Have Aqara square switch, small button, temp, vibration, motion sensors.
They pair and then a few hours later they are gone and don't show up again unless reset. Reading the forum thread I dont seem to be the only one.

Any chance of fixing that ?

Im using Hub v2, US customer Rev E fw: 000.022.00014

thanks

Humidity offset

Add humidity offset to temp humidity sensors.

Xiaomi Aqara Temperature Humidity Sensor - Humidity offset not working

Hi,
The humidityOffset is not working in the device handler "Xiaomi Aqara Temperature Humidity Sensor"

The problem is that the offset variable "humidityOffset" is not referred to in the device handler is not linked to the value that you entered in the preference input. I did a quick test replacing the humidityOffset variable in the Parse function with the humidOffset variable from the preference input and the humidity value was corrected.

input "humidOffset", "number", title:"Humidity Offset", description:"Adjust humidity by this many percent", range: ".."

else if (map.name == "humidity") {
if (humidityOffset) {
map.value = (int) map.value + (int) humidityOffset
}

This code in the Parse function will solve the problem:

} else if (map.name == "humidity") {
	def humidityOffset = humidOffset ? humidOffset : 0
	if (humidityOffset) {
		map.value = (int) map.value + (int) humidityOffset
	}
	updateMinMaxHumidity(map.value)

Minor - suggested change to Battery message in Recently

I think that for consistency we should change 'recently' message for battery reporting from

descriptionText : "${device.displayName} is at ${roundedPct}% (${rawVolts} Volts)"

to

descriptionText : "${device.displayName} Battery at ${roundedPct}% (${rawVolts} Volts)"

since:

• we always indicate the variable on all the other recently messages
• there's another field w/ percent (e.g., humidity) - I know volts would seem to rule that out but it's still a bit confusing if you see my first example below
• battery icon doesn't show on iOS recently (which is why we put in the volts)

that would change it from

to

on iOS (don't have Android to test - not quite as relevant since apparently the icon does show there - but even so there should be consistency)

Thoughts?

Alec

Enhancement Suggestion : Pressure change

Would it be possible to add a further status label to the pressure showing if the pressure is Rising, Falling or Static when compared to the previous reading, or maybe to change the icon to show Rising, Falling or Static?

Potential Issue - Battery Changed changing on its own - Xiaomi Temperature/Humidity

So - I re-paired my old Xiaomi Temperature/Humidity - was set up with DTH current as of yesterday early afternoon (Eastern Standard Time).

As expected - Battery Changed Date was yesterday - Jan 26th.

This morning I noticed in the IDE that the Battery Changed Date was showing as today. I hadn't even been in the app. Looking at logs it looks like battery changed date changed to today with the first battery report of the day at 2:34 am . (I promise I wasn't up in my app at the time :-) )

I have updated my DTHs to yesterday's version - will also pair my single Aquara Temp/Humidity (square version).

Will check them both overnight and see if they update themselves again and will report in in the morning.

Variant of Xiaomi Temperature Humidity Sensor not supported?

I installed the two custom device handlers "Xiaomi Aqara Temperature Humidity Sensor" and "Xiaomi Temperature Humidity Sensor" from this repo, but I still can't get my sensor detected as something other than "Thing" (I have a sensor that looks exactly like the circular "Xiaomi Temperature Humidity Sensor" on the frontpage of this repo).

Here's my "raw description" from the IDE:

01 0104 5F01 01 05 0000 0003 0019 FFFF 0012 07 0000 0004 0003 0005 0019 FFFF 0012

Unfortunately I don't understand enough of this to "fix" the device handler myself. Is the above sufficient for you to (try to) add support for this device? Is there anything I can do to help with that?

Can't save current version. Extra } line 224

Tried updating this guy via the repo and get an error 500. Manually pasting it in the ST IDE yields and error. I got it to save by removing the extra close curly bracket on line 224.

I'm pretty new to github, not sure if an issue was the proper thing to do, but..

Xiaomi/devicetypes/bspranger/xiaomi-temperature-humidity-sensor.src/xiaomi-temperature-humidity-sensor.groovy

Line 224 in 48848b7

}

Icons - Battery Android Vs. iphone

Weird or non display of icons from certain https and how they render differently on ios and android

Idea: Alexa Smartthings skill temperature reporting

Currently, I can ask Alexa to tell me the current temperature reading on my thermostat device via the Smartthings Alexa skill. But it won't work on the temperature sensor. I'm wondering if this might be possible if the temp sensor DTH emulates the characterstics of a thermostat so that the ST Alexa skill will interact with it.

configureReporting - not supported by Xiaomi devices?

I have been doing a bunch of reading and research on what is the appropriate code to use for configuring attribute reporting time intervals. What I found should be used is:

zigbee.configureReporting(cluster, attribute, dataType, minReportTime, maxReportTime, minReqValueChange)

Most of the "official" supported ZigBee device handlers in the SmartThingsPublic repository use configureReporting to set up battery reporting, but it's been well established that Xiaomi devices use a very non-standard method for reporting battery voltage, so I tried making code to set up configureReporting for each devices

However, based on my own tests and testing of code by joelw135 and GSzabados that I came up with for the Original Xiaomi Temp / Humidity sensor, it appears that configureReporting commands are ignored.

I did some Googling, and found a discussion thread here on GitHub by some users of deCONZ (a graphic user interface-based ZigBee monitoring & control software solution) trying to use Xiaomi devices.

In the thread, one user posted this about reporting of attributes by Xiaomi devices:

It looks like the sensor is smart enough to send multiple reports once it's awake (unlike the Hue motion sensor, which uses separate scheduling for presence, lightlevel and temperature. I see no pattern in the timing, indeed, it would seem it only sends reports once a threshold for change has been crossed. Note that at 9:07, only the temperature is sent - I assume bacause there was no change in humidity.

Normally, this would be configured through the ZigBee attribute reporting configuration

This seem to be hard-coded in the sensor (and, in fact in all Xiaomi devices I've seen) - they don't support reading not writing the attribute reporting configuration.

So, this appears to confirm what we've been seeing - the Xiaomi devices will ignore configureReporting() commands (and also ignore readAttribute() commands as well), and they will send attribute reports at intervals according to Xiaomi's design.

If that's true, then there's no way we can help reduce the level of reporting for any users that are seeing their battery level drop rapidly.

If everyone agrees that configureReporting commands are ignored, then the code for the refresh() and configure() functions of all devices should be the same as what Brian has recently updated to for many of the DTHs:

def refresh(){
    log.debug "${device.displayName}: refreshing"
    checkIntervalEvent("refresh");
}

def configure() {
    log.debug "${device.displayName}: configuring"
    state.battery = 0
    checkIntervalEvent("configure");
}

def installed() {
    state.battery = 0
    checkIntervalEvent("installed");
}

def updated() {
    checkIntervalEvent("updated");
}

private checkIntervalEvent(text) {
    // Device wakes up every 1 hours, this interval allows us to miss one wakeup notification before marking offline
    log.debug "${device.displayName}: Configured health checkInterval when ${text}()"
    sendEvent(name: "checkInterval", value: 2 * 60 * 60 + 2 * 60, displayed: false, data: [protocol: "zigbee", hubHardwareId: device.hub.hardwareID])
}

Xiaomi Aqara wall single switch

Can’t get it work tryout any DH in here
Attached picture of my switch type

Xiaomi Aqara Vibration Sensor - tiltAngle inconsistent

I have this on my overhead garage door. The tiltAngle in the open or closed position isn't consistent. It will always be within 1-2 degrees. For example, at closed it will report it as either 99 or 98, and at the open position it reports as 101 or 102. I suspect there is some logic in the rounding function that can be adjusted?

Swap Lastcheckin and lastevent (Motion/press/open etc)

Doing so means the the recently tab will look complete (My OCD is kicking in) as we can add the heart beat icon

tileAttribute("device.lastCheckin", key: "SECONDARY_CONTROL") { attributeState("default", label:'Last Update: ${currentValue}',icon: "st.Health & Wellness.health9") }

Example of DH will look like

Current Recently Tab looks like

What it will look like with the change

What's preferred way to update fork?

This is a question to you more experienced Githubbers. I'm currently only using the web version though ok w/ getting into the command line if absolutely necessary. I just did a pull request to update a single line in one DTH and noticed that it was also "committing" the pulls I did a couple of times to bring my fork up to date w/ Brian's. Does that matter? It looks kind of messy.

What's preferred process to keep things clean when I want to update my fork? What I've read on the command-line stuff (rebasing and all) seems fairly tedious. Should I just delete my fork and refork? Does that cause other problems?

Thanks!

Facebook user reporting -436% battery

User posted this on one of the facebook groups im on

Says he gets it once or so per day

Add held back to original button

With people moaning the held option is still missing lets work together on trying to fix this.
Before we start I dont understand how any one finds the original DH's held option reliable enough.
it just didn't work either it didn't register the hold and do the push or do both or every so often it would work.

To make this work you cant send the push till after you receive the the released we can then work out the time between the push and the released and do the required action

so we get the pushtime and releasedtime when they happen

heldtime = releasedtime - heldtime

if(heldtime >= userdefinedtime){
//event = held
}
else
{
//event = push
}

I'm getting the following error on def heldTime = releasedTime - pushedTime

groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.lang.Long#minus. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number] @line 286 (parseCustomMessage)

Enhancement Suggestion: Info / Debug message display preference settings

Inspired by Hubitat's native device drivers, I'd like to suggest adding preference setting toggles for info and/or debug log message display.

I have already built code for this in my updated round "Original" Xiaomi button DTH currently being beta tested (Pull Request #110). Here are what they look like in the device preferences page:

I set up the defaults at pairing for only info log messages to be displayed, and when the debug log toggle is also set, it's easy to see which kinds of messages are being displayed:

If people think this would be a welcome enhancement, then I could do a Pull Request on all the other DTHs so people can try it out.

Fire Detector won't trigger Smart Home Monitor

I tried out the Fire Detector today (thanks for the DTH!), and I discovered something strange. It works perfectly and triggers "SMOKE" on the device status page, but it doesn't seems to trigger Smart Home Monitor. I have the alarm set up for smoke detection (obviously), but neither the app nor any of the triggers reacted.

When I changed to the old beta DTH (https://github.com/inpier/inpier-devicetypes/blob/master/devicetypes/kennethevers/xiaomi-honeywell-smoke-detector.src/xiaomi-honeywell-smoke-detector.groovy), SHM worked as intended and triggered both warning in the app and my actions.

I don't know if SHM needs a special trigger in the code?

"double-click" in Xiaomi Zigbee Button

Hi @bspranger
is there any chance to easy implement missing "double-click" action in original Xiaomi Zigbee Button?

double click catchall: 0104 0006 01 01 0100 00 5D4F 00 00 0000 0A 01 00802002

Both Temp/Humidity sensor DTHs not updating mobile app display??

On the [RELEASE] Xiaomi Sensors and Button (beta) thread on ST Community Forums, two users are reporting that when using bspranger/Xiaomi DTHs with their Temp/Humidity sensors, the ST mobile app does not display any values for anything, like this:

User @cowboysdude has "original" Xiaomi Temp/Humidity sensors, and user @Busybeee is working with an Aqara Temp/Humidity sensor, and they are both reporting the same problem. So it seems there may be an issue with both Temp/Humidity sensor DTHs.

Both of them say they can see the temp / humidity reports in the "events" log (I'm not sure which log they are referring to - so I will ask). This tells me that their devices are paired okay, but for some reason the tiles are not being updated with the latest reported values.

It's really difficult to troubleshoot this for me because I don't have either of the Temp/Humidity sensors so I can't confirm the problem with the mobile app not displaying any values (like in the above screen shot.)

I would recommend reading through posts from the past two days in that thread to get a sense of what they're experiencing.

New BETA for Xiaomi Aqara Vibration sensor

I have uploaded the code for an initial beta release of a SmartThings device handler for the new Xiaomi Aqara Vibration Sensor (Model DJT11LM).

The new code can be viewed here.

I do not yet own an Aqara Vibration Sensor, so it is completely untested and needs beta testing by users who do own one. Please know that it will very likely generate errors in your log, and also not all planned features are implemented.

The initial features are as follows:
• Vibration / Movement detections will generate a Motion - Active event
• When the sensor is tilted, an Acceleration - Active event is generated
• When the sensor is dropped, a Button 1 - pushed event is generated
• The above three event types will be displayed as "Vibration Detected", "Tilt Detected", and "Drop Detected" in the main tile for the sensor in the SmartThings mobile app. If no other events occur within 61 seconds, the display will clear out with a grey background, meaning the sensor is motionless.
• When the sensor is tilted, if the value of tilt angle change is reported, this will be displayed in the mobile app, and also in the events list and in live logging. It is not yet associated with any SmartThings capability so it cannot be used by any SmartApps other than WebCoRE.
• After the sensor has moved, if a 3-axis value is reported, it will generate a Three-Axis event. The X, Y, Z values are the raw values given by the sensor in the range of -2048 to +2047. This feature needs more development to make it useful.
• After vibration events, if the sensor reports the "level" of vibration, it will be displayed in small text at the bottom of the main tile for the sensor in the mobile app, as well as in the events list and in live logging. It is given as the raw reported value on a scale of 0-512.
• The time/date of the most recent vibration, tilt, and drop events are displayed in smaller GUI tiles for the sensor in the mobile app
• As with other bspranger/Xiaomi device handlers, the battery voltage and % level are reported and its replacement date is stored and displayed in a GUI tile for the sensor in the mobile app.
• Preference Settings are similar to those in other bspranger/Xiaomi device handlers, but also include toggles for informational ("info") and debug log messages to be displayed in the Live Logging page of the IDE.

Any and all comments, suggestions, and bug reports are highly encouraged in order to improve this device handler and its functionality.

I'm tagging @oltman on this as he has also been working on device handler code. Hope you can take a look and see what may be improved, especially with regards to the 3-Axis Accelerometer data. Keep in mind I don't own one of these yet, so everything has been coded without any testing at all. Please go easy on me! :)

Idea: Highest/Lowest temperature of today

Idea: To implement in the maintile of the temperature sensor the highest and lowest temperature of the current day?

Heads Up: Display Issues on iPhone app - both custom and standard DTHs

You're all probably aware of it - per thread at https://community.smartthings.com/t/ios-2-14-0-released-1-30-18/117246/83 it looks like rendering is off on both standard and custom DTHs on iPhone

Here's what our most up-to-date Xiaomi Aqara Motion Sensor is looking like on my iPhone this morning - note the weird icon before "Last Updated" - how off the value tiles look -

This is what my Iris Motion Sensor - using completely standard DTH is looking like - even worse!

Suggest we hold off on any image "reconciliation" between Android and iPhone until this gets straightened out...

Aqura - Firmware

Hi, probably a stupid question but... How do I know what firmware my device is using?

Thanks very much,

Mark

Xiaomi mijia Honeywell Fire Alarm Detector (circa 20€)

I'm going to ordered one of these:
https://www.gearbest.com/alarm-systems/pp_615081.html

There is an existing DH:
https://community.smartthings.com/t/release-beta-xiaomi-honeywell-zigbee-smoke-detector/94790

Looks like they already got the important fonctionnalité... but the thread never had a big audience so full potential never reached.

It's probaby not complaint with our insurance (not CE or american equiv so keep a stupid one near by)... but i'd rather have this in the house and send me a text if im not in than the stupid one alert nobody and burn my property to the ground... as with xiaomi its hella lot cheaper than nest so, one in garage, lounge etc. Anyway i think this would be a good addition to your growing xiaomi DH family.

GB normally takes like a month to deliver stuff to me so, i'll maybe have a bit more to say in a while.

Have any of you got one of these already... thoughts impressions?