oberkc

Well...I am not quite sure what you are trying to achieve here, or what hardware limitations exist, that requires (what appears to me) to be a relatively complicated set of programs. One thing I noticed, however, is that the first program calls to "Run Program 'Motion1 - Timer Set' (If)" but when I look at the program 'Motion1 - Timer Set' , there is no (if) clause. But I tend to think like @Guy Lavoie , if it is working for you, I don't see a reason to modify the programs.

Well, I am quite confident that you can use a program to increase or decrease brightness or color or tone, I am unsure how the innovelli switches relate to the hue bulbs or weather you can adjust the response to the inovelli switches.

I once tried using a Hue bulb with the Polisy via zigbee. It did, in fact, connect and I was able to control it. I found, however, that the level of control and features did not match that of using a hue bulb with the hub. I have also used the hue bulbs/hub with network resources. This is quite reliable but does not provide the ability to use hue devices as a node in scenes. Given this, I prefer using the hue hub and hue node server. I have no experience with the inovelli switches.

If the suggestion from @larryllix does not work, make sure you have rebooted your EISY.

And, having just committed to avoiding new matter devices for a while, I may have to try one next time I happen to be near an Ikea store. I am so fickle.

That would make sense in isolation. Unfortunately for me, this was just the latest example of the weird and unreliable behavior of matter devices. (Even stranger, the next day, this device began working again.) This problem has occurred with all four of my matter devices, across three different brands (Govee, Nanoleaf, and Cync.) This is not a problem I associate as being caused by the EISY, but it is a problem that makes it hard for me to recommend matter to anyone at this point. I have spent far too many hours trying to make matter work for me and I will not be buying any more matter devices until I have some confidence these problems are solved. Thanks for your thoughts, but I believe I have hijacked this thread too much already. If something changes where I think UD can help, I will get back to you.

I definitely experienced some of this. This has NOT been my experience. Yesterday evening, and not for the first time, a matter (wifi) device added three days ago stopped responding in all hubs (EISY, echo, google). The matter device (Govee, FWIW) remained connected to wifi and I could control it via its native app and its "works with Alexa" integration. Another Govee matter device continued to work (but for how long we will see). No...for me, other matter connection issues are NOT usually related to "dropped wifi networks".

Unfortunately, based on my experience so far, adding matter devices to Alexa/Google/Apple/EISY only to find them losing connection later, then gaining it back, then losing it again, is not uncommon. This happens to me regularly and not just with the EISY. This morning, for example, one of the devices I added yesterday lost connection with Alexa. Sometimes I find that trying to turn on/off the device from one of the hubs will re-establish communication. Sometimes, power cycling the non-responding device can work. I have had some matter devices simply drop wifi connection. Sometimes, nothing works besides deleting the device everywhere, factory resetting the device, then re-adding. Still, it seems as if matter is making progress, if a bit slowly.

Yes, by first adding to Alexa, then sharing to google home, then sharing to EISY. Until recently, this has not worked for me but now does. I have two Govee Devices, a Cync Bulb, and Nanoleaf (over thread). We will see how long things stay connected, but the way things worked this time, I am hopeful that this matter connection will last. There is a bit more history to this than I let on here and if you are interested, send me a PM.

Well, for what it is worth.... There was an update to IoX to version 6.05.something. It claimed to include improved matter support. I assume it is not coincidental that I have now successfully added a couple of matter devices (those relying on wifi). Even now, however, adding the Thread device continues to elude me.

Do you have the zmatter board? My experience with matter so far is not good. I have echo and nest border routers but cannot successfully share several matter devices (all lights) to EISY. I have not tried the Aqara devices. I used zwave for shades, and they work very well for me. In fairness, I have a decent number of zwave devices in the house and this may help with communication, but Zwave would be my recommendation based on my own experience.

I have been experimenting with matter, both wifi and thread. I have an Echo hub and Nest hub (2nd generation) border router. I have several Govee devices that support matter over wifi, a GE Cync bulb that supports matter over wifi, and a Nanoleaf bulb that supports matter over thread. All of these devices are successfully paired with google nest and shared with Alexa, via matter. All can be controlled by Alexa and Next. At this point, the only device that I can share and pair with the EISY is the Cync bulb. I had two Govee devices (Table Lamp and Permanent Outdoor Lights) that I once had paired with the EISY but, without warning or any reason that I could identify, quit working from the EISY and no amount of resets and re-pairing to date has been successful. The Nanoleaf bulb has been intermittent with Alexa and Google, but as of now, seems to be working. I think it once paired with EISY but certainly will not do so now. I don't know if Alexa and Google are updating their matter standards (currently v1.4?) or whether doing so is rendering the EISY incompatible, but matter on the EISY is generally not working for me (or I am doing something wrong) and I have mostly given up hope that the current version of IoX works reliably with matter. I have not tried any Ikea matter devices. I will be interested in hearing whether anyone has any luck with these.

Some times it is best not to sweat the small stuff. 🙂

Don’t know, but I have just come to expect, and accept, it. It seems about every six months we get a bunch of new topics about daylight savings time. This year less so. I guess many of us have come to accept it.

I believe the simplest approach would be to have two programs. The first: if status keypad is unlocked then run second program (if path) else nothing The second program, disabled: if time is from sunset to sunrise then run entry lighting program (then path)