larryllix

You could try just unplugging one and test the other also. If this has just started there may be ne that the power supply is breaking down. Mine older GDO always made some noise that I blamed on my inverters. When I installed my second GDO with the battery backup, my Insteon system stopped functioning throughout the house to about 25%, so it was easy to find. There have been many complaints here over the years about these Chamberlain GDOs.

A couple of Insteon FiterLincs would be the simplest and fastest way to eliminate noise from Chamberlain garage door openers for me. If it doesn't work then you have two FilterLincs for other and future trouble shooting. They are easy. You just plug them in and plug the GDO into the filtered outlet on the end of the FilterLinc, and then the IOLinc on top of the FilterLinc in the unfiltered receptacle.

Since the SynchroLinc was discontinued (as Insteon/SmartHome further dies) I haven't seen any easy Insteon devices capable of doing this. Most of the more complex solutions were wired in. Possibly ZWave has some devices? Would be nice to hear from Zwave people about any devices they have.

One caveat with that. If you disable a program in the middle of timing, it will stop running and may never turn the light off, leaving it on. Measures need to be taken to clean all possible combinations up when re-enabling the program. In addition to the status/control methods, and the exemplify this, I have the original MS devices and despite their status showing on permanently, they also send a control On each time motion is detected. The differences between MS1 and MS II units is becoming quite large.

There may be some setting or clues in this setting realm under gmail webpage settings.

I can't remember the details anymore but there is a flag in the setting for the gmail account available via the same gmail webpage settings that allows "foreign accounts" to use or access your email servers. I don't know why this would suddenly give you problems, as google added this new security concept a few years ago, but it would be worth looking for inside the setup options of your gmail account. I know I had to enable the switch a year or two ago.

Access your google mail account via the webserver and see if there is a flag or email stuck in there, asking for permision, you need to approve. Google keeps changing it's permision and security ideas and dumping crap on their users. Then if you don't constantly monitor their latest idea you are left behind with some broken service. Google is a marketing company first, and doesn't really give two hoots about anybody's feelings or satisfaction, that doesn't forward their quest, at that moment in time.

curl: try 'curl --help' for more information which shows -s as a valid option. UPDATE: '| sudo curl' was English instruction, not bash script = all good now

Try the action section of the programming selections. Comments were added between lines in the If, Then, and Else section a few versions ago. They can be found under odd places though and consume too much vertical space, making the code less readable, IMHO.

I do the same, but one caveat is, any program relating to, or calling the program being tested, will not be linked properly during the testing phase. Commenting out a line is one of the most basic troubleshooting techniques in other languages.

Sure but why run up your HVAC bill with too much fresh air. Let your ISY figure out what is most efficient. I use mine to cool the house down at nights to save an A/C bills if the dew point outside is less than the dew point inside and I don't want the humidity. ISY decides all that and could control your ecobee programming to effect it.

With the ecobee NS you should be able to control the cycle of the HRV / ERV to suit your indoor/outdoor climate differences though. I don't really need that much cycle time as we use the HRV button timer on every shower and toilet visit for 15,30, or 45 minutes anyway. I do turn off the HRV cycling when in vacation mode (to save energy) , but not away mode. The ecobee may do that anyway, being wired. After trying many schemes for vacation mode setting, now I use the ecobee NS vacation mode to control my ISY things. It is much more reliable and I can control it with a simple app from anywhere. When any vacation is terminate I run the HRV for an hour to get some fresh air in the house as we get home.

I wouldn't use a scene to control an HRV system. Scenes have no confirmation of the device working, and no Insteon retries if it fails to turn on or off. In my cold winter climate, if my HRV system got stuck on, it would take me a week to get the humidity levels back to a reasonable level again. Most likely somebody would develop a cold/flu by the time the humidity was back on target. I run a cycling program, sync'ed to my central air fan (to save energy) and base the run time on whether the humidity level is higher or lower than needed, and the dew point of outside is higher than dew point of inside and would be beneficial to the house. This amounts to about 1 minute every 40, or 20 minutes every 40 minutes, decided by the humidity and dew point level comparisons. In the winter, running the HRV too long would dry my house right out, and the humidifier would never keep up. In the summer, running the HRV too long would raise the humidity levels way too high, and the house would feel damp, while the A/C runs 24x7.

Unplug the GDO and test it for operation at the IOLinc. Chamberlain GDO are notorious for clobbering Insteon signals. I have two vintages and the older AC motor one caused me grief for years that I couldn't find. I always blamed it on my Outback Inverter system. When I got my second one with battery backup, my Insteon system quit down to about 25% function, throughout my whole house. Two FilterLincs resolved it.

