lilyoyo1

I don't use non toggle options. I keep mine in Toggle mode, set device to their proper state and use programs to turn off the kpl backlight when necessary

See adding devices

Won't help with what you're trying to do. They lock needs to be closer to the isy

Change default to off and see what happens

Non toggle on=buttons on Non toggle off= buttons off That's how it's built into the device. You can always create a scene, add the button to that scene, and then create a program that turns that scene off anytime you physically press the button after a second or 2

If it's not close to the isy it won't exclude or include

FYI- if the ISY is not aware of an insteon device, it will still add due to how the protocol works. However, since it is not part of the isy data base, it will not have the necessary information needed to have the proper settings of the device. You would get a different message during adding and how it shows up. Since yours says that it cannot determine insteon engine, its recognizing what the device is and so forth....Its just not able get all the information it needs to complete the process. Most times, this comes down to communication between the ISY and device, incorrect code for what that device is reporting, or something happened at the factory which a factory reset wipes out. I attached an image of what you would receive if the ISY did not have the 2477d in its database.

The Id could be incorrect. Follow the instructions i gave previously and you don't have to worry about typing in the id

If that was the case, it would still add to the isy. It would simply say unsupported device type (something along those lines). With that said, it is still in the console.

Nothing. The universal heal had been removed and replaced with update neighbors for individual devices as this is the best method for updating zwave devices

There's not a large contingent of irule users on here. You're better off going to the irule forum with your issues

Highly unlikely to cause any problems. Many people on here are (and have been) constantly writing new links for years without issue

I hope so too. I'm pushing for you

I know it's a personal thing but I'm all for you continuing insteon support. Especially with their newer devices coming out. Besides that, too many users are already entrenched with insteon to abandon. I'd be good with an off the shelf zwave dongle. Not only would it be cheaper than a purpose built solution initially, it would be easier, faster, and cheaper to upgrade each time a new version is released

I just googled the terms I wanted to find. I rarely use the search function

Factory reset the switches. Try adding by choosing start linking and holding in the set button on the switches

Does your UI and firmware both match

Per the usual- No! Michel has said they have it running on Polisy but still working out the bugs

I recommend creating scenes and seeing how things behave with different settings so that you have a better understanding how things work together. Here is a previous post on how what the commands means https://forum.universal-devices.com/topic/23417-intseon-command-default-ignore/

It's in the same section that you put your user codes

That is correct

What do you mean? The isy has always supported locks since they implemented zwave support

You should be able to do the same with the isy

Neither can really add functionality that doesn't exist in the lock. The firmware shouldn't go backwards in regards to what the lock can do. It's not a dongle issue either as the dongle works well with 5.0.16. The only way to take full advantage of the dongle is for all devices to be Zwave+. That's when you'd see the benefits.

I use yale in all of my installions and have found that 5.3 pretty much breaks everything with the locks. 5.3.2 doesn't fix being able to see the different options either that the lock allows you to see. I've subsequently rolled by to 5.0.16 and recommend the same for yourself. I did submit a ticket to UDI about the issue some time ago. Hopefully @Michel Kohanimwill be able to chime in about when a fix may come to get back functionality with the newer (or upcoming) firmware