Techman

You should also make sure you have a stable power source. If your area has frequent black outs, brown outs, etc then you should first look into a whole house power line filter as power line surges can reek havoc on electronics.

The ISY log will show if a device has changed its status, it doesn't log if a program ran. The program summary shows when the program last ran and when it's scheduled to run again. If the program summary shows that the program ran then the problem is either with communications or the PLM. Being that the scenes reside in the PLM and assuming that you have no other issues controlling devices then I would focus on the PLM, power line interference around the time the program ran or if you have multiple programs running at the same time then they should be separated by 10 seconds or so to avoid collisions. Does your ISY log show any other activity about the time your program was supposed to turn off the lights?

The log would show that the program ran telling the scene to perform but there's no way to know if the scene actually triggered. Another possibility is that there's interference on the power line around the time the scene is supposed to turn off the devices. Most of the older PLMs fail around the two year mark. Sometimes they become intermittent before that completely fail. This is usually due to defective capacitors. Is the green led on the PLM lit?, if not then there's an issue with the PLM.

MustangChris04 The scenes reside in the PLM, not in the ISY. It's possible that the PLM is starting to fail. The ISY logs will not show the status of a scene, only the status of the devices in the scene. How old is the PLM, and what is its firmware version Try running a scene test for the scene that is at issue.

Assuming that you have a single band PLM and that the restore modem fails then you would most likely benefit from a new dual band modem which also has the latest firmware release.

gadgefreak, how old is your PLM. If It's more than 2 years old it's possible that it's starting to fail and needs to be replaced.

Certainly strange, probably best to go ahead and order another KPL so you'll have something to compare it with.

Try the yellow filter it will defuse the light without adding much in the way of color

The heartbeat signal is also available in the ISY log. You can also write simple program to notify you if a heartbeat signal is missed.

If the keypad button leds are too bright at the lowest setting you might want to try replacing the clear plastic lens behind the button with a yellow or blue lens take a look at this link http://www.smarthome.com/insteon-2401l-led-color-change-kit-for-keypadlinc-4-color.html

In the future you don't have to delete a device in order t rename it, just right click and rename. This will also update any programs the device is in.

With the power disconnected, try removing and replacing the memory card. If that doesn't help then I would suggest submitting a trouble ticket to UDI and let them troubleshoot it.

I would try to measure the voltage at the plug end of the power adapter to make sure you that you're actually getting power to the ISY.

Hi Gary, Take a look at this topic. I'm currently using the ISY network module to control some of the Grace tuner's basic functions. http://forum.universal-devices.com/topic/8346-upnp-help-grace-digital-media-player/ Techman

Sounds like you may have gotten a unit that someone returned. It's highly unlikely that the unit was originally shipped without the card

when you boot up the ISY what leds are lit on the front? Is the RED led on the front panel blinking?

I had also been playing with the sensor contacts. Today I'll leave it alone and just monitor the heartbeat. Seems the heartbeat only sends an "ON" signal and the state of the contacts has no bearing. I had problem with my SD card in the ISY which may have interfered with the previous heartbeats. I cleaned the contacts on the card and reinserted it. The ISY is now functioning normally. Prior to reseating the card I had trouble accessing the ISY and I had a few programs that got corrupted. In retrospect I guess we really don't need software access to the "closed" node. That node could theoretically be removed from the ISY.

I just got a heartbeat signal, 25 hours and 15 minutes after the last one. I guess we just need a way to access the Closed node via the ISY.

That's good news. Let me know what you get tomorrow. Did your sensor also install as a 2421 triggerlinc? Does your "closed" node populate?

I also got a heatbeat "on" signal the first time I inserted the battery. That was the last time I got one. I have good communication as the "open" node works flawlessly. UPDATE: I just got a hearbeat "ON" signal. Unfortunately I was playing with the magnet just about the same time as the heartbeat arrived so I don't know if that had a bearing on anything. Guess I have to wait another 24 hours to see what happens.

I'm not getting a heartbeat signal, how about you?

You should also take a look at the furnace to see what terminals the wires are connected to Is your air conditioning a single stage or two stage compressor? Does the furnace have a two stage gas valve? Do you have an external temperature sensor that was connected to the Honeywell?

I'm still testing the current firmware release, so I don't have anything to report yet. . The status of the contacts on the sensor shouldn't have an effect on the heartbeat node. The heartbeat should report regardless of the state of the open/close node.

What you have is a failure to communicate. I would start with the PLM and replace it was a dual band PLM. You also need to focus on something that may be creating noise on your powerline

You should be able to work around that issue with a program.