I have a Third Reality Zigbee motion sensor that recently stopped working. My best hypothesis is a keeps getting pushed out to it in the background and then it can't talk to my Hubitat anymore.
After the first time it stopped working, I did a factory reset and the exclude/include process. While configuring it, I noticed the Update Firmware button on its device page, so I clicked it. No motion status changes were getting reported. So I did the exclude/reset/include process again, but without the firmware upgrade and it functioned as expected, but only for the rest of the evening. That has been a repeatable process and the last log message before a long period of inactivity is simply "update."
So can I block this update for this device?
Application: 4F
Endpoint Id: 01
Firmware MT: 1233-D3A1-0000004F (same text before or after problem)
Manufacturer: Third Reality, Inc
Model: 3RMS16BZ
Software Build: 0000004F
Driver: Generic Zigbee Motion Detector (No Temp)
Also Tried Community Driver: Third Reality PIR Motion Sensor with same results.
0000004F is the current firmware version. Firmware updates are not automatic, you must push the update button (which is always there even if firmware is up to date). You can see firmware update progress on the 'Hub' device in the logs, not the sensor device.
Your issue sounds more like a communication problem. How many mains powered Zigbee repeaters do you have in your system?
Only 4 Zigbee devices total, and the only mains powered device is on the far side of the hub from this sensor. The sensor has worked reliably since June 2022, only starting to have this problem a week or so now. No other topology changes or new devices recently.
Can you see when the 4F firmware version was released? It might be current, but is it also new? I definitely did not push the update button the time when I saw the update message in the log most recently, but it has also stopped working without that message present. Maybe it was updating something else.
I neglected to mention that I put in fresh batteries. The prior pair measured 48 by the device, I think, and also in the good range of a handheld battery tester. But I tried new ones as the first remediation.
I have a C7 hub running platform version 2.4.3.172. I just upgraded to that this morning and rebooted it, but I never let it get more than a minor rev or two behind.
My powered zigbee device is a power strip that is easy to move, at least temporarily. I can probably put it line-of-sight to both the sensor and the hub and see how things behave. Thanks for jumping on my issue and I'll report back after I run it like that for a while.
It's definitely not recent. I checked an undeployed sensor I bought in April and it was at the current version. You could always try rebuilding the Zigbee network.
Despite working fine for a while, that few devices and not near a battery powered sensor are a recipe for dropouts and general mesh issues. You probably need a repeater device closer to this sensor or more devices in general to build a stronger mesh.
No Wifi router channel changes or router now set to "optimize" channels?
Any router firmware updates that may have changed something?
No new Wifi equipment in the house?
Have you physically moved or relocated the hub?
Anything new in the home that may be blocking signals like large mirrors, metal signs, or ductwork?
How are you powering the hub, are you using the supplied power brick?
