walkman9999

I did. It went well for the most part, one powerline device didn't come back but I replaced it. Everything worked fine for about a week after the replacement.

Hello - Very reliable install went south a few weeks ago. Determined problem was a bad PLM. Replaced PLM and things went back to normal for about a week. Now I have a problem where when a scene is triggered, multiple devices that are not part of the scene are switched ON. This happens for two scenes in particular. Should note that these scenes have been part of my install for years. I thought maybe restore of the new PLM would help, but that ran into a "failed to write" error (see log: _restore-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.25.txt). I am able to download the links table, but not sure what it is telling me (file: PLM Links Table.v5.8.4__Wed 2025.02.12 16.57.37.xml). I also captured a log of the scene running and triggering the switchlinks that are not part of it (log: scene-trigger-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.49.txt). The programs are included as well, but I don't believe this is a programming problem - although I'm open-minded. One program has the IF and second one has the THEN. North Gate.v5.8.4__Wed 2025.02.12 16.59.01.iox -> _North Gate.v5.8.4__Wed 2025.02.12 16.59.16.iox Any help is appreciated. @IndyMike, you have been great at helping me understand the logs in the past. Maybe some insight? Thanks in any case. _restore-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.25.txt scene-trigger-ISY-Events-Log.v5.8.4__Wed 2025.02.12 16.46.49.txt PLM Links Table.v5.8.4__Wed 2025.02.12 16.57.37.xml North Gate.v5.8.4__Wed 2025.02.12 16.59.01.iox _North Gate.v5.8.4__Wed 2025.02.12 16.59.16.iox

This is very useful, TY! I've decided to replace the device with a dual-link model.

Hello - I have a previously working switchlink dimmer v.40 that will not accept updates from EISY. This occurred after PLM replacement, not sure if coincidence or not. I have tried hard reset. Logs are attached for an attempt to write to device, and separate log for attempt to restore device. Neither is successful, but it does seem to be some comms between EISY and the device (I think). Comms to other devices in same are seem to be healthy. Let me know if an more info needed to help diagnose. Any insight is appreciated. TY EDIT: attached log from device query _restore-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.12.35.txt _write-updates-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.13.38.txt _Query-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.28.42.txt

Thank you for the decode. Swapped out PLM and looking much better. I am having a problem with the link tables on two devices after the swap out, but working on troubleshooting and will post in new topic if needed.

Hi all, Existing install, having some intermittent problems that seem to point to PLM (device triggers do not reliably run programs all of a sudden, but comms see OK). The PLM shows connected and I can control devices using the admin console, but I cannot read the device links table from the PLM. I have a spare and am going to swap tomorrow. In the meantime, is there another test to check comms between the PLM and the EISY? TY

Tentative results seem to indicate that the the new KPL has solved the problem. There is still the matter of the other KPL that had similar symptoms, but that one is behaving lately. Acknowledging that there are some logical leaps that have to be taken to blame the KPL, but for now that is the conclusion. Thanks again @IndyMike for assist.

This is all great advice and there is a lot I can work with here. KPL is next (should be here in 5 days), and I'll put some of the easier things on this list into my "best practices" list. The workaround of writing until it "sticks" should make this operationally acceptable, especially since the switch and KPL commands seems to work fine for now and I don't change things often. Will report back on new KPL for closure. Really appreciate the knowledge transfer and targeted troubleshooting.

The electrical environment hasn't changed in any macro way, there is a chance that a new device has been plugged in outside of my control. Any suggestions for testing this theory? An unfriendly/noisy electrical environment seems difficult to fix. I have been considering purchasing a new KPL (if it doesn't help, having a spare seems like a good idea). Will post results of the swap once I receive it. Thanks for your continued input.

