lilyoyo1

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

im asking about the keypad

Read the directions!!! Who does something like that??

is the red wire capped off on your kpl? if you have windows you can use the snipping tool to take a shot of everything and then copy and paste as normal with the picture.

That would depend on whether or not they have an open API for a developer to develop a nodeserver for it. A developer would also have to decide its something they want to take on as well.

What is your ISY UI and Firmware? How did you wire your fanlinc and kpl? Sounds like you may have wired your kpl to directly control your lights! The red wire on the kpl should be capped off and the line wire to the fan should be connected to the power and line switch on the kpl together. Copy and paste the actual scenes that you created. You must configure the controllers in each scene as well as the scene itself.

I would wait for him to return before messing with the work he's done. We all have our styles of setting up the isy. Someone doing something else can throw off corresponding programs breaking stuff or causing loops. By going on top of his work you could be creating a bigger headache for him and yourself.

https://forum.universal-devices.com/topic/7462-run-at-startup/

when you manually tap the iolinc, does it work?

You can always reach out to UDI about their plans for the heal. I'm sure it's still referenced since there are other firmwares out there that it's part of. It may also be something they are working on which may come back.

If both devices support the same associations it is possible to have a direct link with zwave devices so that they work outside of the isy. However, the isy will not know about that association so it will not update the status of the device once on (or off) depending on situation. While this may not matter, this can affect how your programs work. For overall best results, you'll need to let the isy be the middle man. There will be a delay but the experience will be much better