Domoticz

But is there data inside?

waltervl wrote: ↑Friday 09 February 2024 9:51 But is there data inside?

Yes, the data remains.
I noticed that every time I restart zigbee2mqtt, the amount of subtopics remain the same, but the number of messages increases, this happens in all the three main topics.
Is that normal behaviour?

Hello everybody,

Just want to share that I'm experiencing the same issue (for me it started just after migrating to 2004.01), the work arround I found so far is to just go in the settings tab of the zigbee device and click on submit, after this the device works again.

If you need logs, please ask, I'm able to produce them. I also confirm that my mqtt topics still contains data (the info are retained) I also tested with the retain check box activated (in the device settings tab of zigbee2mqtt) and it changed nothing, I still have to apply my work arround to mka emy devices working again.

nonolk wrote: ↑Friday 09 February 2024 11:14 go in the settings tab of the zigbee device and click on submit, after this the device works again

I have to do that for every device individually, everytime the MQTT Hardware is (re)started (fi after a reboot).

Is this the same in your experience?

azonneveld wrote: ↑Friday 09 February 2024 11:40 Is this the same in your experience?

yes exactly, starting from the 2024.01 version.

nonolk wrote: ↑Friday 09 February 2024 13:26 yes exactly, starting from the 2024.01 version.

There is even a quicker way to get the failing devices discovered (again):

First: in the zigbee2mqtt frontend, click the edit icon:


Second: just press the 'Save description' button to trigger the discovery:




I tried the current beta (2024.3.15906), but the bug is still there.

It looks like the init loop is terminated before all devices are read.
Afterwards updating them one by one makes MQTT AD to add them.

Ah, good catch, It's indeed faster.

@gizmocuz should we open a ticket for this ?

A related Github issue is created by a user: https://github.com/domoticz/domoticz/issues/6025

waltervl wrote: ↑Monday 12 February 2024 11:07 A related Github issue is created by a user: https://github.com/domoticz/domoticz/issues/6025

That's me

I've made a short video, demonstrating what is happening.

1. Everything is running fine
2. MQTT AD hardware is restarted
3. Device cannot be controlled (even if I waited a longer time)
4. Name of device is altered in zigbee2mqtt gui (or another trigger, updating the description also works)
5. Device is working again

Here is the video: https://www.azsystem.nl/download/domoticz.mp4

Are all devices not reacting after restart of mqtt AD gateway or some. Is there something specific with those not re-discovered devices? eg All battery devices, specific brand, specific functions?
Are all sub devices from a zigbee device not found (one zigbee device can have several devices created eg temp, lux, motion) or some of the Domoticz devices are not working anymore?

waltervl wrote: ↑Monday 12 February 2024 18:38 Are all devices not reacting after restart of mqtt AD gateway or some. Is there something specific with those not re-discovered devices? eg All battery devices, specific brand, specific functions?
Are all sub devices from a zigbee device not found (one zigbee device can have several devices created eg temp, lux, motion) or some of the Domoticz devices are not working anymore?

Most of the more 'complex' devices are not working:

Ikea Dimmable Lights
Ikea Pushbuttons
Tuya powermeasuring sockets
ledstrip

Only 4 urls allowed, next post will contain devices that keep working

Keeps working:
Silvercrest smart plug
Thermometers
Valve actuator

Im not sure about motion detectors (RTCGQ01LM), they work sometimes.

For for example the tuya power sockets are all the devices not working? There should be a switch on/off, a power measurement device, voltage, current, etc. Are all not working anymore?

waltervl wrote: ↑Monday 12 February 2024 20:38 For for example the tuya power sockets are all the devices not working? There should be a switch on/off, a power measurement device, voltage, current, etc. Are all not working anymore?

for the powersockets I know that the measurementdata is not updated, I have not tested switching them (one is used for the fridge, and therefor always on)

waltervl wrote: ↑Monday 12 February 2024 20:38 For for example the tuya power sockets are all the devices not working? There should be a switch on/off, a power measurement device, voltage, current, etc. Are all not working anymore?

Managed to reproduce on a fresh install using the database.db from the zigbee2mqtt original instance, so the devices are there.

I can supply the image from the installation if you like.
You will need the following to run the image:
RPI4 or RPI3
ZigbeeStick
32gb SD or SSD.

I am no developer, so cannot help.

After the update i had the same problem.
Some zigbees dudn't work. Nit sure if this was only in Domoticz or a zigbee2mqtt problem
Deleted the problem makers in zigbee2mqtt and recreatief them again. After that it worked again in Domoticz.

Not a big issue, but you're busy with it and i noticed after a couple days. So some data is calculated.

Not sure this is related, but since 2024.4 I have issues with zigbee devices that are loosing connection. I use DeConz in stead of zigbee2mqtt but have simulair issues. Within DeConz devices are connected, in Domoticz they are offline for a long period.

Emil01 wrote: ↑Friday 16 February 2024 21:07 Not sure this is related, but since 2024.4 I have issues with zigbee devices that are loosing connection. I use DeConz in stead of zigbee2mqtt but have simulair issues. Within DeConz devices are connected, in Domoticz they are offline for a long period.

Is DeConz also communicating over MQTT?