Continuing the discussion from Bosch Motion Sensor (ISW-ZPR1-WP13) : Smartthings v2 hub:
How to fix your issues with the Bosch ISW-ZPR1-WP13 motion detector.
This explanation is in great detail and very long. It will make your detectors work and if they don’t you will now know why.
I’m not wanting credit for this because I’m a newbie in this whole thing. The only thing I did was to figure out a sequence of events that other people did though in this combination it just works. All of my testing has been done from two Android devices and on Windows 7 PC for accessing Smartthings IDE (there online developer app). You must have a Smartthings account, not a Samsung account. You can have both, but only use your Smartthings account for your Hub. If you can’t, it’s because you don’t have a V1 or V2 Hub.
If you don’t know the difference between the two accounts then use the correct URL below to access it:
Please, everyone state what type of Smartthings controller you have. This is super important. First off do not even attempt this with the new Samsung Connect Home Mesh Wifi Smarthings Hub. It requires the Smartthings (Samsung Connect) app. You will sacrafice a weekend in the process and I never made it work at all. Most of you that say it discovered a “Thing” are using one of the new Wifi contollers with a Hub built in that you enable. For now, I recommend not using them. I hope as you do that Samsung will bring back the functionality of the original Hubs someday for them.
You want things to work correctly use a Smarthings Hub V2. I can’t make comments about V1.
Use Smartthings Classic, Not Smarthings (Samsung Connect). And once again use a Smarthings account, not as Samsung account.
Do not run the V2 Hub along with or in conjunction with a Connect Home wireless router unless you disable the Smartthings hub within the router. What a joke, but believe me if you do you will have issues, LATENCY and and severe connectivity issues with devices.
I have found that some, not all, home wifi mesh systems just toast the whole process. For testing, use one wireless router and a cable to get your ST V2 Hub away from it a very good distance. Testing, testing, you know the drill.
On to the reason you are reading this. How to make the Bosch ISW-ZPR1-WP13 motion detector work correctly.
Here are the symptoms I encoutered in no particular order.
Could not add the device.
Could add the device but then it was stuck on Motion or no Motion and would not change though the temp and battery seemed to work.
Could see it, add it, and it worked while in Walk test mode, but 2 - 10 min. later it was gone until I power cycled it or sometimes just triggering the tamper button.
Sometimes they would work for a few hours.
The battery sequence to clear reset the device wouldn’t do anything. No flash, nothing.
Taking off the back and putting it back on (tapping the tamper button) would not put it into test mode.
I was going to throw away two out of the six detectors I bought, but then I figured this out.
Follow this exactly with no exceptions and hopefully you will be happy you bought these things because if you are like me you just wanted to smash them.
Log into your Smarthings Account IDE (Integrated Development Environment) with a PC preferrably or a browser of some type, NOT YOUR SAMSUNG ACCOUNT.
Select My Locations
Click on the HUB/Location you are now working on.
Go to My Devices at the top.
Remove all of the Bosch devices we are discussing.
Note: Very important. Do not use the same device names again. If you do, this will not work If you have one called “Front door motion” then do not use it again when you add the devices back in. Call it “Door Front Motion” or something. Later, after all your testing you can come back and change the name to what you used to have it. This is a MUST>
Go to my Device Handlers:
Make sure you have only one device handler for this type of device. I highly recommend you use tomasaxerot : Bosch Motion Detector (it’s available all over the place)
Important note: There is a simple mod to his handler that I will tell you about later that makes this process more easy. I don’t know and I apologize if I’m doing something wrong telling you to make this change. But, if you follow the rest of this you don’t have to change his code at all and it still works perfectly fine.
If you have another handler for this device, remove it. Now make sure you go through the correct steps in adding this device handler back in. Most of you know the steps. Go find the Device handler mentioned, hopefully you find the one that you can select Raw and then copy, then add new device handler. Do not type anything into the “From Template”, select From Code, paste in your copied code, select Create, then Save, then publish. Now you are ready to add your motion detectors with the following approach.
Put in the bottom battery in both the left and right side. Now do not push the top batteries into place, just set them in with the negative side in place but the positive side is sticking up on both the left and the right side. Some ask what is the right side. While looking at the back of the sensor being the batteries, the tamper trigger is at the bottom. The right battery is on the right side of the sensor. Remember at this point neither of your top batteries are touching on the positive side, correct. Both are fully ready to snap in.
You have less than 4 seconds from the time you push in the first battery to do this. If you fail, remove the top batteries, wait at least 20 seconds and try again. Here we go. Press and hold the tamper trigger, push down the battery on the right side until it snaps in place, now do the same on the left one. Release the tamper trigger. If you did it correctly it will typically blink a few times rapidly, and then after a bit it will start that 3 blink thing it does when it is in pairing mode.
Important Note: You do not need to put the back on. Sometimes some don’t but they will still allow you to pair. If not, do the sequence over again but this time snap on the back, wait at least 30 seconds, open the back for a few seconds and then close it. It will probably go into Tamper mode and blink like crazy and that is a good sign. Just set it down and wait until it’s done on it’s own. It will then go into pairing mode.
Now select + or + Add a thing. If your device doesn’t show up, go back to step 7 and do it again. If it does show up Select Rename Device. Give it some odd name you have never used. Then select Done and then Save. It should could back with Confirm Paired Device, select OK.
Go back to Samsung IDE and look up your device. If not there, refresh the page, Click on the device. Scroll to the bottom and select Edit. Click on Type (drop down) and change it to “SmartSense Motion Sensor”. Then select Update at the bottom.
Wait for 20 to 30 seconds or longer and then snap on the back. Do not turn the lock tab. At this point or in 10 seconds or so it should go into walk test mode. Some don’t and you have to open and close them a second time. Now it should work.
Now you can go and change the Name to what ever you like.
This brought all my messed up sensors back to life and made them work correctly again. This does not fix the 3 or 4 min delay in between motion detection. Yes it’s probably a hardware setting but I feel it can be forced by the Hub to do what you want. Why? Because it makes no difference what stage of the game you are in, when you select remove a working device it contacts that device immediately.
Note: I hope as mentioned above that I’m not doing something wrong in telling you this. If I am I do honestly apologize and will modify my post if I am.
If you want to skip step 10 above then modify the device handler. Go to Line 20 where it says “Bosch Motion Detector” and change it to “SmartSense Motion Sensor”. It will notify you it has been modified, then save and publish. My tests show that it works. Not guaranteed but it appears to work.
If you change the order, sequence, add or subtract from this approach it doesn’t work. Follow it, ok?
Finally freedom using Bosch