Techman

You should factory reset the switches then link them individually with the ISY

can you post a copy of your program

Hi Jon, The open node on the ISY will show either on or off so I guess there was really no need for an off node to be supported.

The ISY does not support the CLOSED node on the open/close sensor, only the open node and the heartbeat.

It sounds like you may have a communications issue rather than a battery issue. Do you have any dual band devices within close proximity to the sensors? The open close sensor sends out a heartbeat signal every 24 hours. You can write a simple program to monitor the heartbeat node on the open/close sensor and have it send you an email in the event that the heartbeat signal isn't received.

Are you getting low battery signals from the sensor(s) or are the sensors just not working? Have you or can you physically measure the battery voltage on the sensor when it fails? The batteries should last at least 6 months or longer.

Some of the motions sensors have a firmware bug that causes them to send multiple on signals when the batteries get low, this precedes a low battery signal which sometimes is never sent.

Remove power from the ISY then reseat the memory card and power back up.

what device is used for 'Doors and Windows / Door-Sliding'?

If your ran the diagnostics did you find any corrupted link tables?

Try running a diagnostics on each the switches for your kitchen lights, (show device link tables, then compare links) to see if any of your links are corrupted. You can also try a restore device, which rewrites the device link tables, for the kitchen switches to see if that makes a difference. Another possibility may be that with all the RF devices you have in your system you may be getting data collisions that interfere with the Insteon signals. Are the problems you're experiencing consistent or do they vary?

You should have all the switches that control the kitchen lights placed in a scene as controllers? Turning the scene on or off will then correctly reflect in all the switches located within the scene. When controlling the lights from the ISY you should turn the scene on/off not just one of the switches.

Change "control" to "status" Status is the state of the device, Control is when the device is physically turned on or off.

You'll need to clear your Java cache including applications then download the 4.3.26 version of the Admin console. Hopefully that should clean up your problems. Let us know if that cleared up your issues.

What's version of the ISY firmware What the version of the user interface (admin console) are you using? Do you have anything that could be interfering with the Insteon signals such as a UPS, T.V's, etc. that have not been filtered?

The on/off module is a dual band device as are most of the current modules with the exception of battery operated devices and the IOLinc and some switches. You can check the specs for a device on the Smarthome website which will show if it supports RF.

Which option are you using to download the admin console? What's the version of your ISY firmware?

Delete your Java cache including applications, that will remove the admin console

Is it possible that the sensors are getting tripped multiple times because the location they're sitting in is bridging the contacts. Are they sitting on a dry, non-conductive surface?

Are you using your local UI 4.3.26 to access the remote ISY? If so, that might explain the disparity

Make sure that the device names in your program match those in the scene. Click on the "RUN THEN" clause in your program then manually turn on your light switch. The light should come on at 30%. If that's the case then it's working correctly .

Do you mean that the sensor is 10 feet from the PLM? Is the PLM a dual band model? If so and it still doesn't work then try removing and reinstalling the sensor.

Place the sensor on a wet paper towel, the wet node should show as on in the ISY. Press the set button on the leak sensor to re-set off the wet node to off and the dry node to on You'll need to have a dual band device within fairly close proximity to the sensor in order to insure good RF communications between the sensor and the ISY

Remove the 2477D from the scene then add it back to the scene as a controller It needs to be a controller in order to control the scene that's setting your levels. A device that's a controller will show up as red in your device tree, a responder will show up as blue.

Your program looks correct. Did add your 2477D to the scene as a controller?