It can be hard to get answers there but this more of a HA problem than an eisy problem. You'll need a solid/stable HA server to add Integrations like ISY and it doesn't sound like you're there.

For ecobee, the most direct connection is through the HA HomeKit Device integration which uses bon jour to talk to it directly making it a totally local, cloud free connection (as long as its on the same LAN segment).

3 minutes ago, Dr. Q said:

It would benefit me to take note of the Insteon addresses in the HA integration

Yep. More time planning / organizing will speed the whole thing up

Truth be told I had one I bought a couple of years ago to announce for leak sensors and sump pump depth alarm in my basement . One of the leak sensors was in a well area and the floor gets damp there... so it went off as it should but not really an emergency. I was able to move it a foot or so to still work but not false positive. But that event was not a hit with my wife as it was not a real problem and home automation took a shot on goal when its otherwise really good.

I got rid of it. I had the same problem with yolink version. Too screamy. Still looking. I also don't want to keep adding things like zwave, zigbee, wifi etc to solve one problem and throw other topologies at the problem.

.. and I thought about that old X10 chime that gave a nice beep ..... beep ... beep several times.

In systems like Indigo, HouseLinc or Home Assistant, the PLM is the system of record and the automation software looks there and "pulls" the network data from the PLM.

The UDI / iox controllers on the other hand are the system of record for the Insteon network. These controllers maintain the master link table and "push" it to the PLM and Insteon network as each device as added.

As mentioned above, what you want to do is not possible with the ISY.

There is an older lengthy post. This particular comment covers it. If you are hemorrhaging time, you could read the whole thing, but picking through it won't hurt.

My recollection is that there are features in the device's panel when you add it to iox.

That is a sign. If either restore PLM or unplugging from the wall and replugging fixes it... highly likely a dying PLM.

Look at the link table count can help, but..... wait for it to happen again as once you restored, it has its memory of links back for a while.

If it is a failing PLM, these events will cascade until its finally dead.

I had one of those X10 modules as an alert for an automated garage door before closing it.

The Insteon on/off plug, like most Insteon device can be sent a message that will create a very brief, kind of quiet "cheep". It's meant more for diagnostic use to know that the switch is being linked or has a problem. It also can be used in debugging iox programs.

Insteon makes this siren module. It has 2 responses: It can make a door bell-ish ding dong like walking in a store, or a screamy siren sound that has scared my family members, pets and probably the plants.

It's not clear from the post about the continued role of X10. I don't think the current release of Insteon products respond to X10 any longer.

UDI announced that the 994 series was end-of-life almost 3 years ago. If there is newer software, I believe one of the Help drop down menu items would indicate you could upgrade it.

How did you replace your plm. Did you swap new for old, or did you follow the plm replacement procedure to get the new plm's address into the insteon devices?

The symptoms suggest the first of those 2

1 hour ago, Ross said:

@paulbates Paul, will you please let me know what you replace the IOLink with? Hopefully something from YoLink.

Thanks,

Ross

To clarify, I only used the sensor side of the iolinc, not the contact closure feature. For that, I used this yolink contact sensor: YS7707-UC

I was hesitant because it is battery but having no problems. With it. I replaced an iolinc monitoring my sump pump and the cycle times line up with the iolinc.

If you go this route, note that the sensor has a red LED that comes on initially when contact is sensed... for like only 2 seconds and then goes right back out. Made wiring kind of interesting as I thought my wiring was messed up.🤪

How old is the PLM? If you don't know, there's a little white stick on the back with 4 digits, what are they?

Have you had a major power event, eg brown out, black out, nearby lighten strike?

Did you un-plug, wait 10 seconds and re-plug the PLM and retest?

10 minutes ago, MikeB said:

I was previously getting the warning about the skill not being upgraded to support the latest version of Alexa.

That is a different problem. There are 2 ISY skills for Alexa and I think most people were using the newest while also having the prior one loaded. Amazon was taking the worst case scenario by reporting the older, V2 ISY skill

The iox/ac value is the fw rev and what's on the switch is hardware rev. Sometimes the fw version is there too. Iox reads the fw version off of the switch.

What's important to know is that both values are essentially "academic" values as the FW of Insteon switches is not field upgradable by the user. What you bought is what you have.

I know there's' a lot in this thread ..

Does shutting skyport cloud api from the thermostat's menu help? Skyport cloud had growth issues +10 years ago and it trampled on local activity sort of like you're describing.

My experience with the color touches was nodelink and that was a very good experience. I only stopped using them because I moved from that house and left them and the system there.

What I recall about the API is how transactional it is, meaning it's only as good as the last call to it. I would not be confident about it juggling more than one client at a time.

The question is, are you simultaneously connecting to the same stat with both nodelink and the Venstar plugin? The hardware/linux in the colortouch series is pretty limited. If "yes", I would stop one of the the 2 clients, pull the stat off of the wall to reset it and try again,

