Duplicated messages #649
Comments
|
I have the same problem with my Aqara temp/humi/pressure and human body sensors. Most of the times each message is send twice.
|
|
Threre are a lot of cases when such behaviour doesn't produce any big problems, for instance, illuminance, occupancy, temperature and etc data and events have to be analysed by time anyway, but in some cases (for instance clicking not fixed button) such behaviour turns the automation system into a random number generator. |
|
@lych could you share your debug log? (set log_level debug https://github.com/Koenkk/zigbee2mqtt/wiki/Configuration) |
|
https://pastebin.com/Zckx5zKb |
|
We need to figure out if the messages are send by the device them-self. Could you sniff the packets from the button? (http://www.inzoolee.com/capture-zigbee-packets/) |
|
@Koenkk I'm used to using zboss sniffer with wireshark, but if you want I can do it by folowing your link. Starting from packet 1642, I had clicked the button once and it sent 20 Report Attributes commands and all of them with Sequence number 45 in ZCL frame. There are a lot of such clicks in the dump. The button increments Sequence number each new click. |
|
@lych does this also happen with other lumi.remote.b1acn? |
|
I don't know, I have only one, but it seems that my lumi.weather behaves the same way, as @MarsWarrior wrote above. It happens when the link is bad (link quality 0). I'll try to sniff the packets. |
|
Although I haven't managed to catch the same behavior with lumi.weather, it is much more difficult to catch it because I cannot influence on the process of sending data directly, but it also sends a lot of packets with the same Sequence Number. Nonetheless, there is a difference. There are 3 different Sequence Numbers in each packet. In IEEE 802.15.4 part, in the Zigbee network layer data and in the Zigbee Cluster Library Frame. |
|
@lych zigbee2mqtt doesn't do that, it's either the firmware or zigbee-shepherd who does this. |
|
@Koenkk I'm not sure that my conclusions are correct because I'm still not familiar enough with the Zigbee protocol. If such packets have to be filtered, who shoud do it? I think it can't be dongle firmaware because it's too high level for it. Shoud I move this problem to zigbee-shepherd project? |
|
You can, but it will probably not be solved because it's not maintained anymore. What I found strange is that this issue happens only to you, me and many other have these devices and they work without problems. I still think there is something wrong with your device. |
|
It can be the button of course, and I'll check it when I get another one. But I think, I only one who has this problem just because it's quite difficult to notice. To have it, one needs to run by the button something noticable, like lighting, and one click have to invert its state and link quality have to be about 0. Only in this way this construction starts to work like a random stroboscope :) |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I got the same issue with a recently flashed CC2531 USB stick with all the instructions. Everything seems to work well apart from that Here is what happen when clicking on and off on a Philips Hue Remote paired with zigbee2mqtt (device id has been altered in the log for a bogus id). A Xiaomi sensor is working allright (no duplicate) and all the pairing went smoothly. |
|
@viboux can you post your debug log (http://zigbee2mqtt.io/configuration/configuration.html) |
|
My cube started doing this. I'm pretty sure when I first set it up this wasn't happening. The volume on my TV started going crazy which is how I finally tracked this down. I watched the MQTT data which shows one message using |
You mean by changing the log level to debug instead of info? Or doing more? Here is my version number (firmware and zigbee2mqtt). |
|
@Koenkk Okay, thanks, I would never have guessed. Just curious though, is this by design or is it a bug in HASS? I was under the impression the design idea was to us MQTT as a way to get the data integrated into HASS so it could be used like everything else. Thus once the data gets into HASS the MQTT portion is not used. |
|
@bbrendon it was a bug in has which has been fixed now (attribute updates didn't trigger a sensor state change). |
|
I have issue with duplicated messages, but this one if more than duplication. Light is turned OFF. Always. But I always have this OFF/ON pattern. and HA assume it is back ON. At the same time, with Xiaomi wired wall switches, it is OK, even duplicated 3 times. |
|
I installed dev branch and now it is even more interesting. Issue with OFF/ON is fixed. For "OFF" I get single and correct reply. But for ON I get 3 messages. All of them correct though. And for xiaomi switch I always have 3 messages, for both ON and OFF, all of them correct. |
|
If it matters, this is what I see in log |
|
@antst please provide the |
|
I'm also seeing duplicated messages. Tested with Philips and Ikea lamps. Relevant log section: Full log: https://pastebin.com/kK59DkK2 |
|
This issue will be further addressed in #1309 |
|
Looking forward to #1309. |
|
The device. |
|
I guess those are duplicated messages received through different routers, aren’t they? |
|
@Koenkk I have the same issue with my xiaomi cube. I have subscribed to the "zigbee2mqtt/xiaomi cube" topic and the message payload that I get is repeated twice but in the first one it doesn't contain the "action" . However in the second message which is very identical it does give you the action. Here is what is produced: Is this a bug or? |
|
same issue, I can make it work for the automations, but not the dashboard to get the current status, because the second message is null Zigbee2MQTT:info 2021-11-04 23:52:03: MQTT publish: topic 'zigbee2mqtt/Aqara cube', payload '{"action":"flip90","action_angle":null,"action_from_side":3,"action_side":1,"action_to_side":1,"angle":-38.62,"battery":100,"from_side":3,"linkquality":141,"side":1,"to_side":1,"voltage":3035}'
Zigbee2MQTT:info 2021-11-04 23:52:03: MQTT publish: topic 'zigbee2mqtt/Aqara cube', payload '{"action":"","action_angle":null,"action_from_side":null,"action_side":null,"action_to_side":null,"angle":-38.62,"battery":100,"linkquality":141,"side":1,"voltage":3035}'
Zigbee2MQTT:info 2021-11-04 23:52:03: MQTT publish: topic 'zigbee2mqtt/Aqara cube/action', payload 'flip90' |
|
Same issue. I have all messages duplicated for each device in my zigbee network. Example: |
When I click a button (lumi.remote.b1acn), sometimes zigbee2mqtt produce more then one event
more often it happens when link quality is about 0.
The button produces a lot of Report Attributes commands in purpose to deliver them, but all of that commands have the same Sequence Number.
Is there a way to filter commands with the same Sequence Number?
The text was updated successfully, but these errors were encountered: