lilyoyo1

Yes

Directly no. Indirectly yes as there probably won't be any updates to it ever again. It's not worth swapping out unless you have all 500 series (or above) devices. It won't stop working with your devices

You didn't have none as an option so that would be it for me. I may use voice once or twice a week if that

You definitely have to upgrade to the new firmware in order to swap your 300 series to 500 series dongle

You have the old one. The 4.55 is the firmware for the old version

Originally you said a fast on which changes the dynamics of how things would work. The added detail helps alot. When a controller is linked to a responder, a fast on will cause all linked devices to go immediately on at full brightness. The will override any ramp rates, dim levels, or devices that should turn off when the scene is triggered. If none of that is an issue then you can leave your device as a controller in the scene. If you want to have some light turn on at a specific ramp rate or dim level and/or turn off when a scene is triggered; you are better off, separating the controllers from the scene. For example, my bedroom lamps are controlled from 3 different locations. I have a scene created where all 3 are controllers of each other. I have a separate scene created that turns off lights that I don't want on when the lamps are on. In the evening a single tap will turn the lamps to full brightness and turn my responder scene off while a dbl tap will turn them to half brightness and turn off my responder scene. After 10, this reverses itself. Since you only want something to happen with a fast off simply program a fast off to do what you want. In this case, the use of "or" for each controller would be sufficient in a single program.

Then it probably wouldn't matter since the issue is with the zwave board which is separate from insteon. The bug is causing zwave issues not insteon

I typically separate my off program from my on. This allows me to easily override my off programs or have multiple programs without causing issues with one another. If motion is switched off And motion is not switched on Then wait 5 minutes turn off

Each button needs its own fast on program unless the action will be the same for each button press. In order to make sure it works properly, Those buttons cannot be controllers in the scene itself. They can be responders so that their status will be correct whenever a button is pressed.

That is correct. I add it to the room in the portal (and alternate names) and then my connected service. I do use programs to trigger my stuff instead of the scene or device directly. Instead of trying to control every individual light, I use it to turn on what we use mostly. If I tell it to turn off the lights it will turn off any light that's on.

All of my fans are located in their respective rooms and labeled simply fan. I haven't had an issue with that. Are you sure you put each tv in the proper room?

I'd say give it a shot since it's free. If you don't like it, then you can always return it and use the voucher for something else

You're explaining things are different but not saying anything at all in regards to how they are different. I think it would help others if you have an example of how their programming allows you to do things that you can't do with the isy

The isy should do all configuration for you. Nothing should be done outside of the isy (except for specific tasks such as changing 6 button to 8 button and vice versa) With that said, both programs and direct links via scenes have their place. It simply depends on the situation. I'll use a program when I want 2 different outcomes for the same switch. For example, In early evenings, my lamps will turn on full brightness when I hit the lamp button. If I want them dimmed, I'll double tap it. Late night, it the opposite. They'll turn on low and full brightness with a double tap.

Its been covered many times but while there are some that has had issues, there are many more without. Generally, if things go smoothly there isnt a reason to come on here. If a person has issues they come on here for help which is why it seems like a lot of people have issues. Its the nature of the game. There probably wont be an upgrade tool available. Verifying things should be done anyway after any firmware update as a best practice to ensure everything functions to avoid nasty surprises later. Most likely your scenes themselves should be intact as they would be insteon only. The really good stuff involving scenes do not occur until 5.0 when zwave and other nodes such as hue are able to be added to them. As Larryllix alluded to, problem programs will have a yellow box next to them. I still re-save all of mine individually as I've found that sometimes they wont fire properly if I dont. There are quite a few posts written by people who has had success that detailed what they did. I wont rehash those posts but will give a general run down of the main points Make a back of of your current system. You should always do this regardless before upgrading to anything. If you have zwave, back that up as well. The zwave backup is separate from the isy backup. Take pictures, screen shots, or copy/paste your programs so that you can reference them later. Depending on the install size and program amount I use the first 2 methods as I can split screen what Im doing and go through each program 1 at a time to verify any changes I need to make.

Most likely the device isn't awake

Was the isy unplugged when swapping plms? The plm needs to be connected to the isy and posted up before the isy

You can already do this with Alexa and Google home. I'm not sure what you are trying to accomplish from the isy standpoint that already isn't possible

I wouldn't do it. While people have been able to get away with doing so, you could potentially shorten the lifespan of both products. Use the correct tool for the job. Do you really want to replace a $50 switch in 2.5 years over spending an extra buck for a dimmable switch?

It could be that too. You also have twice as many zwave devices as I do so more opportunities. Have you tried using the dashboard instead of AC to see if that cuts down?

I haven't had that issue. I do the same when I initially set up devices but then choose freeze once done. So far I haven't seen any new nodes but time will tell. I also dont look at my device tree unless I need something specific so that may contribute to why I haven't noticed

Probably not. Zwave creates new nodes sometimes. Just delete it. Then choose zwave>options>freeze nodes to prevent that from happening

I prefer hue over lifx. I think their setup is more robust though lifx lights themselves are better

You would need to use a nodeserver if you want things directly within the admin console. I prefer to set things in the app as its easier to see and manipulate, then add to the ISY.

I'm opposite of larryllix in that I use scenes predominantly and use programs to add capability to them. I prefer scenes mainly due to the fact that I have manual control over my devices regardless of the isy. For me, it's paramount that my system works outside of the Isy. If the isy dies how do you operate things? Unless you have one laying around your system is down until you get a new one. At least by setting scenes, you can operate the pumps from home with a kpl as needed until then.