paulbates

You don't have a ton of devices so starting over is do-able. Give this a read first and use it as a guide I'd print out yourf programs you have for a reference. One at a time, delete each device from the ISY, making a list of them as you go so none are forgotten. WRITE DOWN THE INSTEON ADDRESS FOR EACH BEFORE YOU DELETE - 11.22.33 format Reset the PLM Pick delete Modem (PLM) from the File menu and complete prompts Reset the PLM - Un plug, wait 5 seconds, replug while holding the set button until it beeps Unplug the PLM wait 5 seconds and plug in Unplug and replug the eisy, log back in to iox Go to Tools/Diagnostics/PLM info status, look for it to say connected Repeat 3 and 4 above again, even a few times, until it says connected Do not try to add the PLM as a device to your eisy, iox does that on its own One at a time add non-battery devices Go to each non-battery device, unplug, replug while holding the set button For switches, pull out the air gap, wait 5 seconds, then press in and hold In both of the above cases, Wait for the beep Pick New Insteon Device from the linking menu be sure to pick "remove all existing links" One at a time add battery devices Go to each battery device, press and hold the set button until it beeps In both of the above cases, Wait for the beep Pick Link a sensor from the linking menu be sure to pick "remove all existing links" If you get stuck on one, move on to the next. Test everything out. You will have to update programs

Did you try my suggestion of linking a few devices with the linking menu?

Does the iox screen show progress in restoring devices, or is it still/stuck? Do you have any battery wireless devices like sensors: Leak sensors, motion sensors, door sensors or Insteon remotes? Wireless devices each, individually have to be put into linking mode to complete the restore

I believe factory resetting it will make the top button control the load, if it's one of the others out of the box. I've not seen iox release notes mentioning it's been addressed.

Another avenue is to use the linking menu to put iox into linking mode. Then press the set button on the appliancelinc until it beeps. Go to iox and finish the linking process. If this affects multiple devices, you can put iox into linking mode and press set on multiple devices before completing linking in iox

The yolink hub 2 offers speaking phrases if you have yolink devices. I've thought about it as mine is located in the main living area. Not sure if there is an audio out though for larger scale projects Michel has an audio plug-in for this purpose. You'd need some hardware but worth a look.

Per @Techmancomments, and mine above... replugging has bought you the time to order a new one and install... NOW is a really good time to make a backup

I'm leaning towards plm, mainly if your links table is empty. You could try unplugging the plm, waiting 10 seconds and plugging back in. If that works it's partial confirmation that the plm is dying. How old is the plm?

Wi-Fi things, including this stat have come back from power failures on their own in the past at my last house and here. It's an Asus RT- AX88. Though a few years old, it is over configured for core count, core speed, memory and NVRAM for our current use, 14 devices total. Guess there's nothing to do about it but find out when the ecobee app can't contact.

We hope so. We've only had one "lost" day this trip (starting 8/29) because of weather. Looking forward to trying out the Shorts brewery "mother ship" location

Asked my neighbor Steve to take a look and take a pic of it.... And got this 🤪😂 It was simply disconnected from the router and didn't try to reconnect on it's own (?) he said no power outages in our neighborhood since we left It's working now

Thanks @dbwarner5.. and also showed the same on iox. The weather/forecast appears close too, but then realized that's coming from cloud and not the stat. In the UP we've been to Brevoort lake, Sylvania, black river harbor and Marquette today at the UP beer fest. FWIW, we'll be in Antrim this time next week for the paddle Antrim event.

@larryllix.. if the stat's not connected to Wi-Fi, I'll have to pull it off the wall to restart it, or pull the c-wire from the furnace. I can't see the display from +400 miles away right now to know if I have options, or it's locked up. I'll contact my neighbor to see if there was a lighting strike and go in to look at the display

I've had an ecobee smart stat and plugin for ~9 month. I've used the built in ecobee features and the plugin, wrote programs and don't think about it much.. except when traveling. We left a week ago for 3 weeks camping in Michigan's upper peninsula and northern Michigan.. and of course the first stop the first night, the ecobee app reports "offline" 🤷🏽‍♂️. The plugin, via UDM, thought things were ok. It's been between then and now that there's enough signal to do anything and I can connect ot the house pc. Iox also thinks things are ok, if I change modes or fan modes, iox shows a change. I tried turning on AC and set the temp down 3 degrees, it shows a change of mode to cool, but run state of idle. I log into the router, and ecobee is no longer there on the list of wifi devices, but yolink and ring are along with other things are I don't think I've heard anyone report offline in the ecobee app. I have had the plugin report that ecobee, as opposed to the plugin is offline and back again and that has never been an operational problem. Has anyone had this problem? I'm guessing the plugin is communicating with the ecobee "cloud", and it talks to the thermostat

