So I am also testing one of @iharyadi's devices, with the main purpose of looking at routing compatibility with Xiaomi devices.
After pairing it the first time, I realized that it would probably be difficult to "steal" rejoining devices from previously being routed through one of my XBees.
So today, I unplugged my XBees, and then paired @iharyadi's device. Not want to wait for the mesh to "heal", I went ahead and rejoined devices that were previously routing through an XBee.
So far, I've got some Xiaomi "original" and Aqara door/window sensors, a few Aqara Temp/Humidty sensors, and an Aqara Leak sensor rejoined through @iharyadi's device. We'll see how it goes in the "long" term with those.
However, I am having a really hard time getting any of my Sengled Classic (E11-G13) bulbs to pair properly. I'm seeing a Java error in the logs for all those Sengled bulbs that I've never seen before: Queue full, and I've started a forum thread specifically about that error.
The strange thing is with an extra XBee (not previously used) in XCTU, I can see that those bulbs are showing up in the mesh network map as being routed through @iharyadi's device:
I am also noticing low RSSI values despite some of the child devices being in the same room as @iharyadi's sensor (does it have a name that I can refer to it by?)
I put the cart in front of the horse a bit by not installing the custom device driver for the multi-sensor, so I installed and assigned that, and now I'm seeing that Queue full error when I try a manual configure or refresh for @iharyadi's device. Also it doesn't seem to be reporting and the Current States in the device details page hasn't populated with any information yet.
I don't want to reset it or remove it from the Hubitat network yet, so I'm going to reboot my hub and report back if there's any change.
EDIT: A reboot seems to have cleared away the Queue full errors:
I'm seeing quite a few read attr - raw: log entries for the device, mostly on cluster 0B05.
