@KingStrava I’ve had 2 go dead like that, which I ended up returning and exchanging. Since then, I found the following reset instructions that may help. Give this a try, and then add it back to your hub to see if that does the trick:
Step 1: Remove the battery and wait ten seconds
Step 2: Press and hold the reset button while reinserting the battery. Hold for an additional two seconds and release.
Note: The reset button is a small white button located on the side of the motion sensor.
If that doesn’t work, I would exchange it for a new one.
@xavier999, A few of mine are in that range fresh out of the box. I’m not surprised either. I bet the batteries aren’t the greatest.
As for how it changes, I’m pretty sure they report in a similar way that the ST sensors do, and that’s in a range vs incremental 1% changes. In other words, 88%-100%, then 75%-87%, etc, etc. There’s a discussion about battery ranges and how that works somewhere in the community. If I can find it I’ll provide a link.
thanks so much for this device type.
I just started with it this past week. so I don’t have a lot to go on yet, but so far, it seems to be working just fine.
@cvastola This discussion was broken off from another thread because it was getting huge.
You can use Mitch’s code and then switch back to ST’s default so the device runs local to the hub, or you can follow my instructions to pair the device as is and then switch to ST’s default.
When you add the device it will use Mitch’s code right off the bat without any problems, and then you can switch over to ST’s if you want to keep device usage local on the hub.
If you opt to not create a device type with Mitch’s code, ST will add the sensor as a Thing, and then you’ll need to follow my instructions. Without a doubt following the instructions is the long way of doing it compared to Mitch’s. I’ve probably used Mitch’s code for most of mine because it was just faster.
So I tried to delete the code that I added because when I added it everything went fine but the lighting automation I set up wasn’t working…it was as if the motion wasn’t being detected. But I still see the device in my device types even though I have deleted it and when I click on it I get an access denied message…I am going to try and re-add it but I wonder what I am doing wrong…I just added the device type, it recognized the device as a motion sensor but no motion was detected. Weird…
Something is up/wrong with the IDE since yesterday I think. I get the same message trying to delete one of my device types. I’ve submitted a support ticket, but I have yet to get a reply.
Sometimes this has happened to me, and I had to reset and add it back. In just a couple situations I actually had a bad sensor. Try the rest process for the motion sensor:
Step 1: Remove the battery and wait ten seconds
Step 2: Press and hold the reset button while reinserting the battery. Hold for an additional two seconds and release.
Note: The reset button is a small white button located on the side of the motion sensor.
Flashing red when there is no motion and runs through a bunch of colors when there is motion detected…I have two automations set up and both are working and being noted in the logs. Maybe I bought the colorful version?
That’s really odd, and I bet your battery won’t last too long. I wonder if it’s stuck in some find of test mode or something. I’ve not seen that before.
I’d at least try a factory reset and reinclude the device - look at step 11 in the instructions link I provided above. You don’t need to delete the device in ST because of the way zigbee device ID’s are managed compared to zwave, and that’s good because you don’t have to go back and rebuild or reconfigure any SmartApps.
Is there a way to report the battery on these, such that SmartTiles can see it as a capability and output that? I see it in the iOS app…but not able to be chosen in SmartTiles setup. Or perhaps thats a question for @tgauchat for something on their side…just curious.