Upgrade 1.10.3->1.10.14: lost all PTM 215Z devices

[tsunfinger]

describe the problem in Detail. What do you expect to happen ? What does happen ?

after upgrade from 1.10.3 -> 1.10.14 all zigbee devices were working, accept my PTM 215Z - EnOcean Pushbutton transmitter modules (GreenPower).
There was no logging on iobroker or reaction on zigbee device list when pressing button on all of theses devices (I have five of it).
I have to restore iobroker backup to switch back to 1.10.3. After restore PTM 215Z was working...

Adapter version

1.10.14

Coordinator firmware version

0x26780700

Coordinator

ConBee II

Setup

Raspberry PI 4, Ubuntu 20.04.6 LTS

Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections

No response

[asgothian]

Pease update to 1.10.14 again, add the IEEE (without 0x) to the state zigbee.0.info.debugmessages and check if messages appear if/when buttons are pressed.

A.

[asgothian]

Lesen bitte. Du sollst da etwas eintragen, und dann schauen ob es Meldungen im Log gibt wenn du die tasten betätigst.

Siehe auch hier

[tsunfinger]

after upgrade to 1.10.14:
zigbee.0 2025-01-04 17:18:11.472 debug DeviceAvailability:Non-pingable device 0x000000000172d4a9 GreenPower_2 was last seen '16576.837' seconds ago.

that's the only message in logfile (yes, I have pressed the button).

Beside on my other buttons (WXKG03LM_rev2) json message is there but not splitted into the individual "action" anymore (click,hold,double_click)

Finally - no one of my buttons is working after upgrade - have to restore backup

[asgothian]

As long as you don't have any device wich requires the 1.10.14 version, you should be fine with the 1.10.3 one.
You will in the future have to migrate to a newer version, and there may be breaking changes in that.

I can debug the issue with the wxkg03LM devices as I have those, but I do not haver any ptm215Z for debugging.

A

[asgothian]

Duplicate of #2293

[tsunfinger]

was there a fundamental change done in code (but we only have a minor version step)? As there is no logging at all for ptm215Z, could it be triggered by the ieee number? Compared to all other zigbee devices it has a lot of leading "0"s

[asgothian]

There was no relevant change in our code at all, but there was a change in the underlying library (hidden in a minor version update). This was done in preparation for the next major update, which will break further objects in a similar fashion, which is why there is a test branch on my fork for testing and implementing this. You are welcome to try and see what happens if you use that fork.

As I wrote before - I do not have any PTM 251Z device, so I cannot verify if this is affected.

Source for this test is https://github.com/asgothian/ioBroker.zigbee/tarball/1.11

A.
p.s. Please note that there are several pieces of test-code included - the availability system is offline, the map is disabled and there may be issues when trying to add devices to the network