Screw Loose Dan

I guess there's no way to know, but reading how things went, I wonder if the format procedure not go according to plan caused the later issues (time/mail settings, etc).

Well, figured out the issue and resolved for now. I'm slightly embarrassed it was something so simple... The IOLinc had wiggled loose and wasn't plugged in fully. I hadn't thought about looking at the status lights (I don't really notice them normally being up on the 10 ft ceiling), but as soon as my girlfriend touched the IOLinc, the lights came on. She left the 1st GDO unplugged (never bothered with the 2nd one), I tested and confirmed everything worked as expected. Had her plug the GDO back in, repeated tests, and again everything worked as expected. So, for now everything is back to working. I will need to think about a way to more securely hold the IOLinc in place to the ceiling outlet. And, I'll consider putting FilterLincs in place as well. Thanks again for all the suggestions and feedback.

I'm far from an expert, so consider this as much a question and not so much a statement; my understanding is the number of programs isn't going to be such a problem but rather the number of programs running at the same time could be problematic. Unless you have a 7 year old running around the house hitting every button they can reach and yelling at Google to turn lights on/off at the same time (which I live with as a very real life scenario), I don't see your program to keep things in sync as actually being much load on ISY. The programs only get triggered when a light (device) status changes, ISY doesn't scan for changes. It would take a bit of administrative work to get it all setup, but as Bill points out copying the program/folder would speed the process up. I think I remember there being an upper limit on the number of programs allowed, but that was in the thousands. I can't think of any more elegant solution. @MrBill You could do similar with Google like you do with Alexa, using a variable to control the light/scene. However, don't call it a scene but instead use "light" as the category. As @ncoigmentioned, scenes in Google work for voice but don't show in the UI (weird!). But, calling it a light makes it show as a dimmer. And, you could say "Hey Google, set test light to 55%" and it would set the variable to 55.

Thanks for all the great information! I did power cycle the unit when the issue first appeared (using the circuit breaker), but no change. When I get this one down, I'll take a look at what revision it it and if it's not one of the ones listed above, I'll try to get you what it has in it.

I guess it's possible that the GDO became noisy? Capacitors go bad... The IOLinc has been in place since 2013 or so. Never had an issue before. I never tested the communication of this device before, but never had a reason to. There's another IOLinc on the same branch circuit, controlling the other GDO, it's still functioning correctly. Both IOLincs are the same age and both GDOs are same age/model/manuafacturer (Craftman, likely relabeled Chamberlain?). I agree testing for noise (FilterLinc or unplugging the GDO) should be the first step. And the testing with the physical unit would be very simple, normally. Here's the other IOLinc for the other GDO, as I said it's on the same circuit, just a few feet away. Did both a query and an option update. Fri 02/26/2021 02:31:25 AM : [INST-TX-I1 ] 02 62 24 2E A3 0F 19 01 Fri 02/26/2021 02:31:25 AM : [INST-ACK ] 02 62 24.2E.A3 0F 19 01 06 LTSREQ (01) Fri 02/26/2021 02:31:25 AM : [INST-SRX ] 02 50 24.2E.A3 3B.94.51 2F 00 01 (01) Fri 02/26/2021 02:31:25 AM : [Std-Direct Ack] 24.2E.A3-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 02/26/2021 02:31:25 AM : [INST-TX-I1 ] 02 62 24 2E A3 0F 19 00 Fri 02/26/2021 02:31:25 AM : [INST-ACK ] 02 62 24.2E.A3 0F 19 00 06 LTSREQ (LIGHT) Fri 02/26/2021 02:31:25 AM : [INST-SRX ] 02 50 24.2E.A3 3B.94.51 2F 00 00 (00) Fri 02/26/2021 02:31:25 AM : [Std-Direct Ack] 24.2E.A3-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 02/26/2021 02:31:36 AM : [All ] Writing 101 bytes to devices Fri 02/26/2021 02:31:36 AM : [24 2E A3 1 ] Memory : Write dbAddr=0x0033 [08] cmd1=0x2E cmd2=0x00 Fri 02/26/2021 02:31:36 AM : [INST-TX-I2CS] 02 62 24 2E A3 1F 2E 00 01 06 08 00 00 00 00 00 00 00 00 00 00 C3 Fri 02/26/2021 02:31:36 AM : [INST-ACK ] 02 62 24.2E.A3 1F 2E 00 01 06 08 00 00 00 00 00 00 00 00 00 00 C3 06 (00) Fri 02/26/2021 02:31:36 AM : [INST-SRX ] 02 50 24.2E.A3 3B.94.51 2F 2E 00 (00) Fri 02/26/2021 02:31:36 AM : [Std-Direct Ack] 24.2E.A3-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 02/26/2021 02:31:36 AM : [INST-TX-I2CS] 02 62 4C DA 7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 02/26/2021 02:31:36 AM : [INST-ACK ] 02 62 4C.DA.7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 02/26/2021 02:31:37 AM : [INST-SRX ] 02 50 4C.DA.7F 3B.94.51 2F 2F 00 (00) Fri 02/26/2021 02:31:37 AM : [Std-Direct Ack] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 02/26/2021 02:31:37 AM : [INST-ERX ] 02 51 4C DA 7F 3B 94 51 15 2F 00 01 01 0F FF 00 A2 00 3B 94 51 FF 1F 01 E0 Fri 02/26/2021 02:31:37 AM : [Ext-Direct ] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Fri 02/26/2021 02:31:37 AM : [All ] Writing 100 bytes to devices Fri 02/26/2021 02:31:37 AM : [INST-TX-I2CS] 02 62 4C DA 7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 02/26/2021 02:31:37 AM : [INST-ACK ] 02 62 4C.DA.7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 02/26/2021 02:31:38 AM : [INST-SRX ] 02 50 4C.DA.7F 3B.94.51 2F 2F 00 (00) Fri 02/26/2021 02:31:38 AM : [Std-Direct Ack] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 02/26/2021 02:31:38 AM : [INST-ERX ] 02 51 4C DA 7F 3B 94 51 15 2F 00 01 01 0F FF 00 A2 00 3B 94 51 FF 1F 01 E0 Fri 02/26/2021 02:31:38 AM : [Ext-Direct ] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Thanks for the feedback guys. I guess I need to ask my better half for some more help...

