Techman

It's easier if you first change the buttons to a 6 button format, only one button to push instead of two. Glad you got it resolved.

The on and off buttons will be the two large buttons at the top and bottom of the KPL. You'll need to change the buttons to the 6 button format first.

I've have the Amin console lock up on me numerous times when I've tried to rename a program. Firmware and UI 4.4.6. Using the Java application. Local access

I wonder if you have something else going on, i.e. poor communications or programs that are using a high amount of resources. There should not be a several second delay to turn on a light when you run a program. Try running a diagnostics in level 3. If the hop count is high then that would indicate a comm issue.

If it's a simple program with only one then statement it should be almost instantaneous. If you use a scene you'll still need a program to turn it on.

Just saw your 2nd post. Programs execute immediately. It's scenes that have a bit of a lag.

Use an IOLinc. Couple the NO contacts from your relay to the Sensor input on the IOLinc. Then write a simple program If Control sensor input is ON Then Turn on whatever

What's the date code and hardware version of the PLM? You can also try removing power from both the ISY and PLM then power up the PLM, wait about 10 seconds then power up the ISY.

It's possible that there's a communications issue with the leak sensor. Being that they usually sit down low the RF signal may not be reaching a dual band device. Try plugging in a range extender, on/off module, or a lamplinc module close to the sensor to see if that resolves the problem. The heartbeat status will usually show as on in the ISY and is not a indication that your heartbeat signal is always being received

to get the current UI go to this address http://forum.universal-devices.com/topic/18585-release-446-is-now-official/ First delete your Java cache and applications then scroll down to paragraph #4 and select option A. Did you Delete the Remotelinc from the ISY and then reinstall it after you updated your UI?

The Remotelinc can only be added to a scene as a controller, it is never a responder. As Stu suggested, update your UI to 4.4.6 Delete the Remotelinc from the ISY, then do a factory reset on the Remotelinc. Be sure the battery is fully charged. Make sure you're within range of a dual band device, put the Remotelinc into the linking mode, then enter its address into the ISY under linking management, new Insteon device and hit enter. Once it's installed in the ISY you can add it to a scene.

It's also possible that as your timer program executes you're dropping a few clock cycles.

It's possible that if you're running a lot of programs or queries that it could effect your timer. There's no other option that I know of that would give you a more accurate count.

You could append the button letter to the name i.e. Room Light (a), etc.

Nor sure if this is what you're looking for but the order of the buttons is A B C D E F G H

The access points provide better RF coverage than a KPL or other wall mounted switch because the antenna is not obstructed. Other devices which provide the same benefits as access points are the dual band ON/OFF modules and the dual band LampLinc modules. If you have any RF only devices, such as motion sensors, door sensors etc, then you'll probably benefit from having externally mounted dual band devices.

That option doesn't exist. The device heartbeat is preprogramed to be sent every 24 hours. (the hidden door sensor, 2845-222, does have the option to set the heartbeat interval) If you're still having battery issues or if the heartbeat is being sent multiple times within a 24 hour period and the factory reset didn't help then you probably have a defective device.

Perhaps a factory reset might help?? 1) Remove battery and wait at least 15 seconds 2) Press and hold set button on Open/Close Sensor while reinstalling battery 3) 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

You might want to take the CLEAR node out of your equation / program. You can also try to query a node, such as low battery, to reset it. I'm not 100% sure but I believe the Clear node is a AL CLEAR signal which is sent once a triggered node is back to its normal state You can also add the ${sys.node.#.name} variable to your email notification body. This will tell you which node is triggering your email.

The keypadlinc that shows up as a 5 button is actually the 6 button keypadlinc. To remove the device from the ISY right click on it then click on DELETE. It's strange that it installed as a 5 button unless it was previously configured as a 6 button KPL. Is this a new KPL or a used KPL? (The 8 button and 6 button KPL's can be reconfigured to either 6 or 8 buttons). You should probably do a factory reset on the KPL before you reinstall it.

Try putting the sensors into linking mode, only one at a time, then do a restore device. It's possible some of your PLM link records got corrupted. Be sure that the link mode has stopped before putting the next sensor into linking mode

Krusty66, Additionally, you should do a factory reset on both the dimmer and the remote to remove all the links between the two devices, then reinstall the devices via ISY linking. This insures that the ISY is a participant in any commands issued from either the remote or the dimmer. When you have a scene all the devices within the scene know what the state is. Also a scene resides in the PLM not the ISY, this allows the scene to execute even if the ISY is off line. If you're using a remotelinc in the 4 button mode then you'll have bright / dim functions by pressing either the left or right buttons from the pair included in your scene.

How do you currently have the remote controlling the dimmer? It has to be either a scene or a program.

Put the remote and the Dimmer switch into a scene, both as controllers, the correct status will then be reflected on both the dimmer and in the ISY. Was the remote linked using the ISY linking?, if not it should be.

can you post a screen shot of the email configuration you're trying to use. Be sure to obscure your email address / password before posting.