Hubitat with Homemade Temperature, Humidity, Pressure and Light sensor

[leeonestop]

@iharyadi I'm interested in the latest. PM the info thanks.

[iharyadi]

Playing round if I can easily hook something up to use the module detecting a power loss like here.

[iharyadi]

@SmartHomePrimer

Iman, I've been thinking about how to create a remote temperature probe for barbecue that I would be able to set target temps and trigger TTS announcements, send notifications and adjust temp with a fan if needed. I have the original sensor from you and I know you said the expansion of an external probe re

@SmartHomePrimer, I had a chance to get the AD8495 recently. It is quite good an interface board for a temperature probe.

Zigbee K-type thermocouple probe

[SmartHomePrimer]

That’s cool. Nice demo!
I forgot to follow-up on this. My girls bought me this cool gadget for Christmas. It’s an incredibly well engineered device. Measuring internal temperature of the meat and External temp of a the BBQ or oven. Bluetooth connection and charging via a battery in the holder when you clip the thermometer back into it.

Great app, Just tell it what kind and cut of meat you’re cooking and it calculates the rest, then notifies you when it’s done. You can check time to finished and temps from the app or via their cloud connection you can just ask Alexa. The cloud connection also allows you to connect a spare phone or tablet to the thermometer, and then login with a second phone or tablet to monitor or receive notifications anywhere you have internet access.

[iharyadi]

@SmartHomePrimer

My girls bought me this cool gadget for Christmas.

It looks like really nice BBQ probe. Perhaps, I would get one next Christmas.

[SmartHomePrimer]

Why wait? Start hinting for your birthday!

[iharyadi]

Birthday would work too.

[martyn]

@iharyadi received my sensors yesterday, thanks for the fast shipping!

Unfortunately I'm struggling a little:-)

I loaded the device handler from hubitat/Environment SensorEx at master · iharyadi/hubitat · GitHub

I've only tried one so far and it seems to have paired OK, but doesn't seem to do much after that!

How often should it transmit? The blue LED is permanently on, is that right?

After the initial pairing activity in the ZigBee logs I don't see anything else from the device. Hitting Refresh or Configure doesn't do anything.

If I put HE back into Discovery mode I see a single packet from the device:

profileId:0x0, clusterId:0x13, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:254, lastHopRssi:-81

and then nothing at all.

