walkman9999

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

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

Ok, summing up: will hold off on upgrading allowing overall restore to continue (and won’t do that again) will reset device and restore the specific device the device is set to be off in scene, problem is it doesn’t turn off when it is on when scene runs Will update topic after restore and trying above. Very much appreciate discussion

I'm in the middle of restore devices now - seems like I should let it continue? If so, when it is completed I will both upgrade and factory reset/restore as suggested. Thank you.

I did a restore on the specific device and it didn't change anything. I am now in process of restoring everything (file>restore devices). I really don't know enough to say why I'm doing this, but it is processing now.

Also, just noticing that if I test the Scene using Tools>Diagnostics it works fine. Problem only occurs when I trigger the scene from a button on a keypad. Scene test results attached ISY-Events-Log.v4.9.0__Sat 2022.12.03 12.31.40.txt

Hello, ISY994i PRO v.4.9.0 ISY (Help->About screenshot attached ) Existing installation, problem seems to be with one switchlink dimmer (2476d v40). The switch works fine using the physical control. First problem I noticed is that the switch doesn't respond to scene control, it is supposed to turn off when scene is triggered, but doesn't. Then I tested the switch from the admin console and noticed that "Fast On" turns device on, but "On" doesn't. Event viewer output below: "Fast ON" (works as expected) Sat 12/03/2022 11:56:24 : [INST-TX-I1 ] 02 62 1A 3D 87 0F 12 00 Sat 12/03/2022 11:56:24 : [INST-ACK ] 02 62 1A.3D.87 0F 12 00 06 LTON-F (00) Sat 12/03/2022 11:56:24 : [INST-SRX ] 02 50 1A.3D.87 52.65.4C 2B 12 00 LTON-F (00) Sat 12/03/2022 11:56:24 : [Std-Direct Ack] 1A.3D.87-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/03/2022 11:56:24 : [D2D EVENT ] Event [1A 3D 87 1] [ST] [255] uom=0 prec=-1 Sat 12/03/2022 11:56:24 : [ 1A 3D 87 1] ST 255 "ON" doesn't turn the device on Sat 12/03/2022 11:56:05 : [INST-TX-I1 ] 02 62 1A 3D 87 0F 11 00 Sat 12/03/2022 11:56:05 : [INST-ACK ] 02 62 1A.3D.87 0F 11 00 06 LTONRR (00) Sat 12/03/2022 11:56:06 : [INST-SRX ] 02 50 1A.3D.87 52.65.4C 2B 11 00 LTONRR (00) Sat 12/03/2022 11:56:06 : [Std-Direct Ack] 1A.3D.87-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 (seems to be missing the stuff above in RED) Not sure what to look at from troubleshooting perspective. Any suggestions for tests or info to gather? Thanks for reading.

THis seems to be the case. Thank you.

Hello - Existing installation with no recent configuration changes. Lately I've been getting text notifications with the expected/proper timestamp in the message body (created with the ${sys.time12} variable), but a text message time of many hours later. I would assume carrier problem (Verizon), but other texts - including tests from ISY - don't have this problem. Is there a way to enable logging on ISY to show when the message is sent to the SMTP server? Trying to determine where the delay is. Thanks for any advice. :Mike