Warnings with Aqara occupancy sensor #1238
Comments
|
Hello |
|
I am asking this because I had the same kind of message with Aqara LED bulb ZNLDP12LM, they are routers like the Xiaomi plugs ZNCZ02LM. I had the same message with pressure, humidity or temperature: These warning disappeared after deleting each ZNLDP12LM and re-paring them. |
|
After a few hours, I can see that all errors are back, I got plenty of these too now: 3/12/2019, 4:59:27 AM - warn: No converter available for 'ZNLDP12LM' with cid 'msRelativeHumidity', type 'attReport' and data '{"cid":"msRelativeHumidity","data":{"measuredValue":5583}}' |
|
@Fabiancrg I am using recent dev version, firmware 20190223 But I think I have figured out why do we see those messages. z2m thinks the source of those packets (originally coming from switches, occupancy sensors, temperature/humidity sensors) is Xiaomi smart plug! Obviously, ZNCZ02LM doesn't support those attributes. Those messages come from correct devices as well. I feel like the same message comes to coordinator two ways (directly and through the smart plug, which is a router). When when it comes via the router z2m thinks the source is the router, which is false. and |
|
I managed to sniff it. First, here is the log: You can see that occupancy sensor sends illuminance and occupancy update, but the same update is received from smart plug as well. Here is the sniffer screenshot: |
|
It would be interesting to see if this is always the case (group id |
|
I will try tomorrow with some other sensor to see if the smart plug broadcasts its message the same way. |
|
Got it for the temperature/humidity/pressure sensor now (0x06a1):
I observe correlation between availability_timeout and these messages. I had availability_timeout disabled for almost a day and no such warnings in the log. I switched it on (set to 60 seconds), and I got the warning in 10 minutes. |
|
@milakov On my side, I had to reboot Z2M several times today as I am trying to add a unsupported device. Last time I restarted it was 3 hours ago and since no message anymore (except the ones I am expecting from my new device). |
|
As there doesn't seem to be a consistent way to ignore these, I've added ignore converters. These messages shouldn't appear anymore in the latest dev. |
|
@Koenkk Do you have an idea if those messages from the smart plug are valid ones? Is it Ok for the router to broadcast end-device attribute report with the only way to specify that end device through group id? |
|
My concern here is that it coud broadcast some other device attributes this way and if the code doesn't check for the group then it could update this smart plug attributes, wrongly. |
|
@milakov this looks to be a hacky way of using zigbee of Xiaomi, I will check if we can add the group so we can check this. |
|
Can you update to the latest zigbee2mqtt dev and provide the debug logging of these messages? |
|
@Koenkk As I have just sent you some logs for my Heiman remote and also get the same messages in the log as milakov, here is the debug message using the dev branch:
|
|
I don't know how to switch this level of debugging with hass.io, here is waht I have: |
|
@milakov is this with the latest edge? |
|
Yes, I think it is (using through hass.io). But, to be absolutely sure, I reinstalled z2m one more time, now waiting for those warnings. |
|
The warnings won't appear any more, as they are ignored, the messages should still be logged. |
|
I don't know if this is related or not but I might see side effect of this. |
|
In the log, LED1 is "LivingRoom_Light_1" and contact door 1 is "LivingRoom_Door" |
|
@Koenkk I am still getting the warnings: |
|
@Fabiancrg please provide without @milakov are you sure you are on the latest dev branch and did a |
|
@Koenkk Sorry for previous output, here is the Pastebin link with debug log: |
|
@Fabiancrg you are experiencing the problem @milakov was concerned about, can you update to the latest dev branch and provide the logging again? |
|
@Koenkk Here is the debug log after the update --> https://pastebin.com/fPbc4TGE |
|
@Koenkk I am sure I uninstalled zigbee2mqtt-edge and installed it again in hass.io. I have been using dev branch for quite some time already this way. Unfortunately log doesn't have commit number: |
|
@Fabiancrg can you provide the output on the latest dev branch when running with @milakov thinking about this again, ignore converters isn't a durable solution, let's check what comes out of the logs of @Fabiancrg |
|
@Koenkk I have just upgraded and open/close the door, here is the new log: |
|
@Koenkk Please disregard the previous debug log, it does not contains the message about the LIght ON when I open the door, apparently the message was not routed to the light. Note that there is no OFF when door is closed so it seems that only the 'contact = false' is triggering an ON message off the light router. |
|
@milakov @Fabiancrg can you check with the latest dev branch, these messages should be ignored now. |
|
@Koenkk I am still getting those warnings: And this is start up log: |
|
@Koenkk It looks good for me now, I have a message saying "Skipping re-transmitted Xiaomi message", I suppose that's what replaced the message that was sending a ON message from the light. |
|
@Fabiancrg great, than this issue has been solved. @milakov it looks that you are on an older version |
|
@Koenkk Are you positive that the docker image was rebuilt with the new dev version? I am using hass.io. |
|
I see now "skipping" messages as well! Thanks! |
Hi, I am seeing warnings for ZNCZ02LM occasionally with recent dev:
The text was updated successfully, but these errors were encountered: