lilyoyo1

Is this an insteon only installation? It's surprising that you aren't having more issues since the PLM can only effectively handle around 900 links. It doesn't make any sense that the isy shows devices changing state but not programs. Post some screen shots of some of the non running programs maybe we can see something that you're missing

You're welcome. You didn't miss much...really, it was a waste if you've been reading a lot about it. I agree wholeheartedly with you in regards to the Isy. To me, the isy already does what matter promises....just on a smaller level. Overall, my take on matter is that it's for general consumption as a way to provide the masses with a way to easily integrate and provide some automation to their devices. Because they leave the ecosystem entirely in the hands of the mfg. I don't see things being any different now except that you may not need individual apps to set up your devices anymore. Even then, i can see smaller players taking that route by simply providing devices that work with the big 3. Larger players will still want to build out their own ecosystems that can then be integrated. Only time will tell but that's my take

Standards have never bothered me. I've always put my emphasis on my controller and focus on devices that work with that. The Isy has fit that bill for years and continue to do so as more technologies come out. I don't need access to all of them. Just devices that i need to accomplish what i want that are compatible with what i have.

I'm on the call. From what I'm hearing, I highly doubt there will be a bridge as it's up to the mfg. to support matter within their own device line. They really haven't cleared up anything with the call that hasn't already been spoken about. It does seem like the few companies involved are "all in" on matter so i doubt it'll simply be abandoned. My concern is with implementation since alot of the big claims that would make matter great are optional when it comes to company support. In time, they may tighten things up the way zwave has done but that remains to be seen

If you go to YouTube and type in Isy variables, they have some examples that can help you. Googling Isy cookbook will also bring up a guide that is still relevant.

Except the device the signal is for is 300 series. The signal leaving the controller will be for that along with the signal leaving the repeater. This is why a lower class series device in line kills things completely. The signal doesn't pick back up again after the lowest class series. Either way, while 700 series devices can help with distance, its not a catch all. That's why people still have range issues with the latest devices. The op is better served building a strong mesh network with multiple devices (700 series of course), to ensure strong communication

In the ops case it will be 300 since the receiving device is a 300 series device

See link provided above. Just have to read through it

That's device specific. You'll need to refer to your device others manual usually going on their website.

Most likely your first attempts at adding the devices.

its not your plm

Sounds like the perfect time for a new Polisy

No worries. Just showing how easy it is to find general information like this on the forums now. @Geddyput in a lot of time and effort to clean things up and make the every day items much easier to locate and use

It's not in the wiki. It's where it's always been under the sub forum software releases and updates> current releases. ***Thanks to @MrBill who alerted me that there is a link in the wiki which will take you to the current release subforum. I was incorrect saying it's not there.***

Its restore PLM AND restore devices

Potential future use

Factory reset per wiki instructions

If it's not under the battery compartment you can link it to another device and add that device with existing links

The Isy exposes everything within the device list which is why you have those extra nodes. They are part of zwave regardless of whether or not the mfg. takes advantage of it. It's complicated but some zwave devices can be directly linked to another but both devices has to support that ability and class that it uses. For those that do, you're generally limited to 4 -5 devices and they must be in direct range of the controlling device.

Yes, you need a hub with zwave and you cannot avoid the popcorn effect though it's not as pronounced as it once was. Any 700 series device will suffice. Currently zooz is most popular

From the way it sounds, i wouldn't worry about insteon. You have so many devices (and access to more) by the time lack of devices becomes an issue, the market will probably be different with to warrant taking another path at that time. In the meantime, ebay has become a dumping ground. There are so many devices on there, now is the time to buy since supply and demand has prices very low. I suspect it'll be this way for some time. Lutron is a great system but until Ra3 is supported it's a no go on here. For now, caseta and ra2 works. However, 5 years from now, that remains to be seen as lutron makes changes. That leads into my next thing. Worrying about tomorrow isn't worth it. There are changes coming to the market so things could be clearer/better by then.

Look at your first line. Program for what you want to know not what you don't want to know

Isy firmware AND UI? Did you configure the scene attributes and controller?

I stay away from variables as much as possible for many tasks. However, i will use them when multiple scenarios come into play as it's easier to manage things and keep running how i want and when I want... Especially as more and more talks are integrated and automated with cross capabilities. I agree that most basic things do not require them.

When I get that, it's normally after updates. A few days later it disappears. You can try to unlink and relink your account