hart2hart

If I recall correctly, the ISY send a scene command and expects all associated devices to get and process it. For critical lights, I wait a few seconds in program and then send an off command to the switch that actually controls the load(light) to ensure it is off. The device command vs scene command has built in retry logic.

You send reboot ISY relay command to nodelink . I don’t know what it actually sends to ISY. I assumed it was a REST command but not sure. I’ll edit prior post.

If you added zwave devices, wait for other advice as I’m less than a novice with them. Otherwise,Restore your last 5.0.16C backup. Factory reset the devices you’ve added and ten add them again including any scene setup. You will need to recreate any new programs so copy them into a text document to make it easy to create them.

I used new feature of nodelink that sends via relay a reboot ISY command. I save the value of DST in a variable. When the saved value does not equal the current value. I just reboot ISY. This prevents me from having to remember to add programs that have the time change Sensitivity. I’ve been doing same manually for years. I’ve got run at startup on all programs to ensure they set heartbeat etc in motion.

Do you have another power supply? If not, do you have a multimeter to test voltage of current PS? I’ve seen voltage be enough to get small bit of led activity but not enough to power full devices. Not specific to Polisy.

Try taking out the “and status is off section” out and see if it turns on all 3 lights. The first set to 40% makes the if condition no longer true. I thought it would be atomic transaction unless it hit a wait but worth trying. As a simple test select the program and select run then.

I’ve used the same method and don’t necessarily disagree. Just know if any of the conditions that caused the currently running Then or Else path change, the program will reevaluate and may stop or take the other path depending on values. To OP posting a copy of program may be useful.

Most likely communication issue from ISY to the lights instead of program steps being skipped. You can post program. Test turning Lights off and on from the admin console.

Smarthome show them in stock if you want another spare.

Deleted.

What do you mean by rogue? How old is it? Does it beep and flash on and off? That kinda rogue was a failing keypadlinc that I tried restore and factory reset and it would work a couple days before doing same again. I later learned it was likely failing power supply capacitors in older versions that were prone to failure.

At some point you’re going to have/need to go to some version of 5. My thought is do it while conversion is still fresh knowledge. The longer you wait, the staler information will become. I wrote a how to guide to get from 4.7 to 5.0.15 or 5.0.16 that’s on here somewhere. The very conservative planning going into creating that guide was far more time consuming than actually executing it. 2ish hours depending on how many zwave devices you have. I’d go to 5.3 but have issues with schlage deadbolts and 500 zwave. I’m contemplating replacing locks with their zwave+ versions and trying again in next month or two. It offers the future of HA.

Not aimed at anyone... but In totality, this thread could be used as basis for a HA Saturday Night live script. [emoji1787] Assuming SmartHome does remain in business, I far prefer the dual mesh of Insteon for lighting by far. It was the only reasonable choice when moved from X10 11ish years ago. The scenes and keypadlincs are icing on that cake. I’ve helped friends with far more expensive setups and they had nothing on a well developed Insteon dual mesh. UD is by far one of the top tier firms I’ve ever dealt with and it starts at top with Michel. The ISY made Insteon possible for large installations. It served as the foundation and was recommended by SH sales when I started with my then new house under construction. It’s overall capability is fantastic and yes i support the need to abstract out all protocols and have them talk to a core database with Polisy. One example I always mention... Can you imagine replacing a switch in a sophisticated 10 device Insteon scene without it? I have whole house surge protector and have only had a handful of device failures. I have replaced many single band with dual band devices after 50 % off sales. Still got big box of working single band devices. Keypadlincs and iolincs were issues and a few dimmers. At some point electronic updates made them reliable. I replaced one keypadlinc 4 or 5 times in two years. Had 1 plm go bad. I’ve got a large stash of all Insteon devices from last 50% sale. Spare ISY and two spare plms plus one that I rebuilt. If you want to use any of these technologies, I always suggest having many spares on hand but that’s just me. Peace out!

