@Robban@donnib Great work on the Deconz component. I’m in the process of moving all my Xiaomi devices over to Deconz. It works great with the motion sensor and door/window sensor. However I’m not able to get the round wireless switches connected to Deconz. In the Phoscon App it is found as sensor but does not show up in the list. Do you by any chance have a solution?
I also made a issue on it on the Deconz Rest plugin Github.
I’m running deconz headless (2.04.99), so have only access to the wireless light webapp, and the Phoscon App.
If they’re switches they get exposed as events in HASS. If they report battery you should have a battery sensors that also keeps the name of the event that the switch will generate. Check the component documentation to get examples of automations using those events.
Thanks for answering. They do not show up in HASS in the event list (also not a battery sensor). The motion and door/window sensor do.
The problem is that I cannot get Deconz to link with the switch in the first place. I don’t think it is a problem with the Deconz component you wrote, but with the Rest plugin of Deconz.
Do you use the webapp wireless light or the Phoscon App for the linking? The Phoscon App does say it found a connection, but afterwards it is not listed in de sensor list.
I’ve been trying all day with no succes.
How would I do that? I’ve been looking in the REST API documentation, and found something about “permitjoin” parameter, but I do not know how to use this
Through Postman I collected my Api and opened the network and reset the button to join it like described in the REST API documentation of Deconz. Then did GET /api/apikey
I can see that my switch is connected to Deconz, and the “lastupdated” parameter changes when I press the button. However it is not visible in the Webapp.
Maybe @donnib has got some advice, as I think I read that he also uses the xiaomi wireless smart home switches (don’t know for sure)