You probably tested it, but both "run" statements are calling "if"s, which both have to be true.. you'd get the same negative results either way. Does it work with a notification or beeping an insteon switch, or something, to verify?

Forgot to mention i3 is eisy (and I think policy) only, not for the 994

How old are the insteon device with the problems? How old is the plm? The humming and buzzing (and other problems) with akeypads was an issue I had with a number of my keypads around 2011 I think. There was a problem with a production run of them and insteon replaced all of mine from that run. The those keypads were sold with my house last summer, working fine. I've moved into the i3 switches at my new to me house and I and wife really like them. If most of your insteon works if stick with it. If you're going to replace it all, factor that cost in along with the learning curve and controllers for the new technology you'd pick

This should give you a guide for wiring

In many cases a failing PLM will act the way it does because the link table data is bad. What the ISY does is keep the master copy of links in a file as you add devices and scenes. Sometimes when PLMs fail the links table in the PLM becomes corrupt and/or incomplete. This is a link to an older manual, but the procedure is the same. Go to page 60 to 3.10.3 and forward and follow those steps. This type of failure usually comes with older PLMs, but its a place to start and something to eliminate as a cause.

Re-iterating what was said: Homeseer, Insteon, UDI and yes, Home Assistant, as comparatively smaller integrators, aren't fully there yet. None of them have a "we'll be ready here" date. Matter/Thread require significant resources for smaller integrators to complete the work, compared to Apple, google, Amazon. From Home Assistant's current Matter web page: "Realize that you are an early adopter, both on the hardware side and on the software (controller) side so you may run into compatibility issues or features that are still missing. Report any issues you may find and help out others if you find a workaround or tested a device." All due credit to Home Assistant's advanced state of integration, they are not saying "we're there". There's not a date. They are the lead horse in the race. Not all integration companies have the necessary resources to deliver the Matter plumbing .You've chosen an early adopter standard above automating functions in your house and will need the patience to see it through.. or make the necessary platform choices based on the direction you want to go.

I use a doorbell camera. A suggestion is to write an iox program that detects the motion. Then let it call a second program to turn the light on, use a wait statement ,and then shut the light off. By detecting only "on", the effects of the light won't effect operation. Here's my first program that detects motion. It calls a second program that turns various lights on, waits (randomly) and shuts them off. The point is, once motion is detected, the second program runs regardless of the motion sensor going back off: Front Motion Detected-1 - [ID 0027][Parent 0002] If 'Lighting Premise / Front Door (Motion)' is switched Motion And From 9:30:00PM To Sunrise - 30 minutes (next day) And 'Lighting Premise / Seasonal Lights-Entry Closet' Status is Off Then Run Program 'Front Motion Detected-2' (Then Path) Else - No Actions - (To add one, press 'Action')

When it's plugged in to an iPhone block charger, connected to light switches with a scene and backstopped with an iox program, it's working very well for me as an MS

A couple of efficiency comments: My belief is that it would be better for the If to use Control instead of status. When you turn an Insteon device on or off, there are multiple message exchanges between the PLM and the device. I'm counting 14 separate devices being addressed in a row. The way the ISY works.... it doesn't wait between each of the on or off commands. So your Insteon network is flooded with traffic and the next on or off is colliding with the previous. Is individual device reliability a reason for repeating it 150 times? To be candid that is really extreme. Put the individual devices into one or more scenes (one should be fine), and turn that one scene on or off... One time.... no repeat statement. They'll all go on/off appropriately at the same time I know this approach is different than you're asking, but the chain of separate devices coupled with the loop 150 times is going to give you unreliable results.

What is the house code / unit code... Not J is it? I would temporarily shift the house code to something else, and wait and see if it repeats. If it does not, modify your programs to the new house code

Like @IndyMike, I want all my premise lights to on/off in unison and a certain actual dark level outside. Where I live in the US, dusk time is not a great program trigger as it could be very cloudy out (needs to come on sooner) or there's snow on the ground (lighter out and it needs to come on later). I made an Insteon, wired in dusk/dawn sensor. I put it in a small project box and its behind the drapes in a window inside my house that faces south and all that can be seen is a cable plugged in the wall coming from under the drape. It's not that big or noticeable. It can trigger Insteon devices anywhere Insteon reaches. It uses a micro on/off module and a lamp photocell sensor from amazon or home depot. See the post below. You can scroll around in the post to find out more. I also wanted to get away from battery powered sensors. IOX programs let me delay the trigger of the lights a little as the sensor turns them on too early, and I can avoid dark clouds, etc blowing over in the middle of the day triggering them