I have a fleet of these which are really Centralite 3326-L that I ported over from ST and generally speaking, they all work well. However, I have one in particular that after resetting and joining to Hubitat, constantly shows motion when there is none. Yesterday while away from the house, it sent 200+ notifications of motion when HSM was armed.
I have done the usual troubleshooting including a new battery to no avail. Any suggestions or advice?
Correct, it did not, this is new behavior. I am curious and will try to look today, but there is a green flash when it detects motion. I am wondering if it is actually detecting something, or this is a hub issue...
I have about 15 of these Iris v2 3326-L motion sensors paired with my HE hub. They all are very well behaved.
When I was buying these in bulk off of eBay, I did come across one of them that would pair successfully, but would then never detect motion. I tried all of the possible reset options to no avail. So, it is possible for these to simply go bad, IMHO.
Hopefully you have a spare sensor that you can swap out for this problematic one.
During the pairing process, if the button on the side is held too long after inserting the battery they can enter that mode. If I remember correctly, there is also a quick flash of a different color (blue?).
I have 4 hubs covering my house but only one of them has the Zigbee Radio enabled and devices paired. about 4 weeks ago I decided that it was time to migrate off that old hub and on to a new one... something I had been putting off (dreading) for at least a year.
During the move of the devices from one hub to the other, I had 2 hard fails.. both Iris v2 Motion Sensors. One had the physical button die.. I had to solder a jumper to it and use that to press the button during battery insert to get it to go into pairing mode. Other than that, it's still working just fine. The 2nd is still not hanging on a pairing. I put a battery in and it starts blinking blue (pairing mode) forever. The Hub finds it, but never creates a device/completes.
BOTH of these v2's worked every day, all day, right up to the moment I needed to move them. One is just that button, but it's still a fail that occurred that only appears during hub moves (new pairing).
It's possible they are just getting too close to their end-of-life. Which is really sad since there's no easy replacement. (Size)
One quick question - while you had these 3326-L sensors paired with your ST hub, did you allow them to receive the OTA firmware update for them? The final firmware for these motion sensors was much better than earlier versions. It was a bit of a crap-shoot as to what firmware came with these when they were purchased.
For the first batch of 3326-L sensors that I ordered, I initially paired them to an Iris hub just to receive the firmware updates. Later, after Lowes shut down Iris, I used my old ST v2 hub to pair later purchased sensors with, just to update the firmware.
For some reason I thought that HE could now update the firmware on these, but the other day I acquired a used one and added it to my mesh, and I see that it is on slightly older firmware (firmwareMT: C2DF-001F-11005310) and there is no update button. So I guess not. (Is that correct, @mike.maxwell ?)
I have 25 of these on my mesh, and I've managed to break 2 by dropping them. But those just stop reporting motion, and I can't find anything physically wrong I can solder. I use them as temp sensors.
If you reset them, and don't hold the button down for longer than while you insert the battery , you will eliminate demo mode as a possibility.
Agreed... However I seem to recall that there was an option in the Groovy IDE to disable OTA updates. But it has been a long time since I used ST. And I have no idea if that option still exists in the 'new' Groovy-free ST world.