dex Posted September 17, 2022 Posted September 17, 2022 Prior to migrating to IoP (from ISY 994), the following was working. Now, buttons on KeypadLinc (KPL) do not trigger programs. For example, I have a button on a KPL dedicated to launch a "goodnight" program that sets several scenes and states. The button's toggle mode is set to Non-Toggle [Off]. Image attached. Here's the program that used to execute whenever this button was pressed: Goodnight - [ID 0012][Parent 0001] If '*LR Panel - H Goodnight' is switched Off Then Set 'Kitchen Bedtime' On Set 'Livingroom' Off Else - No Actions - (To add one, press 'Action') There were more 'then' program lines, but I have simplified the program while troubleshooting this issue. I have rebooted the IoP, done a factory reset/restore of the KPLs, and walked through every device option that I can see. I have three different KPSs with buttons and programs like this and none of them work. The 'last run time' (in the Summary tab for programs) doesn't show that any of these programs have run when I've pushed the respective buttons. What am I overlooking?
oberkc Posted September 18, 2022 Posted September 18, 2022 My first instinct is to confirm that the new "ISY" is seeing the button press. If you open the event viewer and have someone press the button H, does the event register? 1
dex Posted September 18, 2022 Author Posted September 18, 2022 (edited) In the Event Viewer (set to Level 3 visibility) ... Program-triggered events: Yes Query events: Yes Motion Detector events: Yes Button events: No There are no events showing up from KPLs or dimmer switches. It appears this issue is not rooted at the KPL, but across all devices. Button-controlled scenes are working, the device-to-device signals are getting sent. But ISY is not picking any of them up. What could be causing this? Edited September 18, 2022 by dex
MrBill Posted September 18, 2022 Posted September 18, 2022 (edited) I just jumped on testing this. I've been debating moving to Polisy, however I wouldn't be able to if button press events such as this don't work. Here's what I did. Acquired an 8-button keypad from my spares stock and wired it with a temp cord and plugged in. Factory reset the 8-button keypad, then added it to the Polisy test system and it's PLM (2413U). opened Event Viewer then tested communication by turning Button A on and off from Admin Console, then Turned button A on and off by pressing the button. Everything worked as expected. Opened "Button Toggle Mode" then set Button H to "Non-toggle Off". Pressing button H now causes a single DOF to appear in the event view (as expected). Added an INT variable called Button H Count, then created the following test program: Pressed Button H several times... each press adds one DOF to the event viewer, and correctly increments the Int variable. So everything is working correctly as expected, now the question is why @dex's ISY can't hear the DOF's. Insteon Noise? Edited September 18, 2022 by MrBill 1
dex Posted September 18, 2022 Author Posted September 18, 2022 (edited) Thank you @MrBill! I haven’t had Insteon noise/interference issues for some time. I have several access points and mostly dual-band devices now. That said, are there any good tools these days for troubleshooting comm issues? Edited September 18, 2022 by dex
oberkc Posted September 18, 2022 Posted September 18, 2022 I would be a little surprised if this was noise, since this appears universal across a type of device. I wonder if restoring the keypad would solve this (perhaps some link records became corrupted or don't match the IoP). 1
dex Posted September 18, 2022 Author Posted September 18, 2022 (edited) I have restored the KPL. I'm also seeing the lack of DON or DOF events from any physical press of a button on any device in the house. I did discover this Not sure what this means, but I assume some bad (or improperly formatted) memory?? I'm running Insteon on Polisy (5.4.4) using an upgrade SSD from UD about a week ago. Edited September 18, 2022 by dex
dex Posted September 18, 2022 Author Posted September 18, 2022 Also discovered that when I look at the Event Log via the Portal, I get this (with NaN in all of time/date fields). Device Control Value Time User 4F 85 64 1 ST Off NaN/NaN/NaN NaN:NaN:NaN System 5 0 null NaN/NaN/NaN NaN:NaN:NaN System 1 0 null NaN/NaN/NaN NaN:NaN:NaN System 1 A 94 26 1 ST Off NaN/NaN/NaN NaN:NaN:NaN System 5 A 94 26 1 OL 100% NaN/NaN/NaN NaN:NaN:NaN System 5 A 94 26 1 RR 4.5 secondsNaN/NaN/NaN NaN:NaN:NaN System 5 3E 99 B0 1 ST Off NaN/NaN/NaN NaN:NaN:NaN System 5 3E 99 B0 1 OL 100% NaN/NaN/NaN NaN:NaN:NaN System 5 [...] There are a few lines scattered throughout the log that look like this (long string of zeros). [...] 17 88 A5 1 ST Off NaN/NaN/NaN NaN:NaN:NaN System 5 3F BB 2 1 ST Off NaN/NaN/NaN NaN:NaN:NaN System 5 4B A0 E3 1 ERR 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000NaN/NaN/NaN NaN:NaN:NaN System 5 4B A0 E3 1 NaN/NaN/NaN NaN:NaN:NaN System -2 43 9F 54 6 ST Off NaN/NaN/NaN NaN:NaN:NaN System 5 [...] Perhaps related? Perhaps yet another issue?
Geddy Posted September 18, 2022 Posted September 18, 2022 2 hours ago, dex said: Not sure what this means, but I assume some bad (or improperly formatted) memory?? That "bad" value is known a UI issue. It's fine to ignore and not causing any issues. Mine currently displays: Can you confirm your UI/FW match? Help -> About If you've rebooted/restarted lately have you also power cycled the PLM? Make sure you plug the PLM in first and allow some time before you booth the Polisy.
dex Posted September 18, 2022 Author Posted September 18, 2022 (edited) 1 hour ago, Geddy said: That "bad" value is known a UI issue. It's fine to ignore and not causing any issues. Mine currently displays: Can you confirm your UI/FW match? Help -> About If you've rebooted/restarted lately have you also power cycled the PLM? Make sure you plug the PLM in first and allow some time before you booth the Polisy. Thanks for the note on the UI issue, @Geddy. My firmware and UI versions are identical to yours. I power cycled the PLM again, this time waiting several minutes before booting Polisy. No change in behavior -- DON (Device On) and DOF (Device Off) messages are not being received from any dimmers, switches, or KPLs. Edited September 18, 2022 by dex
MrBill Posted September 18, 2022 Posted September 18, 2022 22 minutes ago, dex said: I power cycled the PLM again, this time waiting several minutes before booting Polisy. No change in behavior -- DON (Device On) and DOF (Device Off) messages are not being received from any dimmers, switches, or KPLs. do you have an extra keypad or can you pull one out. Wire it when a plug in pigtail and cap the red wire. Plug it in in the same place as the PLM.
dex Posted September 18, 2022 Author Posted September 18, 2022 52 minutes ago, MrBill said: do you have an extra keypad or can you pull one out. Wire it when a plug in pigtail and cap the red wire. Plug it in in the same place as the PLM. Well, I happen to have a dimmer switch wired so I can plug it in. I added it (new device) and all on/off events from that switch are seen by ISY, no matter where I plug it in in the house. With 180 nodes, deleting and reinstalling devices would take me days. Perhaps that's a last resort. I have factory-reset and restored devices and that does not seem to resolve the issue. I have also restored the PLM, but I haven't tried factory reset on the PLM before a restore. I think I'll try that next.
MrBill Posted September 19, 2022 Posted September 19, 2022 17 hours ago, dex said: Well, I happen to have a dimmer switch wired so I can plug it in. I added it (new device) and all on/off events from that switch are seen by ISY, no matter where I plug it in in the house. With 180 nodes, deleting and reinstalling devices would take me days. Perhaps that's a last resort. I have factory-reset and restored devices and that does not seem to resolve the issue. I have also restored the PLM, but I haven't tried factory reset on the PLM before a restore. I think I'll try that next. I've about reached the conclusion that when i move my insteon over to Polisy that I need to do it manually, factory reseting every device and start fresh. there's about 3 devices (2 are fanlincs) that I won't factory reset but just clear old links as I re-add because they are hard to get to. I just wish there was a faster way to add my ~380 programs, but I suppose I'm smarter about programming now too so starting from scratch may not be all bad.
dex Posted September 21, 2022 Author Posted September 21, 2022 (edited) After several days of troubleshooting and experimenting, it's clear that device events (on, off, fast on, fast off, etc.) are not getting picked up by IoP. If I factory reset a device, then restore it, no change in behavior. If I delete a device, relink it, then restore it, then device events are seen by IoP -- it works! However, I have so many devices, scenes, and programs that doing a complete delete/add/reconfigure for everything in my system will take weeks (or more). In coming up with an approach to re-add devices to the system while preserving configuration details, I tried using a 'surrogate' device. 1. Add a same-type device to the system (the "surrogate"). 2. Replace the target device with the surrogate. 3. Re-add the target device back to the system. 4. Replace the surrogate with the target device. This mostly worked. I was able to use an extra dimmer switch as a surrogate for existing dimmer whose events are not seen by IoP. After the process, the target device's events are now being seen by IoP. The target device is also back in the original scenes and programs as it was before the process. The only anomaly I noticed was the "local" settings like on-level and ramp-rate did not survive the journey to the surrogate (temporary host) and back to the original. All other configuration seems to have made it as I had hoped. I've done this with a few devices, and it consistently works. Clearly there are things that happen when a device is initially added (linked) into the system that do not happen when restoring an existing device, even if you factory reset that device. So, here's a feature request for IoP: when executing a Restore Device function, provide an option to completely remove and relink the device. This new option would hold temporarily the device configuration (preserving links, scene membership, program references, etc.) but deletes and re-adds the device to IoP, then restores the saved configuration. It would likely take longer than a simple Restore, but take the device through the new linking procedure that seems to be critical in solving this problem. Might show up something like this (in the Restore Device dialog)... It's also semantically similar to Replace [device] with ... itself. Though that seems a convoluted place to put it in the UI. Am I missing a way to do this that already exists (short of a complete system reconfiguration)? Edited September 21, 2022 by dex
lilyoyo1 Posted September 24, 2022 Posted September 24, 2022 4 hours ago, dex said: After my migration to IoP (5.4.4) from ISY994 (5.3.4) I discovered that events initiated at each device were not being seen by IoP. For example, turning on an Insteon dimmer switch would normally generate a DON event visible in the Event Viewer. Now there are no events in the Event Viewer from local device events (i.e. pressing buttons), unless I delete and re-link the device and set it up all over again. What I've tried: Factory reset and Restore Device on each device does not help. Factory reset and Restor PLM does not help. But if I completely remove the device and then re-link it to IoP, all button events show up perfectly in Event Viewer. With ~180 nodes (~100 devices) in my system, removing, re-linking, and reconfiguring each and every device would be painstakingly tedious and time consuming, particularly with all of the scenes, local on-levels, local ramp rates, etc. that I have set up. Is there an easier way? Thanks for any ideas/suggestions/shortcuts. P.S. I would love it if the Restore Device function in IoP would offer an option to completely delete and then relink the device without forgetting it's links, local config, and scene membership. This new option would temporarily hold the device configuration while it deletes and re-links the device. Might show up something like this in the Restore Device dialog... It's also semantically similar to Replace [device] with ... itself. Though that seems a convoluted place to put it in the UI. It would be nice but probably has limited ROI since one could simply manually factory reset the device and restore it (which should give better results). If a person has to do a full system that way, chances are they have bigger issues and should be seeking direct help from UDI. 1
dex Posted September 25, 2022 Author Posted September 25, 2022 Thank you, @lilyoyo1. I have done factory resets and restores on individual devices and that still doesn't enable events to get through to ISY. UD (Michel) is having me do a full "Restore Devices" action that goes through all devices (ISY-99i/ISY-26 INSTEON:File Menu - Universal Devices, Inc. Wiki (universal-devices.com) 1
dex Posted October 2, 2022 Author Posted October 2, 2022 Restore Devices made no observable difference. Device events are not being seen by ISY unless the device is deleted and re-linked.
Recommended Posts