Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paulmann Licht sends every 3 seconds #2424

Closed
pepp86 opened this issue Nov 27, 2019 · 11 comments
Closed

Paulmann Licht sends every 3 seconds #2424

pepp86 opened this issue Nov 27, 2019 · 11 comments

Comments

@pepp86
Copy link

pepp86 commented Nov 27, 2019

Hi, I have a "Paulmann SmartHome Zigbee LED-stripe (50045)" connected to my coordinator. Everything is working well, but this devices sends every 3 seconds its status (without reporting enabled).

Has anyone else the same issue? Is there a way to configure the device to not spam the network?

Thx
Patrick

@Koenkk
Copy link
Owner

Koenkk commented Nov 27, 2019

I'm not sure where this spam comes from, this bulb is not configured to do so.

@monotonus
Copy link

I have the same issue with a Müller Licht Tint E27 bulb: https://www.zigbee2mqtt.io/devices/404006_404008_404004.html

After updating to version 1.7.1 it started to send every 1-3 seconds an "update":

Nov 27 23:59:29 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:29: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":21,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'
Nov 27 23:59:32 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:32: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":21,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'
Nov 27 23:59:33 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:33: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":21,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'
Nov 27 23:59:35 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:35: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":21,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'
Nov 27 23:59:36 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:36: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":21,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'
Nov 27 23:59:38 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:38: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":18,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'
Nov 27 23:59:39 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:39: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":21,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'
Nov 27 23:59:41 hassbian npm[466]: #33[32mzigbee2mqtt:info #33[39m 2019-11-27T22:59:41: MQTT publish: topic 'zigbee2mqtt/Schlafzimmerlampe', payload '{"state":"OFF","linkquality":21,"brightness":14,"color_temp":370,"color_mode":2,"color":{"x":0.4522,"y":0.4085}}'

There are nearly no updates. From time to time the linkquality differs a little bit, but the other values stay the same.

Maybe we also need to update the coordinator firmware itself? I'm waiting for my CC debugger atm.

@Koenkk
Copy link
Owner

Koenkk commented Nov 28, 2019

While reporting is disabled now, did you enable it once? If so, please re-pair the device, otherwise the reporting configuration is still present on the device.

@monotonus
Copy link

Yes I also had reporting enabled in the configuration.yaml, but it never had an effect. After removing reporting and repairing the device all is fine now again for me.

@pepp86
Copy link
Author

pepp86 commented Nov 29, 2019

Disabled reporting, restarted and repaired the device and now the device is no longer spamming the network.

@Koenkk
Copy link
Owner

Koenkk commented Nov 29, 2019

To fix this issue when reporting is enabled, I need to have the debug logging of the spam.

To enable debug logging set in configuration.yaml:

advanced:
  log_level: debug

@pepp86
Copy link
Author

pepp86 commented Nov 29, 2019

Here you go:

https://pastebin.com/LSTMktsA

Had debugging enabled before

@Koenkk
Copy link
Owner

Koenkk commented Nov 30, 2019

Can you:

@pepp86
Copy link
Author

pepp86 commented Dec 2, 2019

Will try it on the weekend and let you know the result.

@pepp86
Copy link
Author

pepp86 commented Dec 6, 2019

Seems to work - but would this affect any other functions?

@Koenkk
Copy link
Owner

Koenkk commented Dec 7, 2019

Nope, it means that they will only report when the value has changed (by a minimal value of 1). Closing this, thanks!

@Koenkk Koenkk closed this as completed Dec 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants