Open/Close Sensor both stuck Open (On) and Closed (On)?

[Blogography]

I've added a couple open/close sensors and am having problems with the state being "stuck."

 

Open the window and the Open State switches to "On" as expected. Close the window and the Closed State switches to "On" as expected. But both states stay stuck to "On" no matter if the window is opened or closed. I've deleted/re-installed and restored and everything else I can think of, but the problem remains.

 

Oddly enough, programs I write are getting the current state correctly and are able to act on them accordingly. I wrote a simple test program to turn on a light when the window is open, turn it off when the window is closed and it works perfectly.

 

Any ideas on how to get the state reporting correctly?

[Michel Kohanim]

Hi Blogography ,

 

What app is this for? You may want to post to the forum for this app.

 

With kind regards,

Michel

[Blogography]

The screenshot is from MobiLinc, which is merely passing along the status it's receiving. The exact same thing shows up in the ISY Admin interface... BOTH the Open AND the Closed status are "On." They are stuck that way until you remove/add the sensor... then the same thing happens again.

[Teken]

The screenshot is from MobiLinc, which is merely passing along the status it's receiving. The exact same thing shows up in the ISY Admin interface... BOTH the Open AND the Closed status are "On." They are stuck that way until you remove/add the sensor... then the same thing happens again.

 

Information Only: There are three nodes represented in the ISY Series Controllers Admin Console.

 

They are Open, Closed, Heart Beat.

 

As of this writing the open & heart beat are the only user accessible nodes to the end user. The close node isn't supported since Smartlabs removed the black jumper in the hardware. Meaning the dual mode isn't available for use until such time as UDI supports this feature. Regardless, the open node will toggle from On vs Off along with the heart beat node if and when the 24 hour time interval has been met. 

[Blogography]

So... after 24 hours the heartbeat will initiate. Once that happens, the "Open" status will start showing ON and OFF properly? Well that was easy... thanks!

[Teken]

So... after 24 hours the heartbeat will initiate. Once that happens, the "Open" status will start showing ON and OFF properly? Well that was easy... thanks!

 

No . . .

 

The *Open* node is what you should be looking at. If you view that node only and open / close that window you will see that change of state. The heart beat is a totally different and independent feature which was included several years ago to offer general insight. Such as the battery had enough power to transmit the heat beat and roughly can inform a person if a device is with in range of a dual band RF device.

 

IE. You place the Open-Close sense 25 feet and the heart beat is received by the controller. Now you moved it to say 50 feet and nothing comes in past the 25 hour mark. You would move the sensor around until you could reliably see the heart beat captured on a consistent basis. Obviously, you could simply press the set button and toggle it from open / close to make it show the status.

 

Also, note if you press the set button a few moments later it will send a heart beat update to the controller too.

 

Lastly, if you have never set up a heart beat tracking program I would encourage you to use the number one heart beat tracking offered by our esteemed: Belias   

[Teken]

This is the program you should incorporate into your Insteon arsenal: http://forum.universal-devices.com/topic/11566-leak-sensors-a-suggested-complete-program-package/?hl=+heart%20+beat

 

Anything that offers a heart beat such as the leak sensor, open-close, hidden door sensor, motion sensor II.

[Blogography]

But that's the problem... the state for the "Open" node is always shown "On." After adding the device and opening the window, the status is "On" and it stays "On" no matter how many times I open or close the window.

HOWEVER... as noted, when I use the status in a program, the correct state is used. So ISY is getting the proper state and using the proper state... it's just not setting the proper state when looking at the status.

[Teken]

But that's the problem... the state for the "Open" node is always shown "On." After adding the device and opening the window, the status is "On" and it stays "On" no matter how many times I open or close the window.

 

HOWEVER... as noted, when I use the status in a program, the correct state is used. So ISY is getting the proper state and using the proper state... it's just not setting the proper state when looking at the status.

 

Simple test ~ Bring the device to the 2413S PLM and repeat.

 

What is the results?

[Teken]

Also, ideally you should be using *Control* not *Status*. Control reflects the actual physical state of the hardware whereas Status does not.

[Blogography]

Unhooked from the window. Deleted from ISY. Walked 10 feet over to the PLM. Added to ISY. Opened and closed the contact. Same thing. The OPEN status is set to "ON" then stays "ON" even when I close the contact. Opening and closing the contact DOES, however, turn the dining room light off and on in my test program. So it's just the status that's being incorrectly reported.

The reason I need the status to be reflected correctly is so I can use the status for alerts via MobiLinc. So far as I know, MobiLinc has no access to "Control" (which is what I'm guessing ISY programs use since it's working correctly there).

[Teken]

Unhooked from the window. Deleted from ISY. Walked 10 feet over to the PLM. Added to ISY. Opened and closed the contact. Same thing. The OPEN status is set to "ON" then stays "ON" even when I close the contact. Opening and closing the contact DOES, however, turn the dining room light off and on in my test program. So it's just the status that's being incorrectly reported.

 

