search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.9k stars 501 forks source link

Unusual LQI values when using Raspbee II with Zigbee2MQTT. #4234

Closed m0wlheld closed 3 years ago

m0wlheld commented 3 years ago

Describe the question or issue you are having

When using Raspbee II with Zigbee2MQTT, LQI values of devices increase over time to 255, then fall to to zero. There is an issue report at Z2M suggesting this is a known firmware bug.

Looking for comments on this.

Screenshots

Visual LQI representation, based on values reported by Zigbee2MQTT.

grafik

Environment

deCONZ Logs

n/a

Additional context

manup commented 3 years ago

Hmm very strange the values are straight from the MCU. Over which time frame does it jump between 0–255? Is this happening for all devices or specific to routers or end-devices (usually battery powered)?

I can only observe the LQI values in deCONZ here so far all seems normal.

Gr4ffy commented 3 years ago

Hmm very strange the values are straight from the MCU. Over which time frame does it jump between 0–255? Is this happening for all devices or specific to routers or end-devices (usually battery powered)?

I can only observe the LQI values in deCONZ here so far all seems normal.

All devices, the time frame is approximately 39 hours 38 minutes. Screenshots from Z2M & HA in attachment. conbee.zip

Only these devices look different: https://www.zigbee2mqtt.io/devices/LLKZMK11LM.html#xiaomi-llkzmk11lm https://www.zigbee2mqtt.io/devices/AC03645.html#osram-ac03645

manup commented 3 years ago

Thanks for the screenshots we're looking in to it and try to recreate the issue in with a zigbee2mqtt setup. It's currently not clear where it happens. For that we'll check at lowest protocol level first and then up to the driver, it's suspicious that the zigzag jumps don't appear in the deCONZ APS logs.

kwetnico commented 3 years ago

And this version : deCONZ_ConBeeII_0x266b0700.bin.GCF ? Or this new beta : deCONZ_ConBeeII_0x266e0700.bin.GCF.md5 ?

Pasha1402 commented 3 years ago

What's changed between "d" and "e" subversions? I flashed "d" and LQI isn't any functional right from update and Z2M restart. After few day's LQIs ended up at 83 or 84 and no longer change... does it make sense to check "e"?

manup commented 3 years ago

There is a new firmware changelog wiki page:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Firmware-Changelog

We're still looking into the issue. Right now it isn't clear if this is really caused by the firmware as we don't see the same effects in the deCONZ APS logging.

kwetnico commented 3 years ago

There is a new firmware changelog wiki page: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Firmware-Changelog

We're still looking into the issue. Right now it isn't clear if this is really caused by the firmware as we don't see the same effects in the deCONZ APS logging.

Personally I have this problem with the Deconz Conbee2 key.

manup commented 3 years ago

Looks like we figured it out, the LQI value was correct but the frame interpreted wrongly. Update in Zigbee2mqtt GIT repository should be up soon.

kwetnico commented 3 years ago

Looks like we figured it out, the LQI value was correct but the frame interpreted wrongly. Update in Zigbee2mqtt GIT repository should be up soon.

For you just update to zigbee2mqtt ?

manup commented 3 years ago

The deCONZ driver in Zigbee2mqtt

m0wlheld commented 3 years ago

So, the fix provided for Zigbee2MQTT should resolve this issue, even without updating (Raspbee II) firmware?

manup commented 3 years ago

Yes :)

s3frank commented 3 years ago

ok I understand now, thanks very much for the clarity. I will wait for the next release and follow that on the zigbee2mqtt side. Thank you all for investigating this and finding the issue. Took a while but still very much appreciated!

On Tue, May 25, 2021 at 8:05 PM Manuel Pietschmann @.***> wrote:

Yes :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4234#issuecomment-847811902, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQW7CWXCI33JOQ3WZOK463TPOHCBANCNFSM4WI2NC6Q .

-- Best regards,

-FF

manup commented 3 years ago

The fix should be in the latest Zigbee2mqtt dev branch.

thackel commented 3 years ago

I confirm that updating Zigbee2MQTT to version 1.19.0-dev (commit #c508155) fixed the issue:

image

Pasha1402 commented 3 years ago

Had spare minute to upgrade z2m: now running v1.19.1, Conbee II 0x266d0700 - after couple days all LQIs = 255. Aren't fix from dev included in Prod?

kwetnico commented 3 years ago

Had spare minute to upgrade z2m: now running v1.19.1, Conbee II 0x266d0700 - after couple days all LQIs = 255. Aren't fix from dev included in Prod?

I have the last release z2m Master 1.19.1 and for le it's ok, it's fix for the lqi

gpiszczek commented 3 years ago

I am also observing lqi = 255 for all devices like @Pasha1402 . On the map lqi values vary for different devices/links. z2m 1.19.1 (from hassos) canbee II firmware 0x266d0700

@kwetnico what conbee II firmware are you running?

kwetnico commented 3 years ago

I use deCONZ_ConBeeII_0x26680700.bin

the latest version broke all my links in fronted under z2m

s3frank commented 3 years ago

I have pretty much the same thing all devices at 255 LQI and now staying there so it seems. Only a few not there (yet).

Coordinator Version {'meta': {'maintrel': 0, 'majorrel': 38, 'minorrel': 102, 'product': 0, 'revision': '0x26660700', 'transportrev': 0}, 'type': 'ConBee2/RaspBee2'}

latest for z2m and ha.

On Mon, Jun 14, 2021 at 3:31 AM kwetnico @.***> wrote:

I use deCONZ_ConBeeII_0x26680700.bin

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4234#issuecomment-860259273, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQW7CTQIDENNF2JOS2DRQDTSUBSHANCNFSM4WI2NC6Q .

-- Best regards,

-FF

github-actions[bot] commented 3 years ago

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

github-actions[bot] commented 3 years ago

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

hreichert commented 3 years ago

Same here with 0x26660700 - all LQI 255

LarsSimonsen commented 3 years ago

Same here with 0x26720700 - 80% of my routers and end devices show 255. A few show null, and a few have plausible LQI's.

the-cyberspace commented 2 years ago

Same problem over here while using the latest zigbee2mqtt version 1.22 and conbee2/raspbee2 firmware version 0x26720700. The LQI quality is on every device 255.

leonidfeldman1977 commented 2 years ago

Same problem over here while using the latest zigbee2mqtt version 1.22 and conbee2/raspbee2 firmware version 0x26720700. The LQI quality is on every device 255.

Same for me... Any solution ?