IndyMike

Sounds more like a communication issue. Garages can be very problematic with all the devices that are plugged into outlets (chargers, etc). Since the 2450 is a plug-in device, try moving it closer to your PLM to check communication. If it works, you need to look for signal absorbers/noise generators on the garage circuit.

@Kentinada, It sounds like you would like to include a "Not switched" for the Ring camera to activate the Else section of a program as shown below for a motion sensor -Correct? Trying to understand the problem and am unclear on the following: 1) Is the option for testing the "not switched off" unavailable for the Ring camera? 2) is the option available but does not trigger when the camera stops sensing motion? Kitchen Motion On Copy - [ID 0012][Parent 0054] If 'Motion/RF / Kitchen Mud.1 Motion' is switched On And 'Motion/RF / Kitchen Mud.1 Motion' is not switched Off Then Wait 2 seconds Set '1st Floor / SC Bar Cans' On Else Set '1st Floor / SC Bar Cans' Off

The secondary buttons do not really have an ON/OFF associated with them. They show up as "keypessed" events in Home Assistant. Think of the events as momentary rather than state events. Youtube of the "keypressed" event in HomeAssistant - Skip to 11:25 Testing scene buttons https://www.youtube.com/watch?v=87jquTZ4B_U

Based on my rather limited testing, your IOlinc (V.41) would be susceptible and your Siren (V.46) would not be. My testing of devices in my home is located here : https://forum.universal-devices.com/topic/41651-all-on-removed-in-what-firmware-version-of-switchlinc-dimmers/?do=findComment&comment=369748 You could also try executing a "all-on" command from the Eisy. Not sure if it's still available in the Eisy. It's located at the bottom of the "My-Lighting" screen on the ISY994. Best to try this when family members are not around

I am assuming that your Siren and GDO are not members of any scenes or programs. You can check scenes by looking at the device in the admin console and looking at the membership tree to the right. You can check program membership by right clicking on any program and selecting "find/replace". Search for your I/O linc and you will be able to cycle through all the programs that it is used in. I'm going to out on a limb and assume that you've already checked this. While it's possible that you encountered an electrical "even" that triggered the 2450, it's highly unlikely that the event would trigger the second floor 2868 at the same time (multiple times). The other possibility would be a "all on event". This purportedly involves a communication collision the generate a "all-on" (or all off) command to all Insteon devices. All affected devices activate. I say affected because Smartlabs has removed the command from more recent modules. It is possible that your 2450 and 2868 were produced prior to Smartlabs removing the command. Please post your device version, firmware and date code

@jhoulihan, not a complete solution, but you could hit save your configuration to a desktop file. You will need to manually enter your address (again) so the IOX finder sees the ISY. The simply press "save" and put the file in a convenient location. You can leave the default name or create something new that you'll remember. The next time the IOX finder "forgets" the address, simply load the file from the desktop. https://forum.universal-devices.com/topic/39489-iox-finder-not-found/?do=findComment&comment=354467

Good idea adding the notification... I'm assuming this is the "new" follow-up program that is talking directly to the devices - correct? Are you still running your scene program and does it still fail to shut off the outdoor lights? Are these lights on GFCI circuits (outside and garage)? I am not familiar with the 'Holiday controller' date control. Assuming the program triggers, the device direct communication should be the same as if you turned the devices off from the Admin console. The PLM will issue device cleanup after each command and will retry communication 5x to devices that do not respond. My only other comment would be to make sure you don't have any other programs running at the same time. The Waits are effective at separating the PLM communication events WITHIN the program. If you have multiple programs executing the ISY could insert communication from other programs within the waits. This normally would be a huge concern, but if your PLM is performing retries to a problem device, it might abandon the cleanup in favor of the new command.

Just noticed that your problem lights were outside - i.e. on GFI outlets. GFI's can sometimes degrade powerline communication. What model Insteon devices are you using outside - are they dual band? Can you temporarily bypass the GFI for testing purposes? To @apostolakisl's point above. Much of this revolves around your programs. Please post them.

There are a few misconceptions regarding the protocol and how the ISY handles scenes - 1) Scenes - ISY scenes do not interrogate members to determine if they have responded correctly. As a result, there are no PLM retries used. The ISY assumes that the scene executed properly. The scenes are a single command and are very fast. Since there is no additional communication between the PLM and responders, scene commands in programs normally do not require delays. 2) Device direct commands (admin console) - Device cleanup commands are used to determine if the device has responded properly. If it does not, the PLM will re-try the command xx times. PLM retries are invisible to the ISY. 3) Device direct commands (programs) - Similar to commands executed from the admin console, cleanup commands are issued. The difference here is that the PLM can be overloaded if commands are "chained" and it will abandon cleanup attempts. This is where you need to insert delay between commands to give the PLM time to issue cleanup messages and retries. 4) Device cleanup retries (advanced menu for the devices) - This is for adjusting the #of retries that devices use to communicate with the PLM (not PLM to device). It will have no effect on scenes initiated by the ISY. It is only available on newer devices. https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device 5) ISY Retries - ISY retries are used when querying a device. To my surprise, they do not appear to be used for device direct commands (anymore??). Retries default to 2 and can be changed by using Telnet to connect to the ISY Shell. Use "CR" max command retries. I do not advise adjusting beyond 2 as this significantly bogs down the ISY. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Advanced_Configuration_Guide#CR_-_Max_Device_Command_Retries

