IndyMike

No experience with Velux or the interfaces. However, a post on the HA forum indicates that the KLF 200 can handle far more than 5 devices. I'd say clarification from the manufacturer would be in order: VELUX America LLC 1-800-88-VELUX https://community.home-assistant.io/t/how-to-control-io-homecontrol-velux-devices-blinds-somfy/88917/3 Please do post back with anything you learn. Others will have the same questions.

Sorry, I'm not going to try to re-quote 10+ years of history. Search the forum's

To the best of my knowledge, Smartlabs HAS NOT removed the all-on command from current PLM's. They are still capable of sending the command (it is a valid command). Smartlabs HAS removed the all-on command from some of the newer Insteon modules. To the best of my knowledge, the IOLinc is STILL SUSCEPTIBLE to the all-on command. The ISY can still send an all-on command if you wish to test your devices. Navigate to the "My Lighting" item in the Admin Console Tree and you will see the all on at the bottom of the window. This will execute the group all on command. Devices that do not respond have been "fixed" or can't hear the communication. Devices that do respond are susceptible. Most of the issues with all on events seem to involve motion sensors, keypads, or devices that trigger programs that talk beck to the same device. I'm not aware of any specific Alexa issues (but then i don't use Alexa). The wiki mitigation posted above works reasonably well. There are Many posts on the forum. Try searching "site:"forum.universal-devices.com" all-on event" Best of luck.

Any error lights on the 994? You may want to remove and check your Sdcard (plug it into a windows machine and check for errors). If you find errors, I would highly recommend replacing the card. You can try a "repair" via windows, but I'd consider that a stopgap. Procedure for replacement is in appendix 😄 of the ISY994 users guide: https://docs.universal-devices.com/production/ISY User Guide 4.2.8.pdf

Sorry, thought you were still using the ISY994. I don't know what format the SSD uses. There are posts on how to re-flash the SSD: https://forum.universal-devices.com/topic/42174-polisy-ssd-image-restore-process-for-a-corrupt-ssd/. I also don't know if the EISY can read the information on the SSD. I would try a mSata to USB adapter and a PC first to see if it registers.

@apostolakisl, that's rough. Sorry to hear. My only comment(s) would be - check the power supply to see if it fried, and check the SDcard for corruption. Two easy ways to recover your configuration.

You can view the programs in a backup. Identifying a specific program and restoring it is rather painful. Copy one of your backups to a separate directory in case things go bad. The 1st screenshot below is the result of an UnZip of one of my backups. Use 7Zip or something similar to open your backup .Zip. Windows explorer will NOT work. You will see the file "uuid.xx.xx.xx.xx.xx.xx.zip". Unzip this to your directory. Open the "uuid.xx.xx.xx.xx.xx.xx.zip" file in 7Zip as well. Extract the CONF folder. Within the CONF folder you will find a D2D folder. This contains your program files. The "*.PGM" files are in XML format. Your challenge will be to identify which file you want to restore (not easy). You can export your current programs to try to determine the program numbering (ID) and what is missing. Beware that Exporting the entire "My Programs Folder" produces an XML file that can't be interrogated by any XML viewer that I have found (format error). I have been successful in exporting individual program folders (non-nested). I'm quite sure this is not the answer you were hoping for. Unfortunately, it's all I can offer. Directory showing Backup Zip, UUID Zip, and CONF file folder CONF Folder contents: D2D Folder Containing Program Files 000A.PGM Contents

As indicated above, the Zen32 does not send ON/OFF commands. Instead it sends "keypressed" events. The ISY appears to be interpreting the "keypressed" event as an "ON" event. Said differently, the ZEN32 will not send an OFF as interpreted by the ISY. You can still use programs and variable to interpret the successive "ON" events: {on program} if 'ZEND32 Button 2' is switched on and $ivar = 0 {0 = off} then {turn devices on} set $ivar = 1 {1 = on} {Off program} if 'ZEND32 Button 2' is switched on and $ivar = 1 {1 = on} then {turn devices off} set $ivar = 0 {0 = off}