I am noticing that two other devices are having same problem (if I'm interpreting the logs correctly). Started yesterday with one of them (another KPL), and now today with a on/off switch (2477s). Logs are attached. The devices do write eventually, so far. Editing to add. During this fail to write event, controlling the device seems to work fine. I've attached second log showing comms during on/off. And, I can read device links tables from devices not affected without problems. ON-OFF-SWITCH-FAIL-ISY-Events-Log.v5.3.4__Thu 2024.05.23 08.14.47.txt ON-OFF-SUCCESS-ISY-Events-Log.v5.3.4__Thu 2024.05.23 08.23.31.txt

Thank you for the insight. This problem occurred when changing attributes to a scene that includes the KPL, but all comms to this KPL seem inconsistent (e.g. changing ramp rate also resulted in a comm failure, when I manually retried to write to device it was successful) Reading link table from the device was also problematic. First attempt retrieved 4 links and then failed. The second attempt (which is attached, along with comm log) failed entirely. I do not mind going thru process of factory reset/restore. Let me know if more testing would help before I do. Thanks again for taking a look. LINK-TABLE-READ - ISY-Events-Log.v5.3.4__Thu 2024.05.23 07.24.03.txt

Hi, I'm having sporadic problems with an existing/stable install. Two of my KPL devices are giving "failed to write" errors about 50% of the time. Subsequent attempts will often succeed (although sometimes it take a few). Other comms in network are fine. I've attached two logs, one with success and one with failure. Can anyone give insight? Edit: Should note: the KPLs work as expected as responders. TY NO-WORK-ISY-Events-Log.v5.3.4__Wed 2024.05.22 08.43.50.txt WORKS-ISY-Events-Log.v5.3.4__Wed 2024.05.22 08.44.42.txt

Hi I hope this is appropriate place to ask this question. I have an ISY99, but my question is about an Insteon device connected to it. I need an in-line solution for turning a device (fan) on and off. I had previously used an Insteon In-LineLinc Relay, but they are no longer available. Wondering if I can use a Micro Dimmer Switch Module and set the ramp rate to zero with the ISY. The fan is obviously not "dimmable".. Any pointers?

I can remove the device from the remote and pair with EISY. However, I then cannot pair with remote. I can remove/find in any order, but cannot pair to both devices. Looking at on-line z-wave reference docs, it looks like the primary controller need to "allow" the second controller. I'm at a crossroads, I do not want to give up the remote, it is the friendly way to control the blinds for guests, etc. And I do not want to give up EISY, but this seems to be the choice. Any EISY advice on "allowing" a secondary controller? Thanks

I would like to continue to use the remote though, is it possible to have the blinds paired to both?

Hello, I am relatively new to this technology I have a working ISY99 config that doesn't include z-wave support. I purchased and installed Bali blinds with z-wave connectivity and a new EISY with the z-wave module. When attempting to pair blinds with EISY, I go into connect mode and put blinds into include mode (terms may be off, but I push button on blinds to get them to try to join z-wave device), and EISY doesn't find them. I do the same with Bail remote and the blinds are found. I've tried moving EISY close to blinds to no effect. Am I missing something simple? Maybe blinds cannot pair to two devices? Any pointers are welcomed. Thank you.

Hello, Attempting to change (or add) user results in error message: "Retrieving /api/users (error returned)" After this happened I logged out and I cannot login. Error message "Access Denied" I don't think relevant, but recent upgrade of ISY to 5.3.4 Screenshots attached. Thanks for any info. :Mike

This is the answer. Clicking on the controller and choosing "Copy scene attributes from Low Hang" for each controller set things right. I think a few people had this idea and were presenting it to me in different ways, so would like to give everyone credit. Case closed. Thanks all!

I'm attempting to validate this, I think I'm following the suggestion correctly. Please see attached screenshots. When I click on the scene controller I can see that the device ("Kitchen Island") is a controller for the scene ("Low Hang") and that Kitchen Island is part of Low Hang. Is this the validation we're looking for? I'm tempted to delete the device and re-add (discover) to ISY. I understand this will require me to add the device to any scene, but there are not too many scenes to add to. Is this valid? Or, I have a spare switchlink dimmer. Would it be a good idea to swap the one that is in there?

Done, but no changes. And, triggering the scene from the remote has same effect as triggering from the keypad. So, triggering from Mobillinc or Test Scene in ISY works, remote or keypad leave the "Kitchen Island" dimmer on. I do appreciate you sticking with it. Any tests you can think of that might help discern a cause?

The keypad buttons are both controllers and responders (for different things). You can see the setup in this screenshot. They are controllers for this particular scene ("Low Hang"), and they seem to control it fine with the exception of this switchlink dimmer. I will charge and update the remote just to keep it up to date. Still works, just don't use it much.

I see. Yes, that remote has fallen out of favor and is not charged. The triggers I'm using are on hard wired keypad links. So hard to understand why the scene works when it is "software initiated" (via ISY Scene test, or Mobillinc), but doesn't work when initiated via any of hte keypads. And, by "not work" I mean the scene works perfectly *except* for turning off the Kitchen Island lights.

Can you explain how, or point me to a reference? I'm not sure how to do that.

Screenshots attached. The scene "Low Hang" is controlled by any one of three keypad links (button "D"), results are same from all.

I factory reset device and then restored from ISY99. Everything seemed to go fine with that process. The problem continues. Summing-up what seems to be the most relevant symptom: If I trigger the scene from a physical switch that is a controller, the scene performs as expected *except* the switchlink dimmer stays on (it is set to go off in this scene). When I test scene with ISY Tools>Diagnostics>Test Scene, everything works as expected (the switchlink dimmer goes off). When I trigger the scene from MobilLinc, everything works as expected. The results are consistent, only seems to not work when triggered from a physical switch (8-keypad) scene controller. Any ideas? Thanks for any replies