FWIW, earlier this year I retired anything Insteon that was a sensor, either iolinc, MSII or leak.

"All On" events are limited for me since the majority of my devices are "All On immune" i3 paddles and i3 outlets. I have some dimmers and micro modules which are susceptible to the all on, none of them have come on randomly, unexpectedly, since that time

I switched to yolink sensors. It does add a small but noticeable delay for motion lighting compared to using the MSII, but this trade off is better for me.

Functional Devices makes contactless sensors that provide dry contacts when the Hot lead they're wrapped around is active. The sensor itself has no moving parts, no battery or maintenance.

My use is for monitoring my sump pump activity, and the contact sensor I use is the yolink. It's small, wireless and battery operated and runs for years. Its accurate and reliable.

In your case if you bought a RIB for around one of the hot(s) from the panel(s), and the yolink hub was plugged into power like the eisy, the eisy would get a simple on and off.

The yolink LoRa radios can go up 1/4 mile between sensor and hub and provide great sensor battery status.

For the RIB sensor, I called Granger, gave them my specs and they recommended the right one.

So what you show there has worked for me and in the past. The new variable in the equation, for me, is Apple. I think they have their own handling for priority alerts? Check the ios settings for the pushover app for critical alerts

When you change the priority, there are new parameters you have to add to the string..

• retry = how long in seconds to wait and retry if the message isn't received

• expire = how long in seconds until pushover gives up

&priority=2&retry=60&expire=3600

Both are "academic" in that I can't image what that would prevent. But pushover won't budge until you send them

Pushover is mentioned and the post is under ISY994. But also email is mentioned. And iPhone.

I don't understand all the links and what the chain looks like. Provide the technical details... If its pushover on a 994i than likely you're using network resources to create the notification, show that if so.

If not, what facility are you using for pushover notifications?

Zigbee and Thread traffics share Physical and MAC layers and can coexist over-the-air.

However at a network and App layer, they are mutually unintelligible. One does not get you the other. Zigbee does not use IPV6

1 hour ago, PeterP said:

Do I need to keep adding those additional trigger buttons as responders to my "All Off" scene and set them to "Off"? My concern is that it's creating a super-bloated scene. Is there performance issues to consider? A better way?

No better way. The performance might be felt only when managing the scene.. adding, modifying or removing scene members. Especially if any of them are wireless sensors, which doesn't sound like the case. The scene itself is a single group # programmed into all the scene members. They all wait for that one group number so, no, run time performance is not a factor.

What can be a factor is that the PLM can handle 1000 links and large scenes can affect the approaching or exceeding that.

1 hour ago, PeterP said:

I want to have multiple "All Off" buttons throughout the house (eg. one at each door, a remote for the car, etc.). Is there a way to add another controller to my "All Off" scene without having to re-do all of the "Insteon -> 0%" settings for each device within that scene for the new controller? (Like... copy default settings from controller A to controller B within this scene.)

No sure I'm following. Each new controller in a scene activates the scene... that's it. A controller activating the scene tells each group member to do whatever it's been told to do for that scene.

A follow up is that scenes are a one time, fire-and-forget Insteon moment. Large scenes increase the odds that one or more member doesn't hear it.

Look under the config tab in iox, there's a checkbox option to turn Insteon capability on or off. What you're describing sounds like the symptom of it being unchecked

2 hours ago, aLf said:

I'm all ears...

How do you set this up? 994?

I was also told that "Home Assistant" would import all of ISY and it would provide notifications. Anyone done that?

Thanks.

There is a Home Assistant Integration for UDI products.. Think of it sort of as what a plugin is to eisy. You install the "Universal Devices ISY/IoX" integreaton on your local Home Assistant server on you local network, and configure it to log into your ISY on your local network.

IMO the Home Assistant built in notifications are very unsophisticated, good for debugging programs, that kind of thing. The don't seem to be kept for long after you view them. I think UDM notifications are more sophisticated / better.

For Pushover, another option if you have a policy / eisy, is to get the paid for notification server plugin from the plugin store, it works very well and has options galore. This gives details on how "how to"

9 minutes ago, BCreekDave said:

I'm looking into setting up Pushover using the Network Resources. If you have this option on your 994 it may be the best solution. Still in the learning mode.

That is a no regret solution. It takes a little to set it up, especially the extremely long Network Resource links. But once you work through those it's a solid, fast solution that is relatively easy to change and expand to new notices.

Its additional advantages are what Pushover calls Apps. What they call Apps is actually folders, you can sort your notifications in different folders and each group has a different notification sound and a presence. I have house notices = report kinds of things like sump pump daily activity.. no notification, just there to review. I have another "App" for Battery levels, and one for House Alerts for critical things that screams.

Another advantage is that other non-eisy things like firmware upgrades for my router. Those come through an Pushover RSS feed from Zapier. There are a ton of alternative inputs