RKinOhio Posted March 10, 2018 Posted March 10, 2018 Here's the puzzle... I bought and set up an Insteon 2844-222 on my ISY994i with Z-Wave. I used a manual install with the older 2842-222 configuration and it worked fine. I could not control any of the sensor's settings from the ISY, but using the sensor status as an input I wrote a program to control an outside light from dusk to dawn with the program controlling the time out which works fine for me. Didn't use an Insteon Hub. The set up wasn't much of an issue and the ISY would show motion from the sensor when motion was present on the console properly. The sensor is battery powered and as you would expect, the battery died. I replaced the battery and now it wouldn't signal the ISY when there is motion. If, however, I press the sensor's 'set' button once, the ISY console reports motion 'on' at the sensor; press again and it reports 'off' at the sensor. When 'on', it won't time out; it just stays 'on' and the same with 'off'. Obviously, the sensor is able to talk to the ISY now, but regardless of the state that I set the status using the set button, it is not communicating motion to the ISY. The sensor's green LED is indicating motion as it did before but the ISY isn't getting the message. This happens regardless of whether I have pressed the set button to turn the ISY sensor status 'on' or 'off' manually. I have uninstalled the sensor from the ISY and then re-installed it without any impact to its operation. I am thinking about doing a factory reset on the sensor, but since it worked before I am a little hesitant. Before I do that, does anyone have suggestions to try out? I have to be missing something here. Thanks in advance! RK
Teken Posted March 10, 2018 Posted March 10, 2018 Reboot the ISY Series Controller.Sent from my iPhone using Tapatalk
RKinOhio Posted March 10, 2018 Author Posted March 10, 2018 Done. Restarted the ISY and reloaded the console. At first the sensor's status was blank. So was the sensor's dusk.dawn status, but the low bat status showed off. Motion did not change the status of the sensor. One press of the set button put the status to on. Another press took it to off. Thanks for the help, by the way. RK
Teken Posted March 10, 2018 Posted March 10, 2018 40 minutes ago, RKinOhio said: Done. Restarted the ISY and reloaded the console. At first the sensor's status was blank. So was the sensor's dusk.dawn status, but the low bat status showed off. Motion did not change the status of the sensor. One press of the set button put the status to on. Another press took it to off. Thanks for the help, by the way. RK RK, Since you already did a delete and add you can try these last two things. 1. Do a device restore 2. Delete the device from the controller. Factory reset the device per the users manual. Than add it back and let us know what happens.
RKinOhio Posted March 11, 2018 Author Posted March 11, 2018 I reset the devices, deleted the sensor, completed the factory reset and reinstalled the sensor. It now signals the ISY when it sees motion, but it enters a loop in which it goes off after about 38 seconds and then comes back on 1 second later, and repeats. I have the sensor sitting inside a closed desk drawer and it is not seeing any motion. I left it there and checked back about 2 hours later and it was not cycling. I woke it up and we are back to cycling. Any ideas? Thanks, RK
Teken Posted March 11, 2018 Posted March 11, 2018 20 minutes ago, RKinOhio said: I reset the devices, deleted the sensor, completed the factory reset and reinstalled the sensor. It now signals the ISY when it sees motion, but it enters a loop in which it goes off after about 38 seconds and then comes back on 1 second later, and repeats. I have the sensor sitting inside a closed desk drawer and it is not seeing any motion. I left it there and checked back about 2 hours later and it was not cycling. I woke it up and we are back to cycling. Any ideas? Thanks, RK Plug the sensor using the Micro USB and report back if it behaves the same using this alternate power source. If it does it may be defective and its time to submit a RMA and get another one via cross dock with Smarthome.
RKinOhio Posted March 11, 2018 Author Posted March 11, 2018 Thanks, Teken. The sensor worked fine with the micro USB. The replacement battery that I used was supposed to be a 3.7V replacement for the 123 battery, but the fully charged voltage of my new 16340 battery is 4.2V, not 3.7V. The recommendation I went with, from someone that used a this rechargeable 16340 in place of a 123 on another product, was not a good battery for this application. I just put in a new 123 and all is well again. Puzzle solved. I appreciate the help. Do you know of a suitable, rechargeable replacement for the 123? Thanks, RK
Teken Posted March 11, 2018 Posted March 11, 2018 (edited) 14 minutes ago, RKinOhio said: Thanks, Teken. The sensor worked fine with the micro USB. The replacement battery that I used was supposed to be a 3.7V replacement for the 123 battery, but the fully charged voltage of my new 16340 battery is 4.2V, not 3.7V. The recommendation I went with, from someone that used a this rechargeable 16340 in place of a 123 on another product, was not a good battery for this application. I just put in a new 123 and all is well again. Puzzle solved. I appreciate the help. Do you know of a suitable, rechargeable replacement for the 123? Thanks, RK Hi RK, You can certainly try your hand at some rechargeable A123 batteries in place of the primary cells. I know they are expensive so investing into rechargeable's may pan out over the long run in terms of ROI. Having said this, if you have the ability to wire a USB cord in that area that is the route I would take. The added benefit is the device will now act like a dual band repeater when powered this way. One thing I did was place a few of these devices on a small UPS so if power was ever lost the sensor state would not be in the ISY Series Controller. Edited March 11, 2018 by Teken
Recommended Posts