My ISY994 does respond to a ping.

That's a classic no-response from a device. The ISY tried to query the device 3 times and received nothing back. Below is and an example of a correct response vs timeout. Your device address (42.D7.A8) indicates that the dimmer is reasonably new (V.45 firmware). It's newer than most of the devices I am using. Unlikely that 3 devices on the same circuit would suddenly all develop problems. If your equipment closet is on the same circuit as the dimmers, you may want to consider filtering devices.

You are not communicating with this device. The ISY is retrying the query after a timeout. Note - the PLM also retries XX times between each of these commands (invisible to the ISY). You're having severe communication issues to this location. Any new devices hanging on your powerline (i.e. Christmas decorations)?

I looks like you may have "Factory Reset" your KPL (erased the link table) and then performed a query. If that is the case, the device is responding with errors and NAK's (negative acknowledges) because it is an I2CS device and is not longer linked to your PLM. I factory reset one of my Test KPL's and got a very similar response. One curious difference is that my ISY994 is using the I2CS protocol to talk to the device. Your log does not show the "CS" (using I2 protocol). That may be a simple difference in presentation (not sure what system you are using). Normally this would be rectified by simply "restoring" the device from the admin console.

@Merlin - Thanks for the response. Another device to investigate - oh well. I am curious how you are powering the devices (and hiding wires) in your installation. Would you mind describing or providing a photo of your wired device? Thanks, IM

I agree that the ISY cannot directly address a KPL secondary button. In order to control a secondary button, it needs to be included in a scene. I am curious why the ISY isn't creating a "scene" for Insteon devices and an "association" for Zwave devices. Either way, it should be an easy thing to determine from the event viewer when the scene is activated by the Z-wave controller. Scene Activation - The 00.00.XX device address is indicative of a Scene. The "CF" flags also specifies a scene command but I am to lazy to decode this AM. Fri 12/01/2023 09:15:15 AM : [INST-TX-I1 ] 02 62 00 00 13 CF 11 00 Fri 12/01/2023 09:15:15 AM : [INST-ACK ] 02 62 00.00.13 CF 11 00 06 LTONRR (00) Device Direct Addressing: The 1A.5D.C7 address is an individual device in my system (member of the scene above). The "0F" Flag also specify a "direct command". Other indicators of a direct command are the 3rd line (02 50) which is a response from the target device. Scene commands (above) do not request a response. Fri 12/01/2023 09:16:24 AM : [INST-TX-I1 ] 02 62 1A 5D C7 0F 11 F7 Fri 12/01/2023 09:16:24 AM : [INST-ACK ] 02 62 1A.5D.C7 0F 11 F7 06 LTONRR (F7) Fri 12/01/2023 09:16:25 AM : [INST-SRX ] 02 50 1A.5D.C7 53.BC.3A 27 11 F7 LTONRR (F7) Fri 12/01/2023 09:16:25 AM : [Std-Direct Ack] 1A.5D.C7-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 I do not know/understand how the ISY is activating Zwave "associated" devices. I do not currently have a Zwave/ISY installation to test. But I am very curious for future installations. One last comment - I do remember a @lilyoyo post from years ago indicating that Zwave controllers should be added to a scene 1st. I had always abided by that when I had my mixed system. Have no idea if it still applies. IM

@djones1415, I apologize if my response implied in any way that you required this type of response. Being an Engineer (and working with Engineers) for 40+ years, pictures and screen captures are my go to. My friends and family would attest that I am uniquely qualified to provide idiotic responses. Glad it helped. In retrospect, Lou's (Apostolakisi) response was exactly correct. Had I seen it, I would not have replied. Geddy's response was "most" correct - pointing to existing Wiki documentation rather than re-inventing the wheel. I need to remember that. IM

Device replacement steps - This only works with similar device types (dimmer to dimmer/switch to switch) 1) Factory reset your new switch. This removes potentially unwanted settings from the new device (X10 addresses, etc). Manual : 2466 Toggleinc 2) Link the new switch and use the "Remove Existing Links" option. There should not be any links after resetting, but... (belt and suspenders). Name the device something similar to your old device - add a "#" or a "new" to discriminate between them. 3) Right click on the "old" device that you want to replace. It should now show the recently added device as an option for replacement. IF IT DOES NOT your old device is in a sub-folder or a different device type. If in a sub folder, move to the root folder. Device in sub folder will not show replace option After moving to the Root folder: replace is now an option 4) After performing the "replace with" you will be prompted to re-boot the ISY. Following the re-boot, the new switch should be in place and all of your programs and scenes should be updated. 5) Re-name the new device if you wish. All the programs and scenes will be updates.