It only disables the triggers of the program.

Something has to move or the box would be open all the time. My mailbox is plastic. My Tags have been outside for years without any problem, but they have been sheltered under the soffits of my house. If the mailbox is left open the Tag is exposed to weather so we will see with that one. The Tags do complain when they see humidity over about 99% RH, which happens all the time while raining here. Yes, the metal enclosure does shorten the range. I was surprised my vehicle one can be detected from over 1 km. The vehicle is metal but not tightly enclosed like the one in my fridge. I had a Tag on my garage door but found it unreliable mounted against a metal garage door so switched it to an I/OLinc for better reliability.

@Michel Kohanimshould be notified of this for investigation. I just did.

I just installed a CAO Tag on the inside of the mailbox front flap, and it only ever misses if the mailman is exceedingly quick with the door, and doesn't hold the door open for more than about 1 second. That hasn't ever happened in about 4 weeks of usage now, but I can make it miss if I try hard. I don't think most Zwave devices would have the distance range on my mailbox as it is about 30 feet from the front of my house and the nearest Zwave device would be inside the house on the other side of my garage. CAO wireless tags can be detected from about 1.5km away in my vehicle glove box.

No. Look in the admin console. The field is called "Luminance". The older MS's field Night/Day doesn't exist anymore.

ISY has developed a problem writing to battery devices and some Insteon plug-in devices over the last year or so. I have no Zwave but many of my Insteon devices have had to be put into linking mode and manually updated. This is not just battery devices anymore but AC powered devices also. The battery write option can be disabled but each time ISY gets rebooted the option turns itself back on and ISY grinds to a halt with massive caching of writing to so many devices. I have attempted to bring this to UDI's attention but has been ignored many times over the last two years in the latest releases. A "run at startup" program to disable the battery write option, can help but is a poor workaround, as the a cache is already full of update instruction by the time the program runs. The updating of Insteon Scenes needs to go back to the way it was previously, and stop attempting to write to battery devices completely. The "Battery Write" option needs to remember where it was last set. as a minimum. I had to put each battery device and about 8 plug-in devices into linking mode and select update to get my ISY back to functioning again. Now every so often I find ISY's cache full of owing writes again, and crippled for HA speed, again. I have also experienced several "ALL-ON" events now, that ISY has become so famous for.

AS per @kclenden above, this is what we have seen so far. 48MotionNotificationFlash5IS0EQ112502502501112223334445556667778889991010101111112121213131314141415151516161617171718181819191920202021212122222223232344EQ0try { Object.defineProperty(screen, "availTop", { value: 0 }); } catch (e) {} try { Object.defineProperty(screen, "availLeft", { value: 0 }); } catch (e) {} try { Object.defineProperty(screen, "availWidth", { value: 1280 }); } catch (e) {} try { Object.defineProperty(screen, "availHeight", { value: 720 }); } catch (e) {} try { Object.defineProperty(screen, "colorDepth", { value: 24 }); } catch (e) {} try { Object.defineProperty(screen, "pixelDepth", { value: 24 }); } catch (e) {} try { Object.defineProperty(navigator, "hardwareConcurrency", { value: 8 }); } catch (e) {} try { Object.defineProperty(navigator, "appVersion", { value: "5.0 (Windows)" }); } catch (e) {} try { Object.defineProperty(navigator, "doNotTrack", { value: "unspecified" }); } catch (e) {} try { window.screenY = 713 } catch (e) { } try { window.screenTop = 713 } catch (e) { } try { window.top.window.outerHeight = window.screen.height } catch (e) { } try { window.screenX = 1273 } catch (e) { } try { window.screenLeft = 1273 } catch (e) { } try { window.top.window.outerWidth = window.screen.width } catch (e) { } Again. Post your programs so people can help. Right click on each program, select copy to clipboard, paste into your thread, so that somebody can understand what you are posting about.

On the webpage of the MS Motion page when you click on your "54.69.C3..1 Motion" node in your device tree.

That was the point. Many of my non-battery, plug-in, devices were a problem also and will not update without the linking mode enabled. IIRC that didn't happen before but during the PLM restore. I know there are different types of update signals and queries from ISY though. When initial linking was done with these devices, none of them required linking mode.

ahhhh. he just upgraded. Perhaps he grabbed the non-PLM firmware??

Possible PLM failure. Have you tried to power up your PLM first, and then power up your ISY994? (after) Have you attempted a Restore on any device yet?