Doudz component has progressed far more than mine and I would recommand anyone who would like to have an “up to date” zigate support to switch to his (https://community.home-assistant.io/t/another-component-for-zigate/). While I don’t use it personnaly, the response from the community seems nice and Doudz is prompt to support new versions.
That does not mean I’ll abandon zigate which is a fantastic tool, but I’ll focus in the future on a version purely based on MQTT with a simple daemon, easier to debug (I’m no fan of automatic component detection) and probably outside HA which is far too rich for my very simple needs. Thanks to all people who supported and helped through this small adventure. The code is still opensource and linked below if anyone wants to reuse parts of it
I started the implementation of a component for the ZiGate (http://zigate.fr/)
Awesome, I just tried it and it work well. The ZiGate is successfully initialized and I successfully see the capture message from my Xiaomi Button (already paired with the ZiGate prior to this test).
As a reminder for people passing here, ZiGate is a Zigbee gateway with an impressive compatibility, it already works well with device from:
Xiaomi
Ikea
Hue
Pluzzy
Orvibo
Innr
Osram
Trust
Jiawen
Heiman
It was started and sold through a Kickstarter campaign and the gateway is now also available here: https://zigate.fr/produit/zigate-ttl/ (all in French for now…)
yep
There is still a lot of work to do. In the current code I misinterpret the use of component / platform and need to rewrite it a significant part of it (hopefully, the code was light )
I still need to find the best way to cope with the diversity of switches & sensors it can manage … hopefully, I am motivated !
The management of all the device type will have to be implemented one by one I’m afraid, since each vendor have it’s own interpretation/use of the protocol.
Once the base framework is in place, I’ll be able to help and implement the different device type/brand.
I hadn’t try, as I thought my device would have to be handled as a binary_sensor or similar since it never really stays on or off and cannot be controlled by hass (unlike a switch).
I tried with the configuration you provided, the sensor is initialized, I see it in hass, and it goes ON when I press the button.
However it never goes OFF again. Only the first press fire an event.
That could be half the solution, another thing is that the pressed/release event are always reported together by zigate. Even when I hold the button down.
I should at least see the switch as off while pressing it but the status doesn’t change.
I’ll see that more in detail tonight
OK, so the switch seems to be a momentary one, which would explain how the double click is available
It behaves differently than the presence detector I tested which fires only a “on” event
Not a complex problem, I just need to confirm I guessed right :
Could you try a double click and send me the log ?
ZiGate is sold with usb serial or usb-serial + wifi during the kickstarter campaign
As far as I see on the website, it is for the time being only sold with usb serial
Btw, wifi is not yet implemented in the python library
The double click doesn’t seems to send anything different.
What I however noticed is that both the Press and Release are reported at the time. When I release the button.
The log entry from custom_components.zigate.interface only appear once I release the button. It seems like hass doesn’t process the first part, which is the press.
Single_click.xml (2.1 KB)
(it’s a log, had to change the extension to xml to be able to upload it here)