I just got back to the computer after getting the kids out the door and low and behold the sensor that refused to work logged motion!. . . . .. . and then refused to again haha.
I changed out the battery and put it in place (as opposed to next to the PC). Forgot about it for 30min, and it seems to be working!
Perhaps a battery issue? Perhaps a ZigBee issue with this spot (seems unlikely as I have an Xbee only 8m from here).
Anyway, I did try the built-in driver with motion no temp. It was no different but it also didn't have the buttons to reset to active/inactive. Those are quite nice for troubleshooting automation etc. Dose that just mean it didn't config properly?
Must admit it would be nice to cut down on extra drivers to remember in the future.
Hi Just thought I'd add my findings.
I purchased a pair of these SNZB-03 about a month back and set both up in my office near the hub and got a similar issue battery reads but never signals activity even thought the sensor flashes as you walk by etc.
I had other HA related things to do so I sent them back.
After reading on here that so many others have them working ok I bought another pair (I'm planning on putting PIRs in every room so the price of these will make a heck of a saving if they are stable.)
Same thing again on first device, paired straight away, battery reads but no activity. I did a full reset of Hubitat by powering off, five minutes later turned on and straight away the sensor was showing active etc.
NOTE : Prior to this point only one device attribute was shown.
I then paired the second device, pairing went seemlessly, same issue though (and battery was at 35%)
I had some things to do to integrate the working sensor on my animated floor plan dashboard (more on that later in another post). All of a sudden I noticed it was working.
My assumption is that these sensors (or more likely the driver) needs some time to settle in before reporting. This may have something to do with the scheduled job which was initially listed at the bottom of the driver page (forgot to screen grab it) but was set for about 20minutes in the future. Since there is no scheduled job for either device now I'm assuming the driver initially sets up a scheduled task for now+20minutes and after that job has run the sensor works correctly.