@Techowl, I'm in agreement with @Brian H. It sounds like you have a device that is radiating signal @310 MHz and is effectively jamming your transceivers. If it is a device that is failing (oscillating) it will not be transmitting the proper X10 format and will be ignored by the transceivers - you won't see any events. You have a couple of tools at your disposal - 1) The tried and true circuit breaker approach. Turn off circuits until the noise stops (communication improves), then isolate devices on the circuit. 2) Use your transceiver to determine where the noise source isn't. Move the transceiver around the house to find an area where the remote range improves. Then reverse the process to find where the range is worst (noise source nearby). It is of course possible that the noise source is outside your home. The breaker test would confirm that.

@rwsani99, Your log from the "show device links" is showing evidence of communication timeouts (no-response from the target device). If things were working properly, you would see a "[INST-SRX ] 02 50 4E.7D.16 71.17.44 XXXXX" after the [INST-ACK}. In the above, the PLM is re-trying communications up to 5x per request, and the ISY is re-trying 3x (15x total). That's rather bad. Since you indicated that you are having issues with multiple devices, I'm am going to guess that you have a rather strong noise source near the PLM. I say near the PLM because you are having problems with multiple devices. I am guessing that it's a noise source, rather than a signal absorber, because it's rather intermittent. Your second log section showed sections of total failure, followed by rather good communication (hops remaining = 2). Inspect the circuit where the PLM is installed for problem items (Pc's, UPS, Printers, etc). Alternatively, you could try moving the PLM to another circuit. Let us know how things are progressing

@alixer, when you performed the "restore device", was the ISY able to complete write the link table (no errors)? If this is the case, then your device has the correct PLM address and the scene information is incorrect. I say this because newer devices (I2CS units produced after 2012) will not allow the ISY to read/write to them unless the PLM address is in their link table. It may still be helpful is you could post your device link table, ISY device link table, and PLM address. The membership tree on the right is also helpful since it shows how many scenes the device is associated with. If your link table compare looks similar to mine above (no missing or mismatched entries) then the ISY believes the device has the correct link table/scene information. If the device does not respond correctly to a scene command (assuming that it received the command), then the ISY Link Table for the device is incorrect. The ISY maintains link tables for each Insteon device and for some reason, yours may have been corrupted. You can correct this by manipulating the device settings within the scene, causing a re-write to the device (as you are doing) OR your can restore the ISY from backup. Obviously, the backup may also have incorrect information, or be missing information on your more recent devices. If you do choose to restore a ISY backup, please follow with the process that @lilyoyo1 outlined above.

That's unfortunate. It indicates that the ISY does not have the correct scene information. You could try installing an ISY backup (restore ISY, restore modem, restore devices) , but that may be more work than "refreshing" you scene devices.

To be clear, my system failure was two fold: Poor programming on my part that led to a program cycling the system on/off causing water hammer. Poor irrigation design causing excessive main pipe flow (erosion). Pipe erosion occurs when you have large zones (high flow) and a capable supply. It's not that hard to avoid as long and you understand the pressures and flows in your system. I found the following site helpful. It includes spreadsheets for calculation pressure loss (friction) in various types of irrigation plumping. For reference, I was just below 7 ft/sec in my system mainline with certain zones operating. https://www.irrigationtutorials.com/#gsc.tab=0

It sounds like your new PLM address did not get written to your older devices. Not quite sure why. When you adjust the parameters of scene devices you are re-writing the scene AND the PLM address. That's why things work properly after the update. I can understand why you wouldn't want to do this for all of your scenes - you probably have a life. Could you try performing a Link Table Read/compare on one of your problem devices and posting the results? Please also post the new/old PLM address. This will tell us if the ISY contains the correct information. If it does, a simple "restore device" should correct the problem. If it doesn't, things get a bit more complicated...

@rwsani99, could you post a copy of the event viewer for when this occurs? There are a number of possible issues that could cause this (serious noise issues, PLM address change, PLM failure). Need to see the event viewer to determine which path to send you down.