It's really annoying that ZigBee devices don't update directly in HomeKit/HomeBridge.
Communication between ZigBee2MQTT and Domoticz is instant but to homekit and homebridge not (I have to refresh before the correct status is displayed).
Scherm­afbeelding 2025-10-12 om 15.50.12.png
Scherm ...

No seperate state topic only 'contact: true/false'. Strange thing is that the status of this sensor in domoticz instant change when open/close door but in homekit and homebridge I have to refresh before the status changes. How can I solve this?

I've monitoring the traffic of one of my zigbee doorsensor (name is 0x00158d000ad849f6)
At topic ' zigbee2MQTT/0x00158d000ad849f6' I get back when I open the door:

{"battery":100,"contact":true,"device_temperature":23,"linkquality":131,"power_outage_count":12,"trigger_count":0,"voltage":3025}

Is ...

yes I'm on the latest version (I've struggling to update but suceeded).I'll try this days to monitoring my mqtttraffic with mqtt explorer.

Someone have an idea? I'm increasingly thinking it's an MQTT problem. Zwavemqtt works instantly between Domoticz and HomeKit/HomeBridge.

In Domoticz, I refer to 'zigbeeAD' under auto discovery.

The MQTT settings for zigbee2mqtt (YAML file):

mqtt:
base_topic: zigbee2MQTT
server: mqqt://10.0.1.122 ...

I've noticed that the ZigBee door sensors in Domoticz aren't transmitting their status correctly to HomeKit via HomeBridge. Only when I manually shut down and restart HomeKit does the status transmit correctly. IIn domoticz the status is updated immediately.
Is there anything I can do about this? It ...

thx, problem is solved. After a while en some restarts things starting to work as expected.

thx, I've now in my yaml:
homeassistant:
enabled: true
discovery_topic: zigbeeAD
status_topic: zigbeeAD/status
mqtt:
base_topic: zigbee2MQTT
server: mqtt://10.0.1.122

In domoticz:
Auto Discovery Prefix: zigbeeAD

Some zigbeedevices working perfect now in domoticz but some are a little ...

Solved it after many hours trying.

One thing I don't understand. In the new yaml.file I've:
homeassistant:
discovery_topic: zigbeeAD
mqtt:
base_topic: zigbeeAD
server: mqtt://10.0.1.xxx

In domoticz I also fill in the 'zigbeeAD' into the mqtt discoverysettings. In the frontend z2m I get an ...

I've updated my Zigbee2mqttversion (first back up data) and updated the settings.yaml file with my own settingsfile. The status:

zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
Active: activating (start) since Fri 2025 ...

I thought by linux but upgrade with cd /opt/zigbee2mqtt
./update.sh I get an error:

pi@homebridge:/opt/zigbee2mqtt $ ./update.sh
Stopping Zigbee2MQTT...
Creating backup of configuration...
Checking out changes to package-lock.json...
Updated 0 paths from the index
Updating...
hint: Pulling without ...

I've 1.35.3. How can I update? By terminalcommand?

I want to add a new device TS0601 (avato led dimmer). After pairing in zigbee2mgtt I get ' not supported device'. However in the zigbee2mqttwiki it looks lik it's a supported device: AVATTO ZDMS16-1 (same device). No I try to add this manually but I'm stuck. I find the right js code for this device ...

solarboy wrote: Tuesday 09 September 2025 17:52 I have 2 of these and they do not show this behaviour. I also use zwaveJSui.

Can you share your settings of these devices so I can compare it with mine.

I've got the Fibaro roller shutter 3 working properly in Zwave JS UI. However, I don't quite understand something. When I close my awning, it retracts properly, but then opens slightly again after a few seconds. After recalibrating, this stops happening, but the same thing happens again shortly ...

I have installed the tuya plugin within domoticz. Devices such as Tuya dimmers work well with this within domoticz. These are immediately recognized as new devices when I first add them to the Tuya smart app. Now I have bought a Nova100 and this is also immediately recognized within the Tuya smart ...

I have installed the tuya plugin within domoticz. Devices such as Tuya dimmers work well with this within domoticz. These are immediately recognized as new devices when I first add them to the Tuya smart app. Now I have bought a Nova100 and this is also immediately recognized within the Tuya smart ...

I migrated from Zwave to Zwave JS. The Zwave sensors within Zwave were neatly recognized in Zwave JS and working fine.

Now I have two new sensors (the same Fibaro wall plug already works fine within JS) and I discovered that I cannot add them.

I use the JS GUI control panel for this. I'm trying ...

Ah, now I understand.
Thanks for the explanation. I'm going to experiment with the dzventz script. It's great that I already have a start.

If I understand correctly, I should use the script: nano notification_external_script.lua ? what should this look like? to send an mqtt message every day? I'm a bit confused as to where I should set something now. I sent a one-time mqtt message in 'nano notification_event_script' with the line: os ...