My one IOLinc for a garage door is showing a communication error in ISY (pop-up when signing in and red exclamation next to it). I've tried querying and writing to the device, with no luck. This is what the Event Log shows on a query: Thu 02/25/2021 09:14:26 PM : [INST-TX-I1 ] 02 62 24 2B DF 0F 19 01 Thu 02/25/2021 09:14:26 PM : [INST-ACK ] 02 62 24.2B.DF 0F 19 01 06 LTSREQ (01) Thu 02/25/2021 09:14:34 PM : [INST-TX-I1 ] 02 62 24 2B DF 0F 19 01 Thu 02/25/2021 09:14:34 PM : [INST-ACK ] 02 62 24.2B.DF 0F 19 01 06 LTSREQ (01) Thu 02/25/2021 09:14:43 PM : [INST-TX-I1 ] 02 62 24 2B DF 0F 19 01 Thu 02/25/2021 09:14:43 PM : [INST-ACK ] 02 62 24.2B.DF 0F 19 01 06 LTSREQ (01) I've never really dove into the Insteon communications. Is the ACK from the PLM? Or is that from the device itself? This is what a write looks like (making an option change to trigger): Thu 02/25/2021 09:28:01 PM : [D2D EVENT ] Event [24 2B DF 1] [ERR] [0] uom=0 prec=-1 Thu 02/25/2021 09:28:01 PM : [ 24 2B DF 1] ERR 0 Thu 02/25/2021 09:28:01 PM : [All ] Writing 101 bytes to devices Thu 02/25/2021 09:28:01 PM : [24 2B DF 1 ] Memory : Write dbAddr=0x0033 [09] cmd1=0x2E cmd2=0x00 Thu 02/25/2021 09:28:01 PM : [INST-TX-I2CS] 02 62 24 2B DF 1F 2E 00 01 06 09 00 00 00 00 00 00 00 00 00 00 C2 Thu 02/25/2021 09:28:01 PM : [INST-ACK ] 02 62 24.2B.DF 1F 2E 00 01 06 09 00 00 00 00 00 00 00 00 00 00 C2 06 (00) Thu 02/25/2021 09:28:10 PM : [INST-TX-I2CS] 02 62 24 2B DF 1F 2E 00 01 06 09 00 00 00 00 00 00 00 00 00 00 C2 Thu 02/25/2021 09:28:10 PM : [INST-ACK ] 02 62 24.2B.DF 1F 2E 00 01 06 09 00 00 00 00 00 00 00 00 00 00 C2 06 (00) Thu 02/25/2021 09:28:19 PM : [INST-TX-I2CS] 02 62 24 2B DF 1F 2E 00 01 06 09 00 00 00 00 00 00 00 00 00 00 C2 Thu 02/25/2021 09:28:19 PM : [INST-ACK ] 02 62 24.2B.DF 1F 2E 00 01 06 09 00 00 00 00 00 00 00 00 00 00 C2 06 (00) Thu 02/25/2021 09:28:23 PM : [24 2B DF 1 ] Memory : Write dbAddr=0x0033 [09] cmd1=0x2E cmd2=0x00 - Failed Thu 02/25/2021 09:28:23 PM : [D2D EVENT ] Event [24 2B DF 1] [ERR] [1] uom=0 prec=-1 Thu 02/25/2021 09:28:23 PM : [ 24 2B DF 1] ERR 1 Thu 02/25/2021 09:28:23 PM : [INST-TX-I2CS] 02 62 4C DA 7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 02/25/2021 09:28:23 PM : [INST-ACK ] 02 62 4C.DA.7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 02/25/2021 09:28:24 PM : [INST-SRX ] 02 50 4C.DA.7F 3B.94.51 2F 2F 00 (00) Thu 02/25/2021 09:28:24 PM : [Std-Direct Ack] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 02/25/2021 09:28:24 PM : [INST-ERX ] 02 51 4C DA 7F 3B 94 51 15 2F 00 01 01 0F FF 00 A2 00 3B 94 51 FF 1F 01 E0 Thu 02/25/2021 09:28:24 PM : [Ext-Direct ] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Thu 02/25/2021 09:28:25 PM : [All ] Writing 100 bytes to devices Thu 02/25/2021 09:28:25 PM : [INST-TX-I2CS] 02 62 4C DA 7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 02/25/2021 09:28:25 PM : [INST-ACK ] 02 62 4C.DA.7F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 02/25/2021 09:28:25 PM : [INST-SRX ] 02 50 4C.DA.7F 3B.94.51 2F 2F 00 (00) Thu 02/25/2021 09:28:25 PM : [Std-Direct Ack] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 02/25/2021 09:28:25 PM : [INST-SRX ] 02 50 4C.DA.7F 3B.94.51 23 2F 00 (00) Thu 02/25/2021 09:28:25 PM : [Std-Direct Ack] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Thu 02/25/2021 09:28:25 PM : [INST-ERX ] 02 51 4C DA 7F 3B 94 51 15 2F 00 01 01 0F FF 00 A2 00 3B 94 51 FF 1F 01 E0 Thu 02/25/2021 09:28:25 PM : [Ext-Direct ] 4C.DA.7F-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 To complicate matters, the IOLinc is on the ceiling in the garage. Normally, not hard to get to on top of a 6 foot ladder...but I recently fell off a ladder (outside in the snow, stupidly) and have 4 broken bones in my foot and my L2 vertebrata fractured. So, absolutely no ladders for at least a 4-6 weeks. If I'm going to do anything physically with the IOLinc, I need a solid easy plan. So, I'm thinking I'll ask my significant other to just swap it out for one that I pre-setup (not sure how that's going to be received). Before I go that route, I figured I'd ask here if there's anything else I should try remotely.

