Silvercrest door sensor not logging

[Knarf99]

Hi, I am using a silvercrest doorsensor with Zigate running on Synology NAS.
It worked fine for some time, but now -since several days- is not receiving switch signals anymore (see log), although Domoticz indicates that it still sees the device via indication “last seen”.
Any clues what to do? .

[Knarf99]

Additional info: the domoticz log is showing:

[waltervl]

Is there a kind of reset pinhole in the sensor that you can switch?
Also put Zigate in accept new hardware mode before you do that.
Else we have to wait for pipiche. He will probably want to see the export of the raw devices from Zigate web menu tools.

[pipiche]

If I understood the sensor is still on the network sending for instance Device Annoucement,
the lastseen is updated regularly which confirm it is on the network and communicating .

Did you check the battery ? are they still good ? I have seen some device with Low Battery able to send Device Annoucement (whcih basically is a connection to the network) but not able to send anything else.

If it works a while and suddenly stop with this behaviour I would consider something like that.

[Knarf99]

Hi Pipiche, batterylevel is still good (only few weeks old), Zigate UI is showing a healthy node. Very strange. I removed the device in Domoticz and reinstalled it as a new device in Zigate again (all history logging is lost af course). Now it is working again, but what actually happened remains a mystery. If I trigger the device I instantly get the above status in the log...(Device announcement: etc.)
Hopefully it will stay on track now.

[waltervl]

I have sometimes de idea that for some devices the device announcement (from an non responding device) is only recognized by the Zigate when it is in accept new hardware mode. But normally it works OK. I see this only with some xiaomi devices.

[pipiche]

@waltervl as part of the Zigbee 3.0 standard an end device (battery based) must do a Device Announcement when the device wake up (even if alreday on the network). What is behind is that as the end device can sleep for a long time and wake up after it might not be ready on the network side to handle the communication. This is why.

@Knarf99 the reason is healthy in the Web UI is simply because the plugin has received a message from the device, and Device Announcement is one.