MrBill

You can also open a ticket: support@universal-devices.com They are fast and amazing!

When you click the device in the device tree is the device type showing correctly in the right window? It's shown with the device address on the very second line of the right window just under the large type device name. I'd try holding the button for even longer, it does sound like the device needs a factory reset. Finally open the Tools > diagnostics > Event Viewer window and set the level dropdown to level 3, then turn the switch on and off using the admin console, and try the local button so see if it's trying to send anything even if the button doesn't work to toggle the load. If you need help reading event view output post it here and someone will help interpret..likely someone other than me, I'm not a good Event Viewer reader, but others here are.

Now that you have your system working again please upgrade from 5.0.16A. I'm assuming you don't have any z-wave, if that's the case go to 5.3.4 If you do have z-wave check the version.... 4.55.00 upgrade to 5.0.16c and don't upgrade to further firmware. 5.0.16c is a very stable release. If the z-wave version is 6.81 then once again 5.3.4. In any of the 3 cases, the update should take half hour or less of your time. Backup, load the revised firmware, wait for the reboot, you're done... there is no adjustments needed to upgrade from 5.0.16A to either of the above.

The important think to understand about link counting is that ANY Insteon traffic that occurs during the link count will destroy the link count. The resulting count can be way too low or way too high. In a system that's all switches it's easy to avoid other traffic... do the count will no one else is home and don't turn anything on or off. In system's with battery devices... it's a bit more difficult... motion and heartbeats in particular. To verify that the link count is valid run the link count repeatedly until you've obtained the same number more than once.

I'd bet on the left label being the actual address since it's obviously Hexadecimal, but that's confusing for sure. You can always try both. Also try factory reset. There's no difference in the Insteon devices different ISY models can control, it's compatible.

I agree with @brians for troubleshooting steps. It seems like this pair should be working but perhaps search for the variable in all your programs to see if something you've forgotten exists is also setting it. to use Find, right click any programs name and pick Find.

To make a wait complete even if the criteria changes it's possible to use two programs Program One If $sVariable = 1 then Run Program Two (then) else (none) ---- Program Two If (none) then Disable Program One Wait (however long) (Do whatever must be done) Enable Program One else (none) In this scenario the wait will complete, even if sVariable changes while waiting.

You could also create a new folder under "my programs" and move everything currently under My Programs to the new folder. Put the folder condition on that folder instead. Then you could add a single program Run at startup, No If, and a then that waits 10 minutes, then sets the debug variable to 0. That would give a 10 minute delay then start programs in case of unattended startup.

I've gotten out of the infinite loop issue before using a folder condition on "My Programs". Create a condition that will never be true..... I use $cTrue = $cFalse but if you don't already have those variables pick any variable that you do have and do something like $iVariable = -99999999... or pick a switch that won't be used and compare it to any condition. Then Save Programs. As I recall the first time the folder condition just disappeared during the save, but I tried again and that time it worked.

I disagree, honestly I don't think I'd give that assignment as a first step to a new homeowner with a working system. It's a great suggestion for someone starting with an empty ISY... update it and upgrade it before you start building. But to tell someone unfamiliar with the ISY ecosystem to jump in and upgrade the system as their first step is a mistake. The first things they should do is learn about the system, how to start the admin console, learn about the devices in there device tree, study the programs in their program tree. Learn how to backup. After they have the basic understanding of how things work, then the upgrading process can begin. My fear of telling a new homeowner to jump in with a firmware upgrade is that they'll end up not understanding what's happening, then they'll end up factory resettng and won't have a good backup.....etc etc.. New homeowners with an existing system should learn to crawl, walk, and then run.... once they have then they should start the advanced topics.

Network resources fire out of the ISY immediately. Not sure what you've got going in the rPi side, but the delay has to be there.

The ISY does thrash around abit during startup,,, most errors right afterward are normal, but it should simmer down within about 10 minutes. Not everything in the error log is an error to be worried about, some entries are more informational. After you reboot the ISY, I'd give it 10 minutes before you try and open the admin console-- let everything get up and running before adding the admin console subscription updates to the mix.

Sun 2022/03/20 06:53:18 PM System -5 Start Sun 2022/03/20 08:03:03 PM System -5 Start those are both places the ISY was rebooted. Did you cause those or did it do it on it's own? We are on the 22nd now? has it stabilized? or are you still having issues?

Yea i'm sure it will get worked out... i was going to move my system over to IoP about now, but based on forum reports I think i'll give it at least another 30 days.... re-evaluate at the point... I've got it running and it has a PLM for testing, but just not using it for 'production' yet.

so far I haven't seen the problem first hand. I do believe there is something, perhaps with IoP firmware causing an issue, and that is obviously a UDI problem and not an Echo issue. Via v5.3.4 on an ISY944 I've not had an issue... even rebooting ISY, which has happened many times in the last week as I've reconfigured and moved some things around to a new network closet I created.

That's an insult to UDI and specifically to @bmercier. I'm certain if there was a need to update the skill it would occur. Fan support was added at some point at least semi-recently, not sure about the time frame tho. @bmercier has always responded in a timely manner to any issue with the skill.

Any program that used "Adjust scene" will need manual repair. First verify that your admin console is matched to your firmware version via Help > About Once they are, open the "Programs" tab, select the "Summary" sub tab, Look for yellow. where ever you find it, the program needs manual attention... and probably used "Adjust Scene". This IS covered in the upgrade instructions.

you could always email sales@universal-devices.com and ask.

While the ISY994 will be around for a long time, if you're upgrading at this point I would move straight to Polisy. incidentally, you don't need to replace the ISY994 to get a ISY994i ZW PRO... just add the z-wave board and purchase the pro upgrade.... but I wouldn't spend my money that way either.... make the jump.

the above link posted while i was finding the other link to go with it: https://www.amazon.com/StarTech-com-Serial-adapter-DB-9-RJ-45/dp/B00006IRQA/

if you mean order one... good luck!

One issue is that upgrade and update, bring all packages up to date.... but the changes don't take effect until the service is restarted. The other day Michel's announcement included an isy restart, but in reality PG3 had updated also. so... either check version numbers to see what needs to be restarted... OR... reboot polisy.

As used here, it won't make much difference. There are use cases where one is more appropriate than the other, but in this case they are fairly interchangeable. That distinction existed in V4 as well.

If you have a 300 series z-wave board (z-wave version 4.55.00) you should upgrade the firmware to 5.0.16C) if you don't have z-wave or have a 500 series board (z-wave version 6.81.00) you should upgrade to firmware 5.3.4. You're current version is old and buggy, however that's likely not your problem... If your system was working for years, I suspect you either have a failing PLM or electrical noise...aka insteon signal blocking or signal sucking devices. Check this section of the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#INSTEON_2