Yes, but since I don't own one, I've been waiting for a Hubitat owner who can help test a device driver.
I guess I should get started on that soon...
Yes, but since I don't own one, I've been waiting for a Hubitat owner who can help test a device driver.
I guess I should get started on that soon...
I thought about getting one but Iām a little leery to buy devices before I know theyāre supported, after getting burned a few times (Xiaomi yee light strip still orphaned, more or less)
For any Xiaomi Zigbee devices, if there's a device handler to support them on SmartThings, then a device driver can be made for Hubitat. Personally I'll only buy a device if it would be useful to me, not just for testing a device driver. In fact I just received a couple of the new revision of the Aqara Button (model WXKG12LM), and have updated the SmartThings DH (currently being tested), and will be updating the Aqara Button device driver for Hubitat very soon.
As you're well aware, Xiaomi's Yee Light / Yee Light Strip is WiFi-based, and as such is a very different monster to support than any of their Zigbee devices.
Yeah, because I was unsure about smartthings when I started getting smart devices so I got a few different wifi/ethernet based things: Yeelight, Nanoleaf, and Sinopeās hub thermostats, and of course Caseta.
I do have yeelight strip control sort ofā¦ itās just TV backlight, so Iām running tasker, sharptools and yeelight app on my ShieldTV, so when tasker detects screen on it turns on the yeelight locally through the app. Iām hoping sharptools gets Hubitat connectivity as well.
I think I can help with that, just as soon as I have time to start moving devices overā¦
[RELEASE] v0.5 of Xiaomi Aqara Button Device Driver
Now compatible with both models - WXKG11LM & WXKG12LM
Originally created by @brianspranger
For convenience please copy the driver code from this direct link.
This release adds support for the new revision of the Aqara Button, model WXKG12LM. This new model takes away the triple- and quadruple-click functions, but adds hardware-based hold support, and also sends a unique message when the button is shaken. Note that if the button is mounted to a surface, thereās no way to get the shake function to work (unless you can shake the whole surface!)
Below are charts of what happens with each type of action, for both models:
Aqara Button model WXKG12LM
Action | Hubitat button event(s) |
---|---|
Single click | button 1 pushed
|
Hold, release | button 1 held , then button 0 pushed when released |
Double-click | button 2 pushed
|
Shake | button 3 pushed
|
Aqara Button model WXKG11LM
Action | Hubitat button event(s) |
---|---|
Single click | button 1 pushed , then button 0 pushed after user-set delay |
Double-click | button 2 pushed
|
Triple-click | button 3 pushed
|
Quadruple-click | button 4 pushed
|
Hold | Not supported (same behavior as single-click) |
Other Features:
batteryLastReplaced
statebutton 0
āreleasedā eventinfo
rmational and/or debug
log messagesChanges from previous version
new Date()
date/time stamplastPressedDate
because it doesnāt serve any real purpose on HubitatlastPressed
to buttonPressed
event, for webCoRE usebuttonHeld
and buttonReleased
events for webCoRE useNote: This device driver is not final, and some features or preferences may be added / removed
Can they be paired to ST and Hubitat at the same time?
Have you had any luck with the xiaomi cube? The ST DH seemed to port over easily enough. The cube was discovered immediately by the hub. When I change the face of the cube, the device state changes properly. However, I canāt figure out how to do anything with it. I couldnāt figure out how to get RM to do anything with it and havenāt had a lot of luck with webcore and Hubitat playing nice to see if it works with webcore.
You have to create custom commands first, I believe.
I see how you can create a custom command. The connection Iām missing is how to use that custom command to trigger an event. I know how to trigger a custom command but not vice versa.
Incompatibilities with RM are because of the difference between ST's button capability implementation and Hubitat's.
If you got webCoRE working on your Hubitat that would work in the interim because it would still "see" the button events from the ST device handler.
I have been working on updating the currently released Xiaomi device handlers for ST and device drivers for Habitat. After that, I plan on working on the Hubitat device driver for the Mi Cube.
No Zigbee or Z-Wave devices can be paired to more than one hub at the same time.
If you want to pair your Xiaomi devices with you Hubitat hub, you should be able to make them available for your SmartThings hub to "see" using @krlaframboise's Other Hub SmartThings Integration app.
Iām working on getting webcore integrated for that specific issue and guessed that was my best option to complete the integration. But the webcore dashboard has been very glitchy for me, which is a whole diff ball of wax on a diff thread, as you knowā¦ I was hoping there was a solution with button controller or RM. I was pleasantly surprised at how easy it was to get as far as I did with the cube and will keep plugging away at getting webcore working.
I have put up an early beta of the Hubitat device driver for the Xiaomi Mi Cube on my GitHub repository.
You can grab the code from here.
It should now register different actions as button presses in RM or other Hubitat Apps, but I have not tested it at all.
Things I still need to figure out include dealing with the Three Axis functionality (apparently not implemented on Hubitat) and also whether the additional data
posted in button pushed
is being handled correctly for the device driver to use.
Let me know if it works at all for you!
Thank you. Both the DH and webcore are working!
Button WXKG01LM isnt implemented yet right?
I only have the two-button model, WXKG02LM.
However, the driver for that should also work for the one button model, but it will just work as a single button of course, sending a button 1 pushed
event.
Can you try it to check and let me know if it works?
The code can be copied from here.
It seems to work but itās sending 2 times that itās been pushed. Even if i try to push it as quick as i can.
2018-04-08 10:36:17.660:infoButton Triggered
2018-04-08 10:36:17.612:infoButton: Button pushed 1
2018-04-08 10:36:17.407:infoButton Triggered
2018-04-08 10:36:17.369:infoButton: Button pushed 1
Also wondering how i subscribe to the event on your buttons.
I used to use this:
subscribe(Button, ābutton.pushedā, ButtonPushedEventHandler)
But dont think you use that one, any idea what i need to use to subscribe to a pushablebutton?
Details regarding Hubitat's Button Implementation can be found here...