If I put HE into Discovery mode again and hold the button in on the device for 3 or 4 seconds then it seems to transmit a bunch of stuff again but only while the Discovery window is open (it seems to loop). If I close the Discovery it goes quiet again.

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:15.067 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B26080B050C0401210400, dni: 2B26, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0104, encoding: 21, value: 0004

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:13.078 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B26080B050C0000210000, dni: 2B26, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:11.058 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B26080B050C2001290200, dni: 2B26, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0120, encoding: 29, value: 0002

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:09.058 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B26080B050C1F01290000, dni: 2B26, endpoint: 08, cluster: 0B05, size: 0C, attrId: 011F, encoding: 29, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:07.044 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B260804000C0000210000, dni: 2B26, endpoint: 08, cluster: 0400, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:05.052 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B260804030C0000210000, dni: 2B26, endpoint: 08, cluster: 0403, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:03.040 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B260804050C0000210000, dni: 2B26, endpoint: 08, cluster: 0405, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:19:01.060 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 2B260804020C0000290000, dni: 2B26, endpoint: 08, cluster: 0402, size: 0C, attrId: 0000, encoding: 29, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:59.348 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0001 08 01 0040 00 2B26 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:59.347 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0001 08 01 0040 00 2B26 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:55.137 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0400 08 01 0040 00 2B26 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:55.136 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0400 08 01 0040 00 2B26 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:51.126 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0403 08 01 0040 00 2B26 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:51.125 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0403 08 01 0040 00 2B26 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:40.911 [info](http://IPADDRESS/device/edit/140)Refresh

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:40.899 [info](http://IPADDRESS/device/edit/140)Configuring Reporting and Bindings.

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:28.657 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: FBE2080B050C2001290200, dni: FBE2, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0120, encoding: 29, value: 0002

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:26.646 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: FBE2080B050C1F01290000, dni: FBE2, endpoint: 08, cluster: 0B05, size: 0C, attrId: 011F, encoding: 29, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:24.644 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: FBE20804000C0000210000, dni: FBE2, endpoint: 08, cluster: 0400, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:22.640 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: FBE20804030C0000210000, dni: FBE2, endpoint: 08, cluster: 0403, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:20.638 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: FBE20804050C0000210000, dni: FBE2, endpoint: 08, cluster: 0405, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:18.665 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: FBE20804020C0000290000, dni: FBE2, endpoint: 08, cluster: 0402, size: 0C, attrId: 0000, encoding: 29, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:16.755 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0001 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:16.754 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0001 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:12.732 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0400 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:12.729 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0400 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:08.851 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0403 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:08.850 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0403 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:04.746 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0405 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:04.742 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0405 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:00.880 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0402 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:18:00.878 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0402 08 01 0040 00 FBE2 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:58.521 [info](http://IPADDRESS/device/edit/140)Refresh

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:58.509 [info](http://IPADDRESS/device/edit/140)Configuring Reporting and Bindings.

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:46.884 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE8080B050C1501210200, dni: 1DE8, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0115, encoding: 21, value: 0002

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:44.863 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE8080B050A1D0128D1, dni: 1DE8, endpoint: 08, cluster: 0B05, size: 0A, attrId: 011D, encoding: 28, value: D1

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:42.871 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE8080B050C0501210A00, dni: 1DE8, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0105, encoding: 21, value: 000A

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:40.856 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE8080B050C0401210A00, dni: 1DE8, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0104, encoding: 21, value: 000A

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:38.862 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE8080B050C0000210000, dni: 1DE8, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:36.852 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE8080B050C2001290200, dni: 1DE8, endpoint: 08, cluster: 0B05, size: 0C, attrId: 0120, encoding: 29, value: 0002

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:34.847 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE8080B050C1F01290000, dni: 1DE8, endpoint: 08, cluster: 0B05, size: 0C, attrId: 011F, encoding: 29, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:32.861 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE80804000C0000210000, dni: 1DE8, endpoint: 08, cluster: 0400, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:30.848 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE80804030C0000210000, dni: 1DE8, endpoint: 08, cluster: 0403, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:28.844 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE80804050C0000210000, dni: 1DE8, endpoint: 08, cluster: 0405, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:26.841 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 1DE80804020C0000290000, dni: 1DE8, endpoint: 08, cluster: 0402, size: 0C, attrId: 0000, encoding: 29, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:25.109 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0001 08 01 0040 00 1DE8 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:25.108 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0001 08 01 0040 00 1DE8 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:21.386 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0400 08 01 0040 00 1DE8 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:21.384 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0400 08 01 0040 00 1DE8 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:06.738 [info](http://IPADDRESS/device/edit/140)Refresh

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:17:06.731 [info](http://IPADDRESS/device/edit/140)Configuring Reporting and Bindings.

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:54.341 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 93410804030C0000210000, dni: 9341, endpoint: 08, cluster: 0403, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:52.418 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 93410804050C0000210000, dni: 9341, endpoint: 08, cluster: 0405, size: 0C, attrId: 0000, encoding: 21, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:50.377 [info](http://IPADDRESS/device/edit/140)description is read attr - raw: 93410804020C0000290000, dni: 9341, endpoint: 08, cluster: 0402, size: 0C, attrId: 0000, encoding: 29, value: 0000

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:48.520 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0001 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:48.516 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0001 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:44.521 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0400 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:44.518 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0400 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:40.732 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0403 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:40.729 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0403 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:36.511 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0405 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:36.508 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0405 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:32.433 [info](http://IPADDRESS/device/edit/140)DID NOT PARSE MESSAGE : catchall: 0104 0402 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:32.430 [info](http://IPADDRESS/device/edit/140)description is catchall: 0104 0402 08 01 0040 00 9341 00 00 0000 07 01 00

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:30.224 [info](http://IPADDRESS/device/edit/140)Refresh

[dev:140](http://IPADDRESS/logs#dev140)2019-01-22 10:16:30.217 [info](http://IPADDRESS/device/edit/140)Configuring Reporting and Bindings.

Any thoughts?

[iharyadi]

@martyn

How often should it transmit? The blue LED is permanently on, is that right?

It should transmit data quite often. You should have something within a couple minutes.

Based on your images, it seems that it struggles to get data. There should be a lot more attributes than that.

The second thing is the humidity value and temperature and illumination is approximately 0. Something is wrong there.

This is like all the sensor is dead. It is strange since I test individually each sensor before I ship out.

You can try to remove the sensor and try to start again. To set the sensor to factory reset. Unplug the sensor from power and battery. Press the button on the back. Plugs the sensor to power while pressing on the button. Keep pressing for 4 seconds and release.

I typically like to recommend to pair as close as possible to the hub initially. You can move the sensor afterward.

Do you have other zigbee device?

[iharyadi]

The looping is a concern.

I have not seen something like this on my end. It is like it loop in the configuration mode. The hub is calling configure multiple times. This happen if it is like the sensor never pair at all. The hub think that there is a new sensor joining but in fact it is already join.

Hmm this is strange.

[martyn]

So a little more on my ZigBee setup:

1. Channel 20
2. XBEE router
3. 5 SmartThings Presence Sensors
4. 2 SmartThings Flood Sensors
5. 2 SmartThings MultiSensors
6. 2 SmartThings Motion Sensors
7. 1 Xiaomi Aqara Motion Sensor
8. 2 Xiaomi Aqara Temperature / Humidity Sensors
9. 1 Xiaomi Aqara Vibration Sensor
10. 2 NYCE Motion Sensors
11. 6 Hue Motion Sensors
12. 1 Xiaomi Aqara Door Sensor
13. 1 Hue Dimmer Switch
14. 1 Osram Switch
15. 1 Xiaomi Aqara Light Switch

The XBEE and Aqara Light Switch have both proven excellent Routers, no issues with any sensors dropping off and everything stable. Layout wise my house is essentially a cube, 5 rooms upstairs, 5 rooms downstairs. HE is in downstairs front right, Aqara light switch is in downstairs rear left (so diagonally from HE) and the XBEE is in the center upstairs (so almost triangle between the HE and Aqara).

I've now tried two of your sensors, with the same results. I also removed them from HE and reset them using the instructions above.

When I pair them there seems to be that initial flurry of activity in the logs but as you mention it's like it's not actually finishing the pairing for some reason?

I've also noticed that they both disappear from the network - by that I mean that when I scan on my XBEE they initially show up during pairing, but then if I stop the scan and start a fresh scan they have disappeared again.

If I put the HE back into Discover mode and leave it there for a while, the sensor does pop up again on the XBEE scan. But again, if I stop the scan and start a new one, the sensor is no longer there.

The original pairing attempts were carried out upstairs (my office) which is closest to the XBEE) the most recent pairing attempts were carried out next to the HE.

(sorry for the brain dump of data above, just trying to give you as much information as possible).

[iharyadi]

The channel looks fine.

I have tried my sensor along with xbee. It get along fine. I can try it again later on with xbee. It is early morning here for me.

I do not have aqara to test.

I mention the 2 just in case my sensor pair through those 2 and not working as expected.

Based on trying the other sensor and get the same results, we can rule out hardware issue.

I am starting to be suspicious that there may be some incompatible device in the mesh. It cause the sensor never completed pairing. This is my first guess.

It also possible that it is told to leave the mesh. This is my second guess.

I am not sure whether it is practical to try to shut your other zigbee routers to troubleshoot this issue.

The other option is to find a sniffer and try to see in the traffic if there is anything out of ordinary that cause the above.

Do you have the other hub to try to isolate the issue?

[martyn]

I powered down the Aqara light switch and tried again but got similar results.

I'm loathe to power down the XBEE as this has a bunch of endpoint devices routing happily through it. For reference HE has 4 endpoint devices and 2 router devices, the Aqara has 2 endpoint devices and the XBEE has 20 endpoint devices. The endpoint devices do jump around occasionally but are mostly static (mostly the SmartThings Presence Sensors move).

I do still have the SmartThings Hub active so will try pairing there and report back

[SmartHomePrimer]

Just curious. Are the Hue Motion sensors directly paired? Most of us can’t even get a single one to work, let alone pair. Not saying it’s the issue, but definitely stands out as different if the are indeed paired directly to the hub.

If they are, is it feasible to remove the batteries from all 6 to test?

[martyn]

OK, I tried one of them in SmartThings and it works fine so I guess there must be something off with the HE setup.

Just to make sure HE ZigBee side was still OK and not experiencing any general problems, I paired another Xiaomi Aqara Temperature / Humidity sensor and it paired fine and is happily chatting away, routing via the Aqara light switch.

Out of interest, which XBEE and settings do you use on it? Mines setup as per the thread at Everything Xbee

[martyn]

Before I added the XBEE (a month or so ago) I had 3 Hue direct paired with no issues. After adding the XBEE the Hue moved themselves there automatically. I added the other 3 Hue a couple of weeks or so back and no issues (they seemed to jump on the XBEE straight away).

Sounds like I may have been lucky with the Hue then?

[SmartHomePrimer]

It’s not that I’ve never been able to get it to pair. I can, but I get zero response from the Hue Motion sensors in HE. @mike.maxwell has had similar experiences. It seems they work fine for some, but don’t work at all for most people that try. Definitely something in your favor.

[martyn]

I seem to recall I had to use a community device handler to get them to configure, but once they start reporting I switch to the built in device handler.

Other than that I've not done anything special with them!

[iharyadi]

@martyn

Out of interest, which XBEE and settings do you use on it? Mines setup as per the thread at Everything Xbee

Mine is XBEE S2C. I may not have 100% exactly the same setting. It is setup as a router. I confirm that on my xtcu. My sensor see packets from Xbee as well as far as I can tell based on the RSSI.

Out of your routers and coordinator(the hub), I think at least Xbee and the hub should be compatible with my sensor. I am not sure about Aqara. However, you shut it down. It does not work as well.

My second guess is that something is telling the sensor to drop out of mesh in your Hubitat Zigbee Mesh. I am hopping that we do not have to go in there. The brute force way to troubleshoot this is to turn off device by device and until one point you should be able to find the problem. Another way which can be difficult is to fire up a sniffer and watch for a suspicious traffic.

[iharyadi]

Out of your devices, the one that I have heard back and tested with my module in their network are ( I also own some of them and use them along with my homemade sensor)

SmartThings Presence Sensors
SmartThings Flood Sensors
SmartThings MultiSensors
SmartThings Motion Sensors
Xiaomi Aqara Motion Sensor
Xiaomi Aqara Temperature / Humidity Sensors
Xiaomi Aqara Vibration Sensor
Xiaomi Aqara Door Sensor

I do not recall any feedback on below.

NYCE Motion Sensors
Hue Motion Sensors
Hue Dimmer Switch
Osram Switch
Xiaomi Aqara Light Switch

As a candidate, if you want to try powering down method is Osram. Their bulb has a bad reputation. However, this is really more of wild guess. End devices do not typically send packet that tell routers to drop out of Mesh.