bamarayne
(Jason "The Enabler" as deemed so by @Smart)
162
I bought one of these a while back and finally got around to mounting it and adding it to the network. I mounted mine in the garage.
Initial inclusion:
Pain in the butt. It is an officially supported device, but it connects as a z-wave door sensor. Even when excluded and then included under the actual device. I went into the app and changed it to a z-wave motion sensor and it works great.
Device type:
I am using @bridaus device type. Just because I can. It works great.
Summary:
The sensor is super sensitive and works perfect for the garage. I have my lights set to go on when the house door opens or when the garage door opens or when there is motion. With a 15 minute delay for off after the open events or when there is no longer motion. This one picks up the slightest movement meaning my lights do not go off until I leave the garage.
Iām going to buy more of them.
Edit: @bridaus, will you do me a favor and add the ability to change the timeout on this thing back into your code? If not, thatās cool. Thanks.
I paired two of these last night, couldnāt get them to work properly until I installed the custom device type. They seem to work great once connected properly.
Maybe I got lucky. I set mine to 25% sensitivity and connected it. At first it came up as an open/close sensor but when I went to remove it it then listed as a z-wave motion sensor. Works great. Even turned up the sensitivity to 50% without any issues so now it works well in my living room with vaulted ceiling.
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
166
I had all kinds of trouble, but it was all my faultā¦ I managed to freeze muy hub and everything I was doing was useless until I rebooted it.
I have it set to 100% and picks up everything. Itās perfect for my garage.
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
170
Iām pretty sure you have already done this, but is worth askingā¦
Exclude the device from the app.
Run a general device exclusion even if the first time was successful. I did this twice moreā¦ Just to be on the safe side. But this studio probably wonāt be successful if the device was successfully excluded by step one.
In the API deserve the custom device type. Refresh the page or log out and back in, just to make sure itās gone. Iāve been fooled by glitches in the system before.
Reboot the hub
While the hub is rebooting do a system reset on the device (it canāt hurt plus you have a couple of minutes to kill)
go back into the API and create the custom device type. Make sure itās saved and published.
Add the device back to the system. Make sure you have the battery out of the device, start the search procedure in the app, put the battery in, count to 2 and press the button on the back. Count to 2 again and press it again if it isnāt found.
*note during this step it may need a quick press, or a long press. Iāve noticed it sends to be different with different devices.
After all of this you should be good. This is what I went through to get mine working. After I figured out that I had frozen my hub.
The minimote has an āexcludeā button. Press it, then press the appropriate button on the device to enter exclusion mode. Be within a a footish. Youāll get a blue light on the minimote confirming that itās actually been excluded. Iāve had such an easier time with the minimote for device resets vs the hub.
Edit: I typically exclude via smartthings first to avoid zombie devices, and then exclude with the remote. Seems that sometimes smartthings fails to fully exclude from the zwave network but still deletes it from its internal āgraphā database.
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
175
Thank you very much for this device type, it works great for me!
Do you think it will be possible to add a āreset timeā shorter between movements.
I would like the motion to turn inactive after 2 seconds for example. If we could make it modifiable in āEdit Deviceā it will be fantastic!
FYI ā sending out constant movement notifications with 2second spacing will possibly cause congestion on your zwave network and will certainly chew thru your batteries in short order.
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
178
Just curious, does anyone have any of these they are wanting to get rid of?
Thank you for your answer @codytruscott, I am aware of the battery life if i report more frequent movements.
However, I still need to be able to change the āreset valueā on inactive movement faster as this procedure is crucial to mode changing in my configurationā¦