oberkc

I have started to play around with some of these parameters. Based on memory, if you define color temperature, you will generally get a “white”, with warmer ir cooler tones. I have also had some luck asking mr google what xy numbers one can use for a given color. My experience so far is that the admin panel may not reflect the actual status. I plan to contine to continue to explore this capability. Perhaps we can share notes with each other.

It is blue. Thanks for the clarification. I vaguely recall some short messages but they did not persist long enough for me to read them. Perhaps I just missed it. Thanks for all the work figuring it out and posting the instructions.

This worked for me. The only thing in the instructions that were a little ambiguous in my head were the notes about the notification. I assume you were talking about a notification from UD mobile.

Maybe it has been said, but my biggest fear of not updating would be the loss of access to the admin panel die to the loss of java. In my limited experience, this can happen quite suddenly and unexpectedly. If not actively moving towards the latest EISY-UI, i think you are risking making it much harder to upgrade in the future.

It is near certainty that it is a Mac issue. I lost mine a month or so ago. As far as I know, one must now use the eisy-ui.

FWIW, I am on Safari and I do not notice any flashing blue line or a clearing of any search results. I just now upgraded to 1.3.11_1 beta (not yet rebooted), however.

The recent past has brought me a lot of issues. I don't know if it was coincidental with my loss of the Java Admin console or something else. This program is one. A few of my PG3 (twinkly, govee, maybe others) have lost connection to some (but not all) devices. Less reliable and consistent device response. It is hard for me to imagine this being related to software updates, but it sure has been frustrating and time-consuming. On the other hand, the EISY_UI is really maturing and the login process is much less troublesome and much faster. I remain hopeful that the problems will work themselves out.

Whatever it was turns out to be fixed in the beta version released last night.

I am on the latest Beta version. At this point, I do not know how to check the time or sunset time or location from the EISY-UI, but I must assume EISY-US-predicted sunset was 7:36 and logs show that it ran at that time. I do not know why else it would have ran at that time. One of my questions is why, regardless of sunset, did it NOT run at 8pm?

I have not yet found a means to copy a program text on EISY-UI, so I have a screenshot. I have a program that has been in place for several years and has worked as expected. I wanted a program to close blinds at 8pm or sunset, whichever is later and this program has done so. It has even worked as recently as a few weeks ago. No changes have been made since first creating it. The program is below. I expect this program to trigger at sunset, 8pm, and 11:59pm. Tonight (it is now 9:41)The program shows last run at 7:36pm (presumably the calculated sunset time) and ran false (expected). I expected this program also to trigger at 8pm and evaluate true. Yet, it apparently did not. Blinds are still open. Last run at 7:36 was false. Did something change in the program logic execution recently? Am I missing something?

As am I.

On the java console, there was a means by which one could define the command for each device within a scene. For example, "default", "on", "set brightness". I don't see this capability in the new UI, nor do I see it in the upcoming builds. Am I missing it somewhere? Edit...nevermind. I found it.

That does not sound right to me. Is it, possibly, needed if one wants to use matter-over-thread?

Yes. Minor issues, but otherwise is a LOT of new capability compared to the production version. Beta still lacks a couple of key features that make it difficult for my purposes (cannot add nodes to groups or folders, cannot see node scene membership, missing network resources) but I can fill in some of the missing features with UDMobile.

My sunset-based programs appear to be working now, presumably a result of updating to UI 1.3.6