Hi @Merlin, Unfortunately, I can't help with inclusion issues as I don't have the Eisy. I do have a number of the ZSE44's and am happy with them in general. They do have a lot of "nodes" as you refer to them. On my ISY994, I believe I was able to "group" nodes by right clicking on the main node (1) and selecting "group devices". This would move the secondary nodes under the main node in the device tree (make them less obvious). As I indicated, I have a number of the ZSE44's. I am happy with them except for my "outdoor" devices that consume batteries. The issue here is that I have devices outside the house that go through wide temperature swings this time of year (40" degrees). This drains a lot of battery. Devices in the house run ~1 year on a CR2450. Outside, less than 1/3 during spring/fall. I am posting because I am interested in the Aeotec Mutisensor 7's that you have coming. Then have an advertised life of 3+ years. The are similar to my Zooz ZSE40's that I have been happy with (motion, temp, humidity), but have a much better advertised battery life. Please do report back how you like the Aeotec devices. If you have further questions on the Zooz ZSE44's, I'll help where I can. IM

Wow, after reading @Geddy's post I logged into the admin console to re-checked my Scheduled execution times (no changes). They are back to being correct down to the tenth of a second. Wild and wondrous - I guess that's why they call it software.

Hey @paulbates, Let me start by saying that I have the ISY994. I have two programs that run nightly at sunset, and 30 minutes past sunset. When I looked at the program summary tab, both programs were set to run @EXACTLY sunset and 30 minute past. My sunset is at 5:36:10 (I'm a little West of you). Since my programs are slightly different from your Time = Sunset, I decided to add a test case. That's when things got weird. After saving my test program, ALL of my sunset programs showed a "Next Scheduled Run" time that was 4 minutes, 4 seconds early. I expected 5:36:10 PM (sunset) for my sunset programs, but got 5:32:06. I expected 6:06:10 PM for my night program (sunset + 30 min), but got 6:02:06 PM. All that I can think of is that the next run is "predicted" when you save the program. It is then "refined" after the program executes (or perhaps at the end of the day). Definitely not the result I was expecting and in line with what you are seeing. Original Sunset Program: Fires @5:36:10 Outside Sunset - [ID 0015][Parent 0002] If From Sunset For 1 minute Then Set 'Outdoor / SC Outside Sunset' On Else - No Actions - (To add one, press 'Action') Original Night Program: Fires at 6:06:10 Outside Night - [ID 0016][Parent 0002] If From Sunset + 30 minutes To Sunrise + 5 minutes (next day) Then Set 'Outdoor / SC Ouside Night' On Else Set 'Outdoor / SC Ouside Night' Off New Test Program: Fires at 5:32:06 Outside Sunset1 - [ID 0011][Parent 0002] If Time is Sunset Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

@madmartian There is a discussion of SIS and SUC Z-wave controllers over here: https://www.vesternet.com/en-us/pages/your-guide-to-a-user-friendly-stable-z-wave-network What I gather from this is that the SIS controller is the "repository" of all device node information in the Z-wave network. If you had other controllers in the network, they would be unable to operate after you reset the SIS. This is my first exposure to the SIS concept. Since you are resetting your entire network (all devices and dongle), I don't believe there is an issue. Curious if anyone has a different take...

Hey Andy, Given that you apparently have an Insteon door Open/Close sensor (there I go ASSuming again), I would tend to agree that this appears to be a Eisy issue. If you could perhaps post some "level 3 event viewer" traces, with manual Vs door operated triggers, someone with a Eisy could chime in on the issue. Not much, but the best I can offer for now.

Edit: after re-reading your code, the "Switched on" control action in the If clause should prevent multiple triggers. Unless the door is cycling open - closed - open, etc. I'll leave the original post below. It's something to try for troubleshooting purposes. I have used the "Beep" calls with the ISY994 for years with no issue. I don't have a Eisy to test... Just guessing here... Since things work when you trigger the programs manually, it seems that the alarm system integration may be the issue (ELK?). One of the differences in the Eisy is the use of a node sever for the Elk integration. The ISY994 used a "built in" integration. You may be getting multiple triggers or other timing issues when your door opens. You could try locking the program out using a variable or by testing that the program isn't already running. Waits could also be used to make things easier to test. Something along the lines of: If 'Lwr Ground Floor / Backdoor-Opened' is switched On and $Status.ProgramBeep is not $Status.Running Then $Status.ProgramBeep = $Status.Running Wait 1 second Run Program 'Beep' (Then Path) Else - No Actions - (To add one, press 'Action') BEEP ProGRAM If Then Beep Beep Beep $Status.ProgramBeep = $Status.Idle Else - No Actions

The following is what I use for polling my outdoor lights. The If statement you are looking for is "Time is Last Run Time for {program name} + 30 minutes". You will also need to make sure that "run at startup" is checked in the program "summary tab" Outside Daytime Poll - [ID 0030][Parent 0002][Run At Startup] If From Sunrise + 30 minutes To Sunset - 10 minutes (same day) And Time is Last Run Time for 'Outside Daytime Poll' + 20 minutes Then Set 'Outdoor / SC Ouside Night' Query Else - No Actions - (To add one, press 'Action')

UltraLoq U-Bolt Pro. I installed a WiFi set at my daughters house and Z-Wave in mine. We both love them. The locks are 700 series and paired to my Zooz 700 series Z-Stick from their remote locations (75+ feet). I was impressed.