Koenkk / zigbee2mqtt

Zigbee šŸ to MQTT bridge šŸŒ‰, get rid of your proprietary Zigbee bridges šŸ”Ø
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.03k stars 1.67k forks source link

Issues with Green Power devices past 1.36.1 #24119

Open DennisJohnsen opened 1 month ago

DennisJohnsen commented 1 month ago

What happened?

Hello

So i'm in a bit of a pickle atm. I'm currently running 1.36.1, but there is a fix in 1.40.1 for something else i would like. I digress.

But all versions past 1.36.1 (I've tried 1.40.1 and 1.40.0 and 1.38.0) causes over half of my Green Powered devices to stop responding with any action. They show up in the UI just fine, but no action is sent to MQTT when clicking them, but it seems to some of them. It seems random which ones work and doesn't work, nothing with range to the Zigbee adapter. So i'm at a bit of a loss.

The devices in question: https://www.zigbee2mqtt.io/devices/PTM_215Z.html#enocean-ptm%2520215z

As soon as i revert back to 1.36.1 they all just work as expected again when Zigbee2Mqtt is running again.

I tried to interact with two switches in the log, one that works and one that doesn't. Not sure if makes a difference or not. The one that works: 0x00000000017199a1 The one that doesn't work: 0x000000000171db5f

Zigbee2MQTT version

1.40.1

Adapter firmware version

0x26690700

Adapter

Raspbee 2

Setup

Raspberry PI x86 via Docker

Debug log

log.log

chris-1243 commented 1 month ago

You should check #23814. Try the latest-dev. Your problem should be fixed.

There was unfortunately a bug in the deconz driver only.

DennisJohnsen commented 4 weeks ago

Hmm, the same issue with :latest-dev. Only a few of my switches work. At least it's consistent the same switches that works/fails with these different versions than 1.36.1

:latest-dev seems to be restarting though. Heres just a quick look at the logs without debug enabled:

Using '/app/data' as data directory
Starting Zigbee2MQTT without watchdog.
[2024-09-29 10:04:12] error:    z2m: Cannot find '0x00178801093e0030/11' of group 'Stue'
[2024-09-29 10:04:12] error:    z2m: Cannot find endpoint '11' of device '0x00178801093e0030'
Error: waiting for response TIMEOUT
    at DeconzAdapter.checkReceivedDataPayload (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:718:28)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:77:18)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)
Using '/app/data' as data directory
Starting Zigbee2MQTT without watchdog.
[2024-09-29 10:06:11] error:    z2m: Cannot find '0x00178801093e0030/11' of group 'Stue'
[2024-09-29 10:06:11] error:    z2m: Cannot find endpoint '11' of device '0x00178801093e0030'
Error: waiting for response TIMEOUT
    at DeconzAdapter.checkReceivedDataPayload (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:718:28)
    at EventEmitter.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:70:18)
    at EventEmitter.emit (node:events:517:28)
    at parseReadReceivedDataResponse (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:361:27)
    at parseFrame (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:566:32)
    at processFrame (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:515:53)
    at Driver.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:63:25)
    at Driver.emit (node:events:517:28)
    at Driver.onParsed (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:881:14)
    at Parser.emit (node:events:517:28)
Using '/app/data' as data directory
Starting Zigbee2MQTT without watchdog.
[2024-09-29 10:07:36] error:    z2m: Cannot find '0x00178801093e0030/11' of group 'Stue'
[2024-09-29 10:07:36] error:    z2m: Cannot find endpoint '11' of device '0x00178801093e0030'

I will try to add legacy_triggers: true to my config, and set logging info to debug and post a full log.

DennisJohnsen commented 4 weeks ago

Still no dice. The same switches still fail/work on :latest-dev

I attached the log for this restart, where i interacted with both a working switch and a failing one. Same devices as mentioned above

The one that works: 0x00000000017199a1 The one that doesn't work: 0x000000000171db5f

I was unsure where to put legacy_triggers: true so i tried both in the root of the config, and also nested under advanced.

log from :latest-dev

DennisJohnsen commented 3 weeks ago

I just tried 1.40.2 today, same issue.