GHenry

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.

…but two of my sunset rules just fired (correctly) at 18:50, even though the Java interface says sunset won't be until 19:50…?!

eisy v5.9.1 My eisy experienced an 8-hour power failure on Friday. When power returned, the time was off by 8 hours. I reset the location, and the time corrected itself, but today was the Spring time change to Daylight Saving time, and the times of sunrise and sunset are still one hour off. I thought I recalled an NTP service setting when I initially set up the predecessor ISY-994i, but now I can’t find it. How can I correct sunrise/sunset times (some rules use it)?

You'll eventually have to reboot. Would a fixed LAN address assignment in the router solve the problem?

I think you're expecting too much, too soon. The release notes say "installs HomeKit plumbing," not HomeKit itself, similar to the way it says "installs eisyui plumbing," not eisyui (presumably the forthcoming browser-based UI).

Believe me, they want it worse than you do. And they're working hard on it. So let's give them some slack.

Thanks, I would never have found that! 🤭

UD Mobile v1.1.88, iOS 18.3.1 I have added a state variable to Favorites. It is currently set to 1, according to Admin Console, but shows as blank (neither 0 nor 1) in Favorites. When I tap the Favorite to view the Device Dashboard, it also shows as 1, and when I return to Favorites it then shows as 1. But it disappears every time I switch to another app and switch back to UD Mobile . Tapping it displays Device Dashboard, where its value still shows as 1, and when I return to Favorites, then the 1 appears again. Note that it does not disappear when I change views in UDM and return to Favorites, nor has it happened yet in UDM on the Mac. This behavior is replicable. Is this a bug?

ifconfig en0 (or en1) should do the trick. If not, just try ifconfig and scan through everything until you find the IPv6 addresses.

I also write the date any bulb (not just WiFi) entered service (also for batteries!).

IP Scanner Ultra shows only a private IPv6 address for my eisy, but LanScan shows both public and private IPv6 addresses. Port scan through 12000 shows 22, 53, 1884, 3000, 8080, 8199, 8443, 8881, 8882, and 8883.

Beta software is for testing. It's not for production, and it typically requires a non-disclosure agreement (I don't know about UDI), so I'm not going to try it until it's released—even then there will be a few bugs (there's always one more bug…).