Has anyone managed to get a Xiaomi remote working with Deconz? I’ve got the remote registered using Phoscon and its appearing in HA (battery sensor showing only).
I’ve setup an automation to recognise a trigger event;
I’ve been able to fire the event using the developer tool: Events, so I know the automation works, but I haven’t been able to identify the event number correctly (I think). Has anyone any experience of this and how to identify the event?
Thanks for the response, I’d not looked at that before. When I use it, nothing shows, so I used to to observe other events and they show, so I I’m wondering if it’s the deconz add-on that is not recognising the events of the switch. I can see it’s passing the battery level through the sensor (which is what it’s supposed to do), but not it seems the button press, unless there is something else I’ve not done.
As a belt and braces check i looked at the logs in the deconz add-on and can see the button press activity, it just doesn’t seem to be firing an event.
Already done, afraid it didn’t make any difference either. I’ve also checked that the conbee stick is at the latest firmware level. HA is at 0.92.1, so I’m up to date all round.
@Holdestmade I think it’s more fundamental than the automation. I’ve been able to trigger the automation by calling the service, which tells me that the automation will be triggered when the event is recognised by HA. I’ve just updated to 92.2, just in case. I think the next thing for me to try is to remove the add-on and start from a clean slate. I’ve already tried removing the integration and re-initialising that so I think I need to get my setup as clean as possible and re-start from there.
I’ve had a play with the listen activity for events and no activities under deconz_event fire. That concerns me, hence my thought of removing the add-on and re-stalling.
I had the same problem when i searched for xiaomi or ikea switches. Then i changed from deconz to zha and that didnt help. I still only get the battery status
What’s the problem with the switches? They appear with the “battery_level” in the integration but you have to use dconz_events in your automations. So your automation should look like this:
@dnuc no, that aspect is fully understood. The issue is that the deconz_event is not presented under the events tab on the developer menu. I’ve tried removing and re-installing the add-on and that hasn’t helped it re-appear (it has existed in the past, when it was first installed). For the devices the battery level is present which shows that they are recognised. I have not been able to get the deconz_event recognised whilst it is not present in the events tab.
I’ve just got myself a conbee II, so I think I’m going to strip out the add-on and then re-add from first principles, It’ll take a while but worth it if it solves the issue.