GRYBD1

I have Matter (Thread) devices and no Zigbee, don't expect to ever buy a Zigbee device. While not ideal, a choice between Zigbee and Matter, defaulting to Zigbee, would work just fine for people in the same situation and not affect current Zigbee users. Thank you for all the effort you are putting into delivering Matter support.

My home is all Insteon lighting along with a half dozen Matter (native Thread, no Wi-Fi) device that I have been experimenting with. A few additional devices are ingegrated using Polyglot. Currently I have two functioning thread border routers, Apple HomePod Mini and 4th gen Echo Speaker. The result is two independent thread networks. While the networks don't talk to each other, all the Thread devices are connected to both networks. Changes made on one side show up without perceptible delay on the other. Everything works! One caveat is that special device features that are not part of the Matter protocol such as power monitoring reporting and color profiles are only supported by vendor specific apps. So those details are not manageable or visible in the Home or Alexa apps. Looking forward to the time I can see and manage the Matter supported features of Matter-Thread devices using all the capabilities of my eisy. My hope is that someday ZMatter will be another border router that my Thread devices can be connected to, and that each device will be a node in the IoX tree. Even better, but maybe the realm of Polyglot, would be support for vendor proprietary features of Matter devices. Maybe the stuff of dreams, but it would be great to be able to see the power utilization of my Eve Energy Smart Plugs in the UD Mobile app. Just being able to turn them on and off via IoX would be a wonderful improvement.

will never trigger Program Test1 to run at all. the only way the THEN and ELSE in that program will every run is if they are run by another program or manually run. Agreed.

Changes to the value of a state variable cause an event to be triggered. Program Test1 should only be run when the UD Mobile shortcut is pressed, it should not run when the value of the variable changes. Therefore, I believe an integer variable is the correct choice for this. Testing with an integer variable works fine, I have not tested using a state variable but suspect doing so would probably cause a loop.

Maybe too late to help but I think the goal can be achieved by using two programs and a variable. One program that runs when the status of the keypad button changes. It uses "status" and has the "Set" commands. In addition is updates the value of a variable. Like this. (sorry devices are names in my system) Program Test2 if 'Devices / 1st Floor / 1st Floor GR FP Lights / 1st Floor GR FP Lights SC' Status is On then $Integer_test1 = 1 Set ... Else $Integer_test1 = 0 Set ... With this program the keypad button should turn everything on and off. An important point is to make sure the then/else conditions DO NOT turn on/off any scene for which the keypad button is a controller/responder, otherwise you will repeatedly retrigger the "if" and get a loop. Having said that the keypad button does need to be a controller/responder for a scene, just not one that is set by the program. In the original example maybe leave "LivingRm Chandelier" out of the program and just let the scene turn it on and off. Add a UD Mobile favorite, a command button should work. Display Node: should be the integer "Integer_test1" Display Status: "Value" Commands: program Test1 SET Run if Using the "Configure" option for the for the UD Mobile favorite the color can be changed, and value displayed as "On"/"Off". Program Test1 if $Integer_test1 is 0 then Set 'Devices / 1st Floor / 1st Floor GR Lamp' On else Set 'Devices / 1st Floor / 1st Floor GR Lamp' Off Here the scene that is turned on/off must be the scene that includes the keypad button as the controller/responder. By doing that a status event will be created for the keypad button and the Test2 program triggered. In my example "1st Floor GR FP Lights SC" is the keypad button that is the controller/responder for the "1st Floor GR Lamp" scene. Turn the lights on with UD Mobile and off with the keypad or vice versa. Both will show the current status.