Sensors type lumi.sensor_magnet.aq2 frozen in Phoscon (Phoscon Web app) but the data changes in deCONZ (deCONZ application)

General
1

Hi,

In home-assistant, I do the bindings via Phoscon (Phoscon Phoscon web app). Each contact works fine after the reset and rebind.
But after a few weeks, clicking on the sensor and then on the specific contact, it seems that the data remains frozen. An open and close of the magnet doesn’t change anything.

  • Fabrikant LUMI
  • Product lumi.sensor_magnet.aq2
  • Versie 0.0.0_0003
  • Batterij 100 %
  • Temperatuur 24 °C
  • Staat gesloten
  • Bijgewerkt 21.10.2024 16:01:49 voor 2 dagen
    However, in deCONZ (deCONZ application), when I click on the ‘+’ of the contact and then click on ‘on/off’, I can see the state changing in ‘cluster info’ in attribute ‘on/off’ (from false to true or vice versa).

Therefor I’m 100% sure that the deCONZ-conbeeII detects each changement. But it doens’t send it into home-assistant (because Phoscon is frozen).
I had the problem already before and therefor I have rebinded all contacts (after a hard reset of each sensor). The problem came back after a few weeks. All the magnets become frozen on the same moment. All other types of devices work fine / correct.

What can I do ?

I have no automations in Phoscon (they are in home-assistant).

Product Conbee II
Phoscon gateway version 2.28.1
Firmware 26580700

2

I have the same behaviour with 2.29.1 (running in Docker) and had it before with the release from summer 2024. The lumi.sensor_magnet.aq2 worked well before.

Phoscon shows me for one of them for example that it was updated 46 days ago. The window is opened and closed every day. Repairing (without deleting) doesn’t change anything.

I have the same problem again (after Sonoff sensors (eWeLink) disconnected and not sending out updates) more and more with “eweLink TH1” (Sonoff SNZB-02). Looking on the network graph, I see links (green, yellow) between the missing (battery powered) devices and other active devices (as plugs or the raspbee gateway itself). As some of the newly disappeared devices disappeared only some weeks after first installation, I am sure that it is not the battery (which was shown to have 92% remaining capacity at the last update).

Any thoughts how to find the problem?

3

Update:

I updated to firmware 26780700 for my RaspBee II (I was one firmware behind as I noticed) and going back to 2.28.1 solved the problem.

All sensors (lumi.sensor_magnet.aq2 and eweLink TH01) send regular updates again.

With 2.29.1 I could pair them (after deleting and restarting the deconz container) but they didn’t send any updates (temp sensor stayed at 0°C and humidity 0% for hours).

4

Same issue discussed here I guess?