RDoc

I recently migrated from an ISY994i to eisy with Insteon and Z-Wave devices. As part of this the Z-Wave devices' ids got changed from "ZWxxx" to "ZYxxx", for example "ZW016_002_1" to "ZY016_002_1". The new "groups" (formerly "scenes") now contain the original members with the "ZWxxx" command entries and new entries for "ZYxxx" but only as default entries so they all have to be edited to change to the correct commands. Unfortunately the commands are lost so there's no obvious way to set the new commands to the correct values. There also is no way I can see to remove the old no longer valid entry although it doesn't seem to create problems.

I finally got these devices to work, although I'm not sure exactly how. It seems to be a combination of Restore Device rapidly followed by Write Changes, or something like that. Apparently the communication link was there but for some reason both ends weren't communicating over it. Some variation of a deadly embrace? If it were me, I'd put some effort into figuring out how the com link gets hung like that. Thanks everyone for the suggestions and encouragement.

Unfortunately the log looks like there is an error. events-2026-11-10T22-32-21.csv

Thanks for the replies. I tried that early on with no change. I'm getting a new USB PLM to see if that makes any difference.

Techman: I tried that an there's no change. I also listed the PLM links and the links to the failed node devices are in the PLM list. I also tried manually switching the light on and when I did a query on the switch in the eisy-ui it correctly showed the switch as on. However, when I tried turning it off in the eisy-ui I got the same note failure and it didn't turn off. It seems to be connected and can be queried but the EISY can't control it.

I migrated from an ISY994i with both Insteon and Z-Wave devices that all worked fine in the 994i, to an EISY after saving the Z-Wave and ISY backups and loading them into the EISY. Some of the Insteon switches work, but most don't. In one case there are two identical switches side by side on the same power line, one works, the other shows a node error. I have a mixture of different types of Insteon devices and there seems to be no pattern in which work and which don't. The Z-wave devices seem to work on the EISY although I've only played with a few. I'm using a the same serial PLM I used on the 994i and can go back from the EISY to the 994i with everything plugged in exactly the same way in both, reload the same backup file into the 994i I used on the EISY and everything works perfectly, Insteon and Z-Wave. Returning to the EISY setup, it behaves the same. Some Insteon devices work, most don't. I've tried doing multiple Query and Write Changes to the devices with no improvement. All the packages are shown as the current versions. I tried upgrading to the Beta version 1.4.8 and it's mostly the same although one switch that didn't work in 1.4.6 now works in 1.4.8. Most Insteon devices still don't work. I'm using an Ethernet connection for both the 994i and EISY. This is from the About page. UUID 00:21:b9:f2:72:43 OS Version 14.4-RELEASE-p6 Node.js v24.16.0 Memory 20% 1.5 GB / 7.7 GB Storage 5% 4.2 GB / 91.0 GB

This is getting silly and I'm not here to argue. For anyone who actually wants to have a way to turn on and off a block of debugging lines, just enclose them in a Repeat block as shown. Personally, I use a debug flag variable as shown in the first example with Repeat While so you can turn on and off debugging code in a program just by changing the debug flag variable manually from 0 to 1. However, if you just want a simpler and somewhat safer way to stop execution of a block of lines, the Repeat For 0 method will do it. To let the code lines run again, just remove the Repeat for 0 line(s). Then $A_Debug_V0 = -5 $A_Debug_V1 = -100 Repeat 0 times <== Don't let the code up to the next Repeat run. To let all the code execute, remove this line. $A_Debug_V0 = 5 <== This line (and any other lines in the Repeat block) won't run if it's Repeat 0. Repeat 1 times <== When you are letting all the code execute you can remove this line too. $A_Debug_V1 = 100 Note for more advanced use where you want to have the same debug flag work in multiple programs: (Ignore all this if you just are working in a single program) I strongly suggest not using the same pseudo local variable (AW_Debug) in more than one program because it's still a global variable (there are no real local variables). You can use the same debug flag variable (A_Debug_Flag) in multiple programs as long as you only read the value, not change it programmatically.

@MrBill: Good point. ZW Test - [ID 002D][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $A_Debug_V0 = -5 $A_Debug_V1 = -100 $AW_Debug = $A_Debug_Flag Repeat While $AW_Debug is 1 $A_Debug_V0 = 5 $AW_Debug = 0 Repeat 1 times $A_Debug_V1 = 100 Else - No Actions - (To add one, press 'Action')

@larryllixDid you read the OP? The question was how to comment out debug code. There is no way to do that directly. However, by using a conditional block and flag variables as shown, the code can remain in place and be easily switched on and off. A simpler but less flexible method is to use a Repeat for 0 block. Unfortunately, you can't use a variable for the repeat count. If the Repeat count is 0 A_Debug_0 winds up -5 If the Repeat count is 1 A_Debug_0 winds up 5 I disagree that copy to clipboard produces a more readable code block and you can't paste code into programs anyway.

You might try using a repeat command as a conditional block. In this example if A_Debug_Flag is 1, A_Debug_V0 winds up as 5 if A_Debug_Flag is not 1, A_Debug_V0 winds up as -5 In both cases A_Debug_V1 winds up as 100. AW_Debug is treated as a local variable used to end the Repeat without having to change A_Debug_Flag so the program can be run the same way more than once.

I wanted to temporarily stop using a zwave device so set it to disabled in the Main menu, which showed it disabled. However, when I attempted to update the other zwave devices' links with Repair Links, the ISY went into a loop attempting to update the disabled device forever. I had to reset the ISY to stop the messages, but the next time I did an update it restarted. The only way to permanently stop the messages was to use the zwave command to remove failed device. This is pretty user unfriendly behavior. I'm on V5.3.4

I've just started playing with a couple of these. When installed in the ISY it creates about 24 devices, but I'm only interested in the Dimmer Switch devices numbered .2 - .5. To make all this a bit more organized I created a folder and stuffed all the devices into them. These can be programmed as independent dimmers for 12-24V up to 6A load max per channel, 10A total load on all together. For driving LED's that's a fair bit. The output terminals are labeled R, G, B, W with R Dimmer #.2, G Dimmer #.3, etc. I was able to control my particular led strip light down to 1.5 percent To set parameters use the first device "Multilevel Switch". I set parameter 152, the hub controlled ramp rate. This seems a bit wonky, the set button keeps pulsing for a long time but it seems to work OK in the end.

I just added a Minoston remote switch MR40Z to my mixed Insteon/Z Wave system. Unfortunately, there is essentially no documentation so I have no idea if I'm using it's full potential. However, it works fine. It can emit on, fast on, fade start, and fade stop on the buttons, and seems to have a battery status that's readable. I suspect the range isn't great, my other Minoston devices have very limited range, but I've got some Aeotec repeaters around so it works very well.

These Minoston plugs work fine but the radio section isn't very powerful. I added some dedicated aeotec range extenders and everything works very well now.

Can the isy994i update z-wave device firmware? I'm not asking about the firmware in the 994i itself, rather the firmware in the z-wave device, e.g. a z-wave switch.