From what you’ve told us, I agree that it sounds like the hot and neutral come into that switch box you most recently posted and it has the wires that run to the fixture. You might can replace that box with an extra deep box or consider a dual gang box and cover second half via front plate with one side covered.

Thought you said there were two switches. Only one photo or do they look the same? The difference is where power enters circuit at one of switch locations or at the fixture. You have to account for sense wires to use the existing switches.

What does other switch look like. How is is it wired?

There are multiple ways to wire a 3 way circuit. o power enters one of switches o power enters at light fixture What does other switch location look like? Is your goal to use micro module with existing manual switches or to replaces switches with Insteon dimmers?

It depends on how you use the variables but yes it can. Feel free to post what you need and we can take a look and provide feedback.

Please forgive if I’m missing something more involved for keypad buttons but... I create a scene, add a lamplinc (could be anything) as a controller, add a button on a keypadlinc as a controller and add a button on a remotelinc as a controller. If I press the button on the keypadlinc it lights up and the lamplinc comes on. If I press button on remotelinc depending on type (4 device will come on with on button or off with off button) (8 device toggle version will toggle based on what it’s last known state but within two presses turn lamplinc opposite of what it is). The kepadlinc button and lamplinc stay in sync. You can press buttons on lamplinc and keypadlinc button will follow. The top and bottom late button are a dimmer or a switch and act as such on 6 button version. On the 8 button version, The A button is a toggle for one light but the load wire can be capped and it will act like the others. When using a 6 button to control a ceiling light and fan there are very specific instructions to follow so it moves fan between off low medium and high which are a bit convoluted but it’s documented and works great. I added a program so fan off button turn fan off and then it goes off instead of being on to indicate the fan is off. ...But that’s my preference. What am I missing so I can help. Are you wanting/needing the button beside each other to be one for on and the other for off?

I had the same reaction initially. I now believe UDI is attempting to abstract out direct interaction with all specific HA protocols (Insteon , zwave, zigbee, IP, etc) into nodeservers that interact with device and scene nodes within the Polisy for common functions like programs etc. this provides a foundation to add more protocols and isolate differences without ending up with complex spaghetti coding Smart labs has become more and more difficult to obtain information from to support their Insteon protocol. Therefore UD seems to be saying they will support what exists now and more assuming smartlabs communicates needed information. Not an expert just my hypothesis based on reading here. Obviously only UDI and someone like [mention]Michel Kohanim [/mention] can confirm deny or defer until more is know.

We were both just stating same in different terms on first item. I’m was not aware of repeats exceptions but I don’t use them often. Thanks.

Thanks so much. I just completed the process of moving to a new 16GB Industrial grade SanDisk card. Hopefully, this was good preventative maintenance that will get me to the new era when as it appears Insteon may be a NodeServer on the POLISY. I followed the instructions in the wikis and did not format the SD card and all is back. The username and password, timezone, and email server were reset to default which I think is because The ISY asked if I wanted to replaced the current config with the new config and since both were the same, I said yes. I have a strong feeling that If I'd said No then the 3 items that went back to default would have remained at correct values. Thanks @Michel Kohanim and team as always.

[mention]Michel Kohanim [/mention] I know we have beat this to death but which is correct? Direct from the wiki: “SKIP if a new SD Card Format the SD Card - you do NOT' have to format the SD Card if it's new Telnet To Your ISY Login with the admin password Issue "FS" to format the SD Card, answer the "Are you sure question" with an upper case "Y" Please note: the ISY works with both FAT 16/32, but FS function formats it specifically for use with ISY with some performance improvements so its preferred you use this method.” The wiki appears to contradict itself. It says “SKIP if a new SD Card” and “FS function formats it specifically for use with ISY with some performance improvements so its preferred you use this method.”

[mention]Teken [/mention] I ordered a second card of exact same size and brand to test the clone hypothesis.

Which in OP post the else clause is empty so outward appearance is that it stops. It will finish execution of statement in process with the exception of the Wait statement.