Some might suggest a Pi might be more than needed. There's plenty of guys running ESP8266 microcontrollers, flashed with tasmota, with relays to run an irrigation system. Here's one example. There is a node server for mqtt setup to use tasmota (might need tweaked to use a relay board).

This is an interesting conversation. I've never thought of variables as something I'd like to back up. And, off hand, for my personal use I can't think of any reason I would want to keep them in backups. I can't see the usefulness being a widespread need either. However, there is a backup polyglot (I believe written by @bpwwer). It takes a "backup" of "lighting type device status and can then later restore the devices to those values." I'm fairly certain it doesn't backup variables. but my guess is it wouldn't be hard to modify it to do what you are looking to do. And to be clear, the "backup" it takes is not saved to a file, but to the polyglot (database?), so that might need to be changed for your purpose.

Have you tried downloading this: http://isy.universal-devices.com/994i/5.0.16C/admin.jnlp (I know it's not the preferred way, as the Launcher is. However, I've also found more success using the proper downloaded admin.jnlp versus the launcher)

I believe this is @automationgeek Poly, so lets see if he weighs in. However, I just got it to work for me. All the parameters were as I would expect except I'm not sure the Unifi_siteid is needed if you have only one site (I saw complaints in the logs, removed the parameter and things appear to work). Let's say you go to your Unifi controller using a URL like this: https://1.2.3.4:6789/ Unifi_host = 1.2.3.4 (looks like could be IP or hostname) Unifiport = 6789 (if you don't have a port in the URL, this would be 443 if using https://) Unifi_userid = A valid admin account to login with (I made a read only admin specifically for polyglot to use - Settings -> Admins in the controller UI) Unifi_password = Password for the admin above. Unifi_siteid = Current Site is listed in the upper right corner when I'm logged in to the controller web page. It's also listed in Settings -> Site -> Site Configuration. Again, doesn't appear to be needed and didn't work for me. There is up to a 90 second delay, as it looks like the short poll interval is 90 seconds. Hope that helps!

