ZWave so chatty its breaking things

Add-ons Bindings
1

It seems the Zstick is full and this sensor (zw111 aeotec motion sensor) wont shut up, despite turning on selective report, changing the thresholds and turning command poll off. I have two of these and they are both USB powered.

Logs show this, constant updates via the MQTT event bus between my house and garage:


23:00:16.975 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated BackEveHumidity to 90
23:00:16.976 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'BackEveHumidity' changed from 89 % to 90 % (source: org.openhab.core.automation.module.script)
23:00:29.733 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - mqtt:broker:MQTT_Broker:remote_updates triggered House/out/Back_Eave_Temp/state#20.6
23:00:29.735 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated Back_Eave_Temp to 20.6
23:00:29.737 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'Back_Eave_Temp' changed from 20.7 °C to 20.6 °C (source: org.openhab.core.automation.module.script)
23:00:30.250 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - mqtt:broker:MQTT_Broker:remote_updates triggered House/out/Back_Eave_Temp/state#20.6
23:00:30.252 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated Back_Eave_Temp to 20.6
23:00:31.164 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - mqtt:broker:MQTT_Broker:remote_updates triggered House/out/Back_Eave_Temp/state#20.6
23:00:31.166 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated Back_Eave_Temp to 20.6
23:00:31.409 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - mqtt:broker:MQTT_Broker:remote_updates triggered House/out/Back_Eave_Temp/state#20.6
23:00:31.411 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated Back_Eave_Temp to 20.6
23:00:31.793 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - mqtt:broker:MQTT_Broker:remote_updates triggered House/out/BackEveHumidity/state#90
23:00:31.794 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated BackEveHumidity to 90
23:00:34.384 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - mqtt:broker:MQTT_Broker:remote_updates triggered House/out/BackEveHumidity/state#90
23:00:34.387 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated BackEveHumidity to 90
23:00:35.255 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - mqtt:broker:MQTT_Broker:remote_updates triggered House/out/Back_Eave_Lux/state#0
23:00:35.257 [INFO ] [penhab.core.model.script.eventbus-sub] - Master Sync: Updated Back_Eave_Lux to 0

Any suggestions?

image
image820×990 23.5 KB

Thanks!

2

Since some of the updates are the same, I suspect the event bus is triggering messages. Also maybe device is zw100, zw024 or zw074?

For unsolicited advice why aren’t you using the remote OH binding?

3

I am using the Openhab binding, 5.1.0.

4

I assume you are using the latest version of MQTT Event Bus [4.0.0.0;5.9.9.9] for the event bus.

Can you click on the code tab and paste the configuration sections for both OH instances?

I don’t think it’s the event bus, but I need to test with exactly your configuration to make certain. It certainly looks like something is getting into a loop and the event bus would normally be the most likely candidate.

5

I have nothing against the MQTT Event Bus (and used it years ago) and possibly I don’t understand your set-up. My unsolicited advice was the remote OH binding available in the OH5.1 store.

remote oh2026-01-05 164951
remote oh2026-01-05 164951775×448 38.6 KB

Also Zw111 is nano dimmer and doesn’t have the parameters in your picture

Anyway, another clue could be to set the ZW binding in Debug to validate the ZW binding is sending state updates consistent (or inconsistent) with the thresholds you have set. You can use thezw debug viewer to summarize the log.

1 Like
6

Ah good catch! I didnt even realise I had the remote openhab binding as I’ve been using MQTT for a while, seems its legacy. I’ve removed it. Sorry the sensor is the Aeotec ZW100 Multi Sensor

7

It is not legacy. There are situations where MQTT is a better choice or where the remote openHAB add-on isn’t available. I still maintain it and will do so for the foreseeable future.

But that doesn’t mean the remote openHAB add-on isn’t a better choice in this instance.

8

I mean, legacy in my environment :slight_smile: