Multiple E1C-NB7 Leaving Shortly After Joining

[BradleyShaner]

What happened?

I've got 3 Sengled E1C-NB7 devices that previously worked great. Yesterday, I noticed one of them was unavailable so I tried to re-pair it. It joined, but then it left after a few seconds. During the time it was connected I could control it from the UI by switching it on and off just fine. So I ordered two new ones and they're both doing the same exact thing. I then joined a new Leak Detector TS0207 and it works just fine, staying connected and reporting leak status. I also rolled back to 1.35.2-1 and 1.36.1-1 addons with the same symptoms.

These three are the Sengled devices:
0xb0ce1814036c3e14
0xb0ce1814036c4a25
0xb0ce1814036c3e14

What did you expect to happen?

Device to join and stay joined.

How to reproduce it (minimal and precise)

Enable "Permit join" and they will continuously join and leave until the timer runs out.

Zigbee2MQTT version

1.37.0

Adapter firmware version

20221226

Adapter

SLZB-06

Setup

HassOS in a Proxmox container

Debug log

relevant log, after permitting join:
log.txt

First 200 lines of log:
log-first200.txt

[WayneManion]

I have several of these Sengled E1C-NB7 devices. They worked well until recently. In my case they appear to stay joined, but they become very lazy about reporting the power/energy values. Like I only get a value if I hit the "get value" icon in the UI.

I have multiple Zigbee networks.

One network them has one Sengled E1C-NB7 connected via Sonoff USB Dongle P. The E1C-NB7 very rarely communicates power use changes. A Third Reality 3RSP02028BZ power-monitoring smart plug connected to the same Zigbee network is working as expected, with regular updates about power consumption.

Another network has several E1C-NB7 and multiple Third Reality 3RSP02028BZ connected via smLight SLZB-06 PoE Zigbee coordinator. None of the E1C-NB7s reports power consumption regularly, but all of the Third Reality devices do. I swapped a Third Reality device in place of a Sengled as an experiment and it immediately worked as expected.

I include this information just to suggest that the problem does not lie with one particular Zigbee coordinator.

[BradleyShaner]

I'm going to close this for now. I just tried it again and it works, and stays connected. Nothing else changed, so I have no idea what was wrong unfortunately.

If you're having reporting issues you may want to adjust these attributes. A freshly joined plug doesn't report properly but after making these changes it works great.