dresden-elektronik / deconz-rest-plugin

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

Lost device after updating to 2.27 #7776

Closed molnarti closed 5 months ago

molnarti commented 6 months ago

Does the issue really belong here?

Is there already an existing issue for this?

Describe the bug

My Ikea Trafdri On/Off switch has disappeared from Phoscon since updating to 2.27 (from 2.26.2). The device is not visible from Phoscon or Deconz and also cannot be re-paired. Home Assistant does not detect key presses for the button.

The device reappeares when downgrading back to 2.26.2

Steps to reproduce the behavior

  1. Update Deconz to 2.27
  2. Check list of switches in Phoscon
  3. Ikea Tradfri On/Off switch is missing
  4. Try to re-pair device by following the instructions provided by Deconz
  5. Device is not detected.

Expected behavior

Device should be visible after update.

Screenshots

No response

Environment

deCONZ Logs

No response

Additional context

No response

Zehir commented 6 months ago

I just tried to add one on my network and it's seems to work fine. Did you got a red light on the switch when you press the button 4 times ? Any related logs in deconz ? Do you see it in the deconz GUI ?

molnarti commented 6 months ago

yes, there was a red light blinking, everything looked like the pairing should succeed. I was just thinking about replacing the battery, but had no spares at home, so just tried reverting to the previous version and suddenly it worked. in general it seems to me that I have issues pairing new devices to my Conbee lately. maybe its related to the fact that my conbee stick is in the basement and there is only one device connected to it directly, the rest goes to the mesh network.

MarioMarti77 commented 6 months ago

I have the same behavior than molnarti with Ikea TRADFRI on/off switches, downgrade to 2.26..2 show them again

Zehir commented 6 months ago

What frimware version of the device do you have ? You can download the latest at http://fw.ota.homesmart.ikea.net/global/GW1.0/01.21.031/bin/10005778-tradfri_onoff_controller-24.4.6-prod.ota.ota.signed And then you can install them using the OTA update plugin. Takes about 2-3 hours per switch (can run multiple upgrades at once)

manup commented 5 months ago

The On/Off switch has two DDFs which match to different firmware versions. This was introduced in v2.26.1-beta via PR https://github.com/dresden-elektronik/deconz-rest-plugin/pull/7643

After the update it may take a while until the firmware version is received from the switch (the device should send this periodically to deCONZ), after that the correct DDF should be selected.

MaxVRAM commented 5 months ago

I've had the same issue. Updating to 2.27 caused the IKEA switches completely disappear from the Deconz interface and would not pair again.

I didn't catch a "breaking changes" in the release notes. Is this expected behaviour?

Zehir commented 5 months ago

I've had the same issue. Updating to 2.27 caused the IKEA switches completely disappear from the Deconz interface and would not pair again.

I didn't catch a "breaking changes" in the release notes. Is this expected behaviour?

Are you on linux ? It's not an expected behavior and will be fixed soonish

molnarti commented 5 months ago

What frimware version of the device do you have ? You can download the latest at http://fw.ota.homesmart.ikea.net/global/GW1.0/01.21.031/bin/10005778-tradfri_onoff_controller-24.4.6-prod.ota.ota.signed And then you can install them using the OTA update plugin. Takes about 2-3 hours per switch (can run multiple upgrades at once)

updating to the linked fw solved the issue for me. but i have another switch still in the box, I am curious how it will pair still with the old fw

MaxVRAM commented 5 months ago

I've had the same issue. Updating to 2.27 caused the IKEA switches completely disappear from the Deconz interface and would not pair again.

I didn't catch a "breaking changes" in the release notes. Is this expected behaviour?

Are you on linux ? It's not an expected behavior and will be fixed soonish

Thanks for the clarification. I don't know what the OTA plugin is or if it's a known part of the update process, but figured I'd just roll back until I had time to investigate next week.

Yes, I'm running the docker image on Fedora 39 x86-64.