msoileau

Thank you!!! I had another power supply handy and gave that a shot. Came right up. I had checked that the voltage was good, but it didn't occur to me to try a different supply

My plan is to swap out his zwave board with mine, and his SD card with mine. The only thing I'm not certain on is whether we were running the same firmware. Would this be a problem if we were not, or is the firmware loaded completely from the SD?

My faithful ISY has died after many many years of service. I have a friend that recently migrated away from ISY and I can use his to replace my dead one. Is there a procedure anywhere that I can follow to replace it? I would assume basically follow the SD card replacement procedure, but use the SD card from my old ISY? The dead ISY has the blue LED on power, but I have no network activity. I have cloned the SD card using dd, and everything seems good with the SD card. It really does appear that the ISY is just dead for some reason

Ah. After changing init from "0" to "GV2", I had to delete the nodeserver and recreate it. Now it is working correctly. Thanks!

I'm not following. Originally I had the init set to "0" but I've changed it to one of the status values and I still have the issue. Here is my nodedef: <nodeDefs> <nodeDef id="controller" nls="ctl"> <editors /> <sts> <st id="ST" editor="bool" /> <st id="GV1" editor="I_DEBUG" /> <st id="GV3" editor="EN_ST" /> <st id="GV2" editor="ZONE_STATUS" /> </sts> <cmds> <sends> <!-- These are for our heartbeat --> <cmd id="DON" /> <cmd id="DOF" /> </sends> <accepts> <cmd id="SET_DM"> <p id="" editor="I_DEBUG" init="GV1" /> </cmd> <cmd id="SET_ZONE"> <p id="" editor="ZONE_STATUS" init="GV2"/> </cmd> <cmd id="QUERY" /> <cmd id="ENABLE" /> <cmd id="DISABLE" /> <cmd id="STOP_ALL" /> </accepts> </cmds> </nodeDef> </nodeDefs>

While working on a custom node server, I noticed that I was unable to use my node server in UD Mobile (Android) even though everything looked OK on the admin console. I then tried to bring up another node server and received a similar error. I've tried rebooting the ISY and then performing a sync on UD Mobile. I cleared all data on the app, rebooted ISY, and did a discover. Same error. java.lang.Error: Node Status Relation Cursor is empty. NodeId: 824. Control:30. 500 On my custom node server, I see similar, just different nodeid and control I guess it's possible that both me and the other developer are making the same mistake?

Does this new ceiling fan have new LED lights? I've had issues with Insteon communication with certain LED bulbs, particularly some of the older Cree bulbs

The assistant-relay works very well. You can broadcast custom messages (TTS) as well as a few preset messages. Any music playing is resumed after the broadcast notification. The interface is easy to use via network resources. Unfortunately I have only been able to get it working under Windows so it is not something that I can leave on all the time.

You might also try removing/turning off LED bulbs. I've had multiple instances of noise from Cree LED bulbs causing the PLM/ISY to log X10 commands. Turning off the light would clear up the problems.

I guess that was the problem. I was too lazy to walk upstairs and across the house so I was trying to test by sending a Fast Off from the ISY. Didn't occur to me that it only worked when initiated at the device itself. Is there any way to capture a remotely activated Fast Off for use in this program, or is my best option to just manually run the "Then" block instead of triggering the Fast Off

I'm unable to get any of the Control functions to properly trigger a program. I'm attempting to use a ToggleLinc Dimmer (2466DW). Here is what I'm currently trying: If Control 'H.Room / H.Light' is switched Fast Off Then Set 'H.Room / H.Light' 50% Wait 10 minutes Set 'H.Room / H.Light' 25% Wait 5 minutes Set 'H.Room / H.Light' Off Else - No Actions - (To add one, press 'Action') From the Event Viewer, I see the Fast Off notification going to the ToggleLinc, however I never notice my program fire. I've tried just standard On or Off as well as Fast On. Status events seem to work, but I want to capture a Fast Off. Anyone have any suggestions? Thanks!