The reason I need the status to be reflected correctly is so I can use the status for alerts via MobiLinc. So far as I know, MobiLinc has no access to "Control" (which is what I'm guessing ISY programs use since it's working correctly there).

 

I want you to do do this for me unplug the 2413 PLM for ten seconds. Remove power from the ISY Series Controller. Plug the 2413S PLM back into the wall and wait about five seconds. Apply power to the ISY Series Controller and log back into the Admin Console.

 

Does the *Open* node now reflect the change in states from open vs closed keeping in mind have the sensor next to the 2413S PLM.

[Blogography]

Unplugging the PLM and ISY exactly as you suggested just reset all my battery operated devices to null... including my hidden door sensors, water sensors, and the window sensor. I put the window sensor right next to the PLM. When I separate the contacts, the status for OPEN changes to ON and the dining room lights from my test program come on. I put the contacts back together and the status for OPEN remains ON but the dining room lights from my test program go off.

Is it possible I have a faulty sensor? The water sensors and hidden door sensors are much further away from the PLM... and further away from any plug-in mesh devices (there's an on/off outlet switch directly below the window where the open/close sensor is located).

[Teken]

Unplugging the PLM and ISY exactly as you suggested just reset all my battery operated devices to null... including my hidden door sensors, water sensors, and the window sensor. I put the window sensor right next to the PLM. When I separate the contacts, the status for OPEN changes to ON and the dining room lights from my test program come on. I put the contacts back together and the status for OPEN remains ON but the dining room lights from my test program go off.

 

Is it possible I have a faulty sensor? The water sensors and hidden door sensors are much further away from the PLM... and further away from any plug-in mesh devices (there's an on/off outlet switch directly below the window where the open/close sensor is located).

 

Possible it could be a defective sensor but lets try a few more items so you know for sure. Your options are the following in no specific order of relevance or importance but you should do each one to eliminate root cause.

 

1. Hard reset the open close sensor per the full users manual. Ensure you delete the sensor from the ISY first. Then add it back and report back the results.

 

 

Factory Reset All settings and scenes will be erased and return to factory default settings. 1) If you are using Open/Close Sensor to control any responders, unlink them from Open/Close Sensor. See Remove Open/Close Sensor as a Controller. 2) Use a small screwdriver to gently remove Open/Close Sensor main case 3) Remove battery and wait at least 15 seconds 4) Press and hold set button on Open/Close Sensor while reinstalling battery 5) Release set button when the status LED turns on

 

Open/Close Sensor status LED will stay on for about 4 seconds and then turn off

 

2. Once the sensor has been added back. Take a twin piece of wire and insert it into the external I/O ports. Short (touch) them together does the *Open Node* reflect the correct state of On vs Off? 

[Teken]

Also a little bit of house cleaning just so there isn't something really silly going on. Please ensure the following so the basics are covered.

 

1. You should be running the latest 4.6.2 firmware. Ensuring you followed all the steps in the release notes and cleared out the Java cache and selected ALL box's.

 

2. Ensure both the UI and Firmware match by confirming at the top of the Admin Console Help -> About.

 

3. When you add the device to the ISY Series Controller use the *Start Linking* button which looks like two colored swirling arrows. Going this route will avoid someone selecting the incorrect hardware or entering the wrong Insteon ID. 

[Blogography]

Thanks so much for the suggestions... I'll try hard-resetting the sensor tonight and see where that gets me!

[Blogography]

Updating the firmware was the first thing I tried. I was sure to clear out the Java cache... including the app cache, which meant I had to reinstall the admin console, so everything should be good there. The version number is definitely showing up correctly. Thanks.

[Teken]

Thanks so much for the suggestions... I'll try hard-resetting the sensor tonight and see where that gets me!

 

No worries, in the interim please confirm what the Admin Console indicates as the UI & Firmware. If there is a difference that alone has caused untold grief to hundreds of people over the years. The Admin Console can be downloaded in the same thread the firmware was obtained.

[Blogography]

Well... I've done everything I can think of. I've just spent three hours trying to get this one stupid sensor to work. I've reset it. I've rest the ISY. I've removed and added a dozen times. It's an older model, so I've tried it with the jumper on and off. Nothing... NOTHING... I do will make the state update. Once they go on, they stay on for eternity. The "open" state will stay permanently ON no matter how many times I open and close the window. No idea what's going on since any pairing I make works flawlessly and it's only the state that's screwed up... but these sensors are useless to me if the state won't be set properly by the ISY.

[Teken]

Well... I've done everything I can think of. I've just spent three hours trying to get this one stupid sensor to work. I've reset it. I've rest the ISY. I've removed and added a dozen times. It's an older model, so I've tried it with the jumper on and off. Nothing... NOTHING... I do will make the state update. Once they go on, they stay on for eternity. The "open" state will stay permanently ON no matter how many times I open and close the window. No idea what's going on since any pairing I make works flawlessly and it's only the state that's screwed up... but these sensors are useless to me if the state won't be set properly by the ISY.

Can you show me the UI & Firmware: Help -> About. Also what happens using a two wire pair and shorting them together?

 

 

Sent from my iPhone using Tapatalk