I have quite a few HUE and Zigbee switches/lights exposed in HA using the Zigbee2MQTT broker, all working fine.
I have purchased a HUE tap dial switch and Zigbee has picked this up. But unfortunately it has exposed this a ‘update’ type and not a ‘switch’. I assume this means the switch is due a firmware update (maybe?) but zigbee2mqtt doesn’t find any OTA.
Any idea what I can do with this? Without it as a ‘switch’ I cannot expose it to HomeKit using the plugin.
Thanks
HA only provides updates for mfgr’s that will put the file onto HA’s servers. I’m told this is for security reasons, so that NC controls what they send to your instance.
I suspect that is the problem. I don’t have any firsthand knowledge if that is the issue here or not though.
Perhaps bug Hue to do this…
The more of their customers that request this, the more likely it would happen.
I wouldn’t hold my breath, though. This doesn’t help Hue buy more yachts…
Battery devices like the Tap Dial do not expose switches. They send zigbee events. In Z2M, these were historically exposed as action entities to show these events in the device states.
With Z2M 2.0 and greater, these action entities have been removed in favour of zigbee events. You can bring them back by enabling “Home Assistant legacy action sensors”, but bear in mind that this is considered a legacy action and can be deprecated in the future.
This is a screenshot of my Tap Dial with all legacy sensors enabled - you will notice that none of them are actual switches (they revert to Unknown right after a press):
