lilyoyo1

You can't really remove buttons from a kpl from the isy without removing devices. As mentioned, this wouldn't make a big difference anyway. One thing to look at is how you design your scenes. For example, I don't use controllers in my larger scenes. I add devices to them as responders and then use programs to turn on/off. I also reuse scenes where I can. For example, each room has a scene with everything in it. Whether it's my good night, away, all off, emergency, etc, those scenes are used in them. That allows me to save on links since I'm not creating additional links for stuff I'm already doing.

You need to move it closer to add and will probably need repeaters.

Are those devices still individually activated or part of a scene? Post your new programs for us to look at

Why separate scenes when they do the same exact thing based on the same conditions?

One thing I would start with us adding all of those devices to a single scene and controlling the scene itself. It's a more efficient user of resources and you don't have to worry about commands being missed. I would also change the 0 seconds to 2 seconds to ensure good communication

I think the fact that you're using a single hub for 2 setups is the problem. You could try renaming to totally different things to see if that helps I would also look for a pattern to see what is going on. My suspicion is she is looking at the first or last "scene" that was used and responds accordingly since the beginning structure is the same

After a second look I realize you're using status. Change that to control and it should work

You need to activate the scene

You need to go to an Alexa forum

No. However if all of your devices are part of the isy, a simple program would suffice in place of a Google routine

I think we're all in that boat

We rarely use voice control. That's one thing mine hates. Everytime we do use it, I make notes and look for ways to automate what happened. I'm trying to make my house responsive vs reactive

Mine felt the same way until she first experienced it. Now she hates staying anywhere because of how things are at home

It's not. It could be added by simply telling Google I'm home and then running the corresponding programs. Instead of Google routines, I use isy programs. It accomplishes the same things. Just more efficiently. Motion sensors can work. The downside is that they don't know who entered. By using your lock vs sensors as a trigger, your setup becomes personalised which is more automated than having to tell the system you're home

All that depends on what you're trying to accomplish. In all rooms outside of the theater, I use Harmony so it's that node server. I have Sonos ones in all the rooms as well so the Sonos nodeserver is in play as well. With you using Chromecast you would just use your same setup as now with av remote. My setup starts at my locks. Since we have separate codes, mine does what I want and my wife's does what she wants with hers depending on situation If you let me know what you want to do, I can give you better information to make it happen

Why not have the isy do that itself? Using Ifttt would make it even slower than it is now. You can use Nodeservers (requires 5.0 newest firmware) and isy programs. Currently, when I come home (assuming house is empty), the lights that I want will turn on as well as the tv. Depending on time, if it's late, the bedroom TV will turn on instead of the family room TV. The path to the bedroom will light up so I'm not walking in the dark and turn itself off. Had I wanted to, this could've easily been music instead of TV's

What's wrong with black? ?

If you're using the nodeserver then you would use the WiFi version. If using zwave then you wouldn't need the nodeserver. Zwave distance varies. My general rule is a repeater every 30 feet open air. 10 feet for every wall between it and the isy. I generally will use at least one repeater that supports beaming rather than the isy directly talking to a device.

If you want to use each button as a toggle, I would use variables to track what was done and turn things on/off that way. With that said, as long as it works then you're good.

That's simply over kill especially if one has a large network. The hour it takes to fix problem programs (for most people) is waaay less than the time it would take to rebuild a whole system

I'm referring to your test device as well. The reason I stated what I said is that you were testing in a location that is different than your original lock. If you did not do a network heal with the lock in that location, the ISY may have trouble talking to it. Also, If your repeaters in that particular area does not support beaming you would encounter problems as well. The reason I bring these things up is that you earlier stated that you would move the lock closer to the ISY and then do your heal which is incorrect. Since your devices are over 7 years old, there is a good chance that the repeaters in that particular area may not be capable of beaming as many early generation zwave devices did not have that.

Most likely both are trying to send and receive messages from linked devices causing a collision somewhere so a responders message isn't getting back to them

Having repeaters is good. Having the right type is Paramount. Your repeaters must be capable of beaming. If they aren't then that can change things

Putting it near the isy and healing your network is the wrong move. It needs to be located at it's final location so that the path of set properly. If it's by the isy when you heal then move it, the isy will assume it's nearby and try to talk to it.

Is it in the same location as your other lock? Different locations may yield different results due to your zwave network. Also, make sure you aren't locking/unlocking too quickly as this can affect results as well