GHenry

Thanks, Javi. I'm really hesitant to change anything from over 8,000 km away! Updates will have to wait until I get back in six weeks. 😟 Patience, they say, is a virtue…

With the Java interface, my time zone, system time, and log time were always the same, and correct.

I tried changing "1.3.4" to "1.4.2" and I see the Configuration tab with the other System Options and Legacy Options, but it did NOT display those time and map graphics. That's what I hoped to see…?

Well, that's the point! There is no Configuration tab under the System option; that was in the Java interface, but I cannot use that any more (it comes up blank). AFAICT, there is no analog to the Configuration tab, and thus there is no time in the eisy.ui interface.

MacOS 26.7.1, IoX 6.1.2_3, UDX 5.0.0, PG3x 3.4.23, eisy UI 1.3.4 I’m 7 time zones away from my eisy. eisyUI shows local time, but if there’s a way to show eisy system time, I can’t find it. How can I determine system time?

I'm not terribly technical, but my update went fine, took about 20 minutes to get the reboot dialog. Slick and quick!

D'oh! Synchronizing took care of the problem.

The device ("Den") might not show up in the Mac list of available devices, but it DOES show up in Mac Notifications!

MacOS 26.5.1, MacBook Pro with M3 Pro processor, UD Mobile 1.4.23 (iOS and MacOS) UD Mobile is clearly designed to run under MacOS 26 as well as iOS, because there are settings for the Mac (screenshot 1). I have a device, variously named Den, which shows up in the Java, UD Mobile/iPhone, and web interfaces, but does not show up under UD Mobile/MacOS. It’s definitely in Java (screenshot 2), and in iOS (screenshot 3), and in web (both there, only one shown, screenshot 4) All other devices are shown in UD Mobile MacOS. So why isn’t in MacOS UD Mobile (screenshot 5; believe me, I've scrolled and scrolled)? What am I missing?!

Maybe in the new browser-based interface…

Eisy v.5.9.1, Aeotec TriSensors 5 and 8, MacOS 15.5 At some point in the past, I recall being able to get a graph of current temperatures from my Aeotec TriSensors; if I recall correctly, it was on my ISY-99i via a control-click on the device name in the Main window of the Admin Console. Now when I try, I get no relevant contextual menu items, but I can click the Trend (Chart) icon in the AC menubar. With a TriSensor selected, the Trend icon produces a window with only a menubar; choosing Categories/Current Temperature opens a chooser. When I choose a TriSensor, nothing happens; the window is blank. Am I missing something, or has this feature been removed? (Note that it has never worked for me in UD Mobile.)

I should have posted this 48-line error log snippet. It clearly shows a restart 55 minutes after the previous entry, but doesn't show a reason. There must be one…? It also shows the switch between AM/PM and 24-hour time. ISY Error Log.v5.9.1__Mon 2025.05.05 02.19.58.txt

Maybe. But PG3 is usually restarting. The eisy's MAC address/notification server restarts. My question is: does that indicate that the eisy itself is restarting?

eisy 5.9.1, PG3x 3.3.18, UD Mobile 1.2.5, MacOS 15.4.1 Occasionally I get UD Mobile messages like “PG3 starting” and at the same time, scheduled battery and device reports that are blank (they later update to numbers). I assume that this means the eisy has rebooted (I was out of town at the time). However, I have an alarm system, a door lock, and a thermostat which are very quick to alert on a power blink or outage of even short duration, and they report no outage. The eisy log does not indicate any power failure or reboot at the time of the messages. In this example, I got 11 notifications in UD Mobile at 16.01 on 3 May; the log starts with 2 odd entries in AM/PM time (most entries are in 24-hour time): 0 null Sat 2025/05/03 03:59:53 PM System Unknown 0 null Sat 2025/05/03 03:59:53 PM System Unknown Then another 160 log entries within 40 seconds (I've attached a log snippet). Does this make sense to anyone? Is the eisy rebooting? If not, what's causing all these notifications (note phone time is +7h relative to eisy time)? Log Snippet 1552-1602.txt

Thanks! That's the bug, apparently limited to display; nonetheless, the programs run as expected, and the displayed times of sunrise and sunset appear to self-correct during the night after the time change.