Domoticz

btw, can I make new devices not being set to used by default ?

If I remove the devices and turn z2m hw off and on they will be auto populated again.
In this case I don't care that much of the device ID as it's easy to change the script

Okey.... So.... the 'switch' is probably from the old Zigbee config? As this is persistent in your MQTT broker, you need to remove it manually with (for example) MQTT Explorer
That means, if you can control everything, and see the correct status for the *_identify_* that is

gizmocuz wrote: ↑Friday 06 June 2025 10:37 Okey.... So.... the 'switch' is probably from the old Zigbee config? As this is persistent in your MQTT broker, you need to remove it manually with (for example) MQTT Explorer
That means, if you can control everything, and see the correct status for the *_identify_* that is

I didn't copy the MQTT broker db when I reinstalled.
Something is strange.

MQTT


Domoticz settings ( removed the IP adress.


z2M settings

This is the device we have been talking about Bokhylla

Just use MQTT Explorer and in the search box enter the big hex number 0x..... then you should see them
One of them is probably old data... or you get multiple devices from this node and then it's OK

Easy fix

- shutdown zigbee2mqtt (docker compose down)
- remove all config entries in the homeassistant topic for this device
- enable zigbee2mqtt (docker compose up)

Now you will see if you get a switch/sensor/select/button etc... If you do.. these are all part of this node
If this means multiple devices that are send to domoticz, fine.. use the one that works for you, hide the other ($ character in front of the name, or just don't add it)

if I just keep set the _identify_ devices to unused I'm going to be fine. I think it's something new that z2m expose to MQTT/Domoticz.
It's confusing as they get named the same in domoticz. On it set to Button on device and the other a on/off device.