lilyoyo1

Try to remove/exclude from your Polisy. Once done, manually factory reset the lock and then re-add

It would help if you provide pertinent system information such as firmware AND UI, whether you are using zmatter board or some other usb stick, and what generation board your yale lock has

Not necessarily. Even if communication isn't broken, you're still better served having them than not having them. The strength in zwave comes from having a strong mesh network than just a few devices. Network density matters more than range. By having additional devices, you're creating more pathways for communication rather than having a singular path. It's sort of like trying to yell at someone down the street. If your voice is loud (greater range), they may hear you. However, does that guarantee they'll hear you every time? Now picture the same scenario with 5 or 6 people in different places between you and them (network density). The chances of your message getting through is significantly higher. In addition, it depends on the generation of your devices. Zmatter's range is greatest with an all 700 series install. Anything lower and your range can be impacted. There are no guarantees that will help you. If your current path is terrible, it may help but it all depends on how zwave chooses to route itself. For example, 2 of my bedrooms use an outlet from the 4th bedroom as their closest neighbor even though there are multiple devices much closer to the pathway. Some of my devices aren't even being used as repeaters. With zwave being self healing, even if you could control the outcome, whatever path you chose will probably be overridden. Your devices will look at what takes the least amount of hops to get the job done. Sometimes this may not be the most direct route (similar to Google maps routing) If you're having issues or simply curious that can help. As I've stated previously, the self healing properties of zwave makes it a moot point. Since you stated you're replacing your insteon devices with leave, long term this will matter even less. Network density (within reason) matters much more for an optimized network than anything else. By having a multitude of devices, you're giving your devices many more routes to take should something happen. It's akin to driving around. If you're in an area with 1 way in or out and something happens then you're stuck. However, it'll there are 5 or 6 different paths, you have a greater chance of bypassing traffic.

This isn't a 1 size fits all situation. You could write a program that if any of the individual switches are turned off, then turn off your keypad button. Based on your setup and how you control your home, status may need to be used

If you upgraded from 4.xx to the latest firmware, the instructions on the firmware page states that the password was reset to default

That doesn't make any sense. You want to trigger your devices to turn off but you want the same button to turn on.... Why not just use the regular toggle mode and you'd have it turn on and off. If you don't want the light to stay on, just add a line to your program that turn it off after a second or 2

I think interference issues are overblown. I've done enough installs with C4 and hue bulbs without having issues. Granted, every home is different so it can potentially happen. If there were to be wide ranging issues, I can see it being more from lower quality devices than better quality ones. In addition, depending on UDIs implementation, you may be able to set the channel that ZigBee uses outside the range your network uses

I'm aware of how it runs. Because of past statements from Michel, I wouldn't be surprised if they released both together as it makes sense from a development standpoint

With all of the bugs so far, I wouldn't hold my breath

No it does not. Thats just it's behavior to let you know it's being triggered. If nothing happened, a person may not be certain if it triggered.

If the switch is set to non toggle off then it's sending the off command so your program wouldn't work

I think all would be enabled at the same time since Matter uses zigbee

Try a restore plm and once done restore devices

Whether it works or not, most of us here used the isy prior to the portal. While your method may work, most people here go by the proper procedures to lessen the chance of something going wrong. Clearing java cache has been such a tried and true method that avoids so many potential issues, it's hard to let go of for some of us

There's no right or wrong way. Everyone has their own way of programming things for various reasons. Some people prefer the cleanliness and efficiency of scenes while others may be ok with drawing things out with programs (and the perceived effectiveness of it) despite the experience. Neither is wrong. It's whatever works for you.

You're overly complicating simple programs. The benefits of insteon scenes have been covered countless times in the insteon white pages, thousands of posts, the wiki, and isy cookbook. Scenes was mentioned because they're infinitely better than what you're doing with programs. Programs can't make up for poor techniques and issues. Using band-aid solutions such as programs to fix issues only serves to create more issues long term. It's a rabbit hole you don't want to go down which is why Geddy said something about fixing the actual issue. This is what contributes to making programming hard to understand. In a sense you're turning simple math into an algebra equation.

Where would you suggest they put it? UDI like most businesses will do things based on the majority of their users. Many many more people will leave their units on a shelf than those who will mount their units in hard to reach undesirable locations.....This is especially so considering the need to scan a code is something that may be needed once or twice while in use

As with anything like that do a restore. Sounds like plm shot

Isy994 is discontinued and will no longer receive updates so it will not work with the new devices

The best thing for you to do is buy a few different dimmers and try them. There are thousands of mfg out there and countless different models (not including changes made to their same models).

All scenes need to be created by the isy for it to be aware of them. If you did this manually or with some other software, the isy wouldn't know about it and you would need to set them up via the isy.

The information on needing an ELV dimmer was pertinent to the conversation. Eaton and levitation are the only 2 zwave companies that I know of which makes ELV dimmers. There may be others but I'm not aware. Lutron caseta dimmers are also ELV

All of them including insteon. https://forum.universal-devices.com/topic/34826-zwave-700-series-tips-and-tricks/

I don't use solar edge so I can't comment specifically on that one. Noderservers allows you to use 3rd party devices with the isy that are not natively supported. What people do with them depends on the node server. For example, you can use the Sonos Node Server to control the volume of your Sonos devices are start/stop them.

You're on your own with this question. Most (if not all) here werent in your position when they upgraded to speak on all the what ifs. You can downgrade if you need to but we can't say how any would effect your system.