lilyoyo1

It could very well be something else. However in troubleshooting, Michel is going for the most logical explanation first vs lesser options that may be out there....While it may suck if other devices cache are cleared, sometimes hard choices have to be made in order to troubleshoot and get to the root of the problem

Amazon has been having issues with their servers. That may be causing issues

Add your responders to your scene first and configure them. Once done, add your controllers. The Isy will automatically set the parameters in the controllers. Unless you want the controller to be different than the scene, this will save you time and effort

Is the inlinelinc part off the scene and did you configure both the scene and the controller for them to be off

Scenes do not override anything. When you turn a scene on, you are simply telling another device to turn on, off, or to a specific level. If you manually control a device that is part of a scene, it will do what you tell it. What exactly are you trying to accomplish

Those that know would not be able to say. If I had to guess, I'd say second quarter next year. Third at the most

There's 2 ways. The first sucks but is best. Factory reset devices. Do remove zwsve device (something like that) in ISY then add Zwave device. If you don't want to go through all that, in the Isy do remove devices from the furthest to closest. Then add devices from closest to farthest. This works if you have all zwave plus devices.

It's true that it can still happen depending on the lights. The 2457d2 requires a minimal amount of load (5w I believe) so if your lights do not meet that level then yes it'll happen

See post on previous page on the subject

No. Not if done from the panel. It'll turn off of you manually control the device. When using control, only physical presses will trigger the program

Zwave isn't more stable than insteon. Both have pros and cons. Depending on environment and setup your system can be really good or really bad with either one. People tend to blame the device first and move on when reality is, it's usually something else. You can keep the 300 board and upgrade later. However, as with any upgrade, things don't always go right. You could end up spending more time fixing things after upgrading vs just doing the right thing from the start. Not only that, it's much easier with PLUS due to increased range and network wide inclusion to add devices than it is with the 300 series.

You need to go to the Amazon forums for help

If you're going to switch over, you might as well upgrade to the 500 board and use all zwave plus devices

Clear your Java cache and use the launcher from the 5.3 forum page

If you're using mobilinc connect them that's why it's not working. You can't have that and portal. You'll need to contact udi and have them remove it

Id factory reset everything and start fresh. Make sure the Isy firmware is up to date, clear your Java cache so that firmware and UI matches

Did you clear your Java cache? Also make sure you're using the new launcher as well

When it comes to the Isy, most times, the easy way turns out to be the hard way long term.

No. Having homekit support means they added homekit support. Not that they have an API that someone can use to developer a nodeserver for

Sounds like you added the device by choose add existing links. It may not be there. Could be an old link from something else that's always been present. 1 of the many reasons everyone recommends factory resetting your devices when switching systems. What does the Isy say the device is? What did you use prior to the Isy? It may be the Id of whatever hub you used prior

No problem. Glad I could help

In the admin console, click the Network tab. All devices will show up in the middle of the screen. You can see the name and device address for all insteon devices.

The page you linked to is a good source. All you are doing is clicking on each controller and configuring each device the way you did for the scene itself. You set the fan to be the speed you want for that scene and the other buttons would be set to off.

Theres no copy scene attributes in 5.0 You need to configure the controllers for each scene as well

Did you configure the controllers as well? The controllers are whats in red