@Pipiche , thnx I think i'm indeed at the limit with my devices.

That didn't work either:

2019-08-25 19:49:24.699 (Zigate controller) processNotinDBDevices - NWKID: abba, Status: 0045, RIA: 4, HB_: 3
2019-08-25 19:49:24.703 (Zigate controller) [4] NEW OBJECT: abba Request Model Name
2019-08-25 19:49:24.703 Status: (Zigate controller) [4] NEW OBJECT: abba TimeOut ...

I'm going to try to add a new fresh motion device

Hello , I did a pull but the result is the same. it seems more device ('lumi.sensor_magnet'') are detached, and can be reconnected but stay dead after reconnection (once a blink of the blue led when the magnet is removed or attached), TXpower is set to 0. I'm also not able to add more zigbee devices.

I did , still the same result, maybe the Xiaomi device does not understand what the Zigate controller is sending at the end. I'm away for a week, but I will try a new fresh device when I'm back and update this post. @pipiche, thnx for your quick answers and all the work you do for this nice product ...

I tried it

Screenshot from 2019-08-18 12-12-33.png

The result is the same, it gives these messages in the log :

2019-08-18 12:20:02.823 Status: (Zigate controller) Started.
2019-08-18 12:20:03.576 Status: (Zigate controller) Entering work loop.
2019-08-18 12:20:03.577 Status: (Zigate controller ...

I tried it with another Door contact which is not responding anymore.

If I look at the device log I see :

2019-07-28 08:32:58 Off
2019-07-28 00:20:49 On
2019-07-27 10:16:14 Off
2019-07-26 20:07:02 On

I opened the window and it is not sending info to the Zigate controler.
If I look at the admin ...

Hello All,

I flashed the Zigate controller device to version 3.1A and updated the plugin to the latest beta.
After that, I went away for two weeks. When I came back a few devices (XIAOMI battery operated devices) were not responding anymore.
So I did a reconnect with a 'lumi.sensor_magnet' device ...