You don't have port isolation set on any of the network ports, correct? Also, since I believe you mention it is the wireless computer having issues, you don't have that on a wireless network (SSID) that has guest policies enabled, do you? Both of these things could cause various communication issues (essentially become firewalls). I doubt this exist as I believe you can access the device, just not the admin console, but figured it might be best to eliminate any possible issues. Also, which firmware are you on? The one post had an attachment of your start icon links, and that looked like 4.9.0/admin.jnlp. The screen shot above with the bubble says "First time slowed (showed?): 5.0.16".

@RLawson - Step three under Install section in the first post:

I believe the Find/Replace feature sounds like it would work. Right click on the top level folder in Programs (mine is listed as "My Programs"), then select "Find/Replace" from the context menu. This will allow you to Find all the program folders for devices (obviously use the Find and not the Replace!).

I wasn't trying to set a ZWave parameter, but I have a few instances were I wanted to do things not natively supported by Home Assistant (or at least I couldn't figure it out). Rather than using rest calls (which I hadn't even considered, ironically), I used state variables which trigger programs to complete what I needed. Setting a state variable was relatively easy in HA. Many ways to skin a cat...

Are you able to turn the device on/off via the admin console? Just because the red exclamation is there doesn't mean it won't turn on/off. As I understand, it means there is a communication error (that might mean Isy isn't getting the acknowledgement that the device was turned on/off). Does the Isy show the correct status when changed via Alexa?

I would think the bulbs and their raw components probably change at least as often, if not even more frequently.

I apologize, I have not read the entire thread (skimmed the last couple pages). But, I believe you are using IcedTea java. I have had limited success using the Launcher in Ubuntu, regardless with IcedTea or JRE. However, I don't seem to have any issue using the direct admin.jnlp under either. If you are using 5.3.1, download the admin.jnlp here: http://isy.universal-devices.com/994i/5.3.1/admin.jnlp

I am on 5.3.1.

I never looked at this before, all my Insteon devices update as expected in the UI and I haven't done much as far as programming in HA (I primarily use it for a glorified frontend and to interface with a few things that Isy node servers don't do well). However, I looked at the Dev Tools and listened for isy994_control events. What I noticed was that if I controlled the Insteon device either through the HA UI or through the Isy admin interface, no events showed up. But, if I manually controlled the device, I saw the event.

It sounds like you are on the right track to prove the LED lights are causing the issue. Can you see the wiring? It's hard to tell you best way to wire the filters without knowing how everything is wired there. But, yes, at least isolating the switches from the load (LEDs) would probably be a good start.

At this point, you believe the LED lights are causing noise, correct? Can you temporarily disconnect the lights from the load side of the 2477S and verify that eliminates your communication issue? As for wiring, take a look at this PDF. As the document states, you want it as close to the offending device (LEDs) as possible. In an ideal world, you would actually put one filter in each LED...but in reality you might find putting one in at the beginning of the string (presuming they are strung in daisy chain) may work just fine. Which obviously would save a ton of money.

@jfaiand @PurdueGuy - Thanks for the input! Jürgen was absolutely correct, I appreciate the extra set of eyes. I knew I was missing something obvious. Interesting idea about not using times directly in programs. While troubleshooting this I switched to using a variable (an integer variable = 1 for Daytime, 2 for Evening, 3 for Overnight). This way there's no way of overlapping these programs, and I can use the variable for other similar/related programs.

I recently put a Aeotec Multisensor in our kitchen with the idea to utilize the motion sensor. Thought it would be easy enough, but I'm a bit perplexed and figure I'm missing something obvious. Hopefully someone can gently point me in the right direction. I have three different programs to cover different times of day, where I want different things done. Daytime; Daytime - [ID 0061][Parent 0020] If From Sunrise To Sunset - 30 minutes (same day) And 'Kitchen / ZW KitchMot Motion Sensor 1' Status is Off Then Set 'Kitchen - All' Off Else - No Actions - (To add one, press 'Action') Evening: Evening - [ID 0062][Parent 0020] If From Sunset - 30 minutes To 11:30:00PM (same day) And 'Kitchen / ZW KitchMot Motion Sensor 1' Status is Off Then Wait 10 minutes Set 'Kitchen / Kitchen ceiling' Off Set 'Kitchen / Sink' Off Else - No Actions - (To add one, press 'Action') Overnight: Overnight - [ID 0063][Parent 0020] If From 11:30:00PM To Sunrise (next day) And 'Kitchen / ZW KitchMot Motion Sensor 1' Status is On Then Set 'Kitchen / Under Cabinet' On Else Set 'Kitchen - All' Off I didn't notice it until after sunset, but all three trigger every time the motion sensor is triggered off. For instance, they all triggered at 8:32:19 PM last night while testing, well after sunset but before 11:30 PM. Also, the under cabinet lights (which are in the "Kitchen -All" scene shut off. Am I missing something obvious? Do I not understand how the time schedule works?

My Siren 6 is just a few feet away from my ISY. I don't have any answers for you, but this is what my Event Viewer shows, just for reference: Sun 01/03/2021 07:11:45 PM : [ZW-SHOW ] ---------------------------------------------- Sun 01/03/2021 07:11:45 PM : [ZW-SHOW ] Last working route from ISY to Node 20 - ZW 020 Sound Switch Sun 01/03/2021 07:11:45 PM : [ZWAVE-TX ] [01040092147D] REQ ZW_GET_LAST_WORKING_ROUTE Sun 01/03/2021 07:11:45 PM : [ZW-SHOW ] - Direct Sun 01/03/2021 07:11:45 PM : [ZW-SHOW ] Sun 01/03/2021 07:11:45 PM : [ZWAVE-RX ZW021_1] [31/05] CC=0x31 cmd=0x05 [012A02F2] ACK,AUTO,EXPLORE From=0x15 Sun 01/03/2021 07:11:45 PM : [ZWAVE ZW021_1] Process value Sensor type=1 scale=1 prec=1 Sun 01/03/2021 07:11:46 PM : [ZWAVE-TX ] [01070080140000F995] REQ ZW_GET_ROUTING_INFO Sun 01/03/2021 07:11:46 PM : [ZWAVE-RX ZW021_1] [31/05] CC=0x31 cmd=0x05 [050127] ACK,AUTO,EXPLORE From=0x15 Sun 01/03/2021 07:11:46 PM : [ZWAVE ZW021_1] Process value Sensor type=5 scale=0 prec=0 Sun 01/03/2021 07:11:46 PM : [ZWAVE-TX ] [01070080140100FA97] REQ ZW_GET_ROUTING_INFO Sun 01/03/2021 07:11:46 PM : [ZWAVE-TX ] [01070080140001FB96] REQ ZW_GET_ROUTING_INFO Sun 01/03/2021 07:11:46 PM : [ZW-SHOW ] Node 20 - ZW 020 Sound Switch has the following neighbors Sun 01/03/2021 07:11:46 PM : [ZW-SHOW ] - Repeater - Node 1 - [This ISY] Sun 01/03/2021 07:11:46 PM : [ZW-SHOW ] - Repeater - Node 3 - ZW 003 Repeater Sun 01/03/2021 07:11:46 PM : [ZW-SHOW ] - Repeater - Node 4 - ZW TVRoom Repeater Sun 01/03/2021 07:11:46 PM : [ZW-SHOW ] - Repeater - Node 5 - ZW Electrical Panel Also, I had issues with firmware 5.3.0 (constantly marked as writing) and opened a ticket. Was told to upgrade to 5.3.1, no problem since. @simplextechThe Aeotec Siren is always powered* and from posts around here was historically always touted as an excellent repeater. There's plenty of posts in the past on this forum that claimed the siren made a better repeater than the Aeotec Repeater did. I have both, never bothered testing myself. * The unit is designed to always be powered, although it does have a backup battery designed to last a couple hours if power is cut (for alarm purposes). The battery isn't removable (well, not easily anyway).

I agree with @lilyoyo1, seeing your programs would be helpful but most likely interference. Rather than adjusting one scene, I use different scenes to accomplish similar to what you are doing. In my case I just use two scenes and it's in my bedroom. The first, "Morning", is an extremely slow ramp rate and only goes to 60%. The 2nd one is a my normal scene for my bedroom. You could obviously add more scenes as desired. Morning Rise-work - [ID 002C][Parent 0001] If Time is 4:55:00AM And 'Kitchen / Under Cabinet' Status is Off And $Vacation is not 1 And $Occupy is 1 And $Work_Schedule is 1 And $S_Awake is 0 Then Set 'Morning' On Wait 5 minutes Set 'Master BR - All' On Else - No Actions - (To add one, press 'Action')