oberkc

Yes, weird. It is hard to understand how the program is different before you made changes to the "dimming and timing".

Interesting. I have had a couple of LG TVs and I thought they also had the ability to disable the CEC feature, or whatever they call it.

I think the parentheses comments are a possible issue, but not the cause of your lights coming on at sunset, and sunrise. Your progrm will run the ELSE path any time the program is triggered (sunrise, sunset, switches controlled on) but evaluates false. Your program will always run ELSE path at sunrise and sunset, because it will always be false at those two trigger points. When that happens, the master am scene will turn on. I understand that you may want to accomplish your goals in a single program, but this may not be possible.

Thanks for doing this.

I have no need for the beta until the hub is available.

A little clarification might be needed. I understand that you can log into the portal, go to ISY web access, and see/control the lock. However, when you go to the portal and then to the connectivity>google home, the lock does not show up as an available device to expose to google home. Is this essentially correct? I can confirm that my Schlage zwave lock shows up in the portal/connectivity which suggests (in my mind) that it is not a zwave issue. I wish I could offer a solution to this, but the only thing that is coming to mind is that something has become out of sync and that a reboot of the EISY or portal might help.

I sure do. I sense that you are a bit more ahead of me. I am almost certain that google would not have controlled it. When I originally did this, I did NOT have a thread-capable nest hub. Since that time, I have added a gen2 hub which has thread. I have since reset the bulb and added to the new nest hub and shared with Alexa (also worked without any problem that I could recognize). I have since reset the bulb several other times. Will do, but it will be a week. Heading to Utah for some skiing.

Yes. I shared it from the Alexa to the google home app. I do not recall any errors. I do not recall any mention of a thread network, but this may be my failure to recall. When I originally added it to Alexa, I did not, and still do not, have the nano leaf app. Perhaps that is a variable I should play around with.

I have the echo hub and have successfully added the nanoleaf bulb as well to alexa. I could also share it with a google nest and control the bulb from either device. I have also originally added the nanoleaf to the google hub and shared it with the alexa devices. In all the various combinations I have tried, the nanoleaf would loose connection eventually, sometime reconnecting, sometimes not.

For a standard (matter) that purports to be universal, why would there be? Why would there need to be? There was not setup or configuration information regarding "works with Alexa" or "works with google", either. Are they going to prove the comic to be prescient?

Yes. Agreed. I even tried a few variations. I reset the nano leaf bulb and tried adding directly to UD Mobile (android). No luck. I reset the bulb, moved it closer to the nest hub (gen 2) and added back to google home. I then shared the bulb from the google home app (android tablet) to UD Mobile (also android). No luck. I have tried variations of this using iOS devices with similar lack of success.

Well...just tried adding a couple of matter devices. One is a Cync bulb and wifi. The other is a nonoleaf bulb and thread. Both were prior added to google home and shared with apple (but not yet amazon). I now shared both via a qr code from google home. Both appeared to add (certainly got no errors). The thread device is taking a relative long time and is adding as I type this. Edit: and I come back after 5 hours of "adding" the thread device and find that it has not added and is stuck on the screen saying "adding matter device". The matter wifi device added fine. I may try some different approaches soon.

OK. I will assume that the upgrade took hold and will try some matter devices soon.

I just tried "upgrade packages" on mine (Polisy, wired). Formerly 5.9.1. No change after upgrade. Still shows 5.9.1 I am inclined not to ssh for a variety of reasons, not the least of which is that I am more comfortable (less perceived risk) in using the official method and waiting for an official announcement.

I think Guy Lavoie gets the prize! The only thing that would cause the keypad button to come on (besides directly pressing it) is when the hutch scene is turned on. No other scenes will cause it to come on and no other devices will cause it to come on.