Posted May 4May 4 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 Edited May 4May 4 by GHenry
May 4May 4 Sometimes my individual node servers restart, one in particular and I get UDM notifications. Other times the portal disconnects. But it doesn't cause loss of node values that I'm aware of. Where I'm going is, could what you're seeing be isolated to individual node servers that are restarting and not the entire eisy?
May 4May 4 Author 1 hour ago, paulbates said: …could what you're seeing be isolated to individual node servers that are restarting and not the entire eisy? 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? Edited May 4May 4 by GHenry
May 4May 4 When the ISY program is restarted if you look in the error log there is a "start" line in there that indicates ISY has started.
May 4May 4 I've had the occasional restart of the ISY software, but it hasn't happened in a month. It restarts on its own. See the last entry on April 5. This log snippet if from /var/udx/logs/log. Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: no packages need upgrading ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: cleaning up old/unused files ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: deleting old log/debug files ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: generating sysconfig report ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: **** Finished Running UDX Daily Tasks **** Sat Apr 5 06:40:17 PDT 2025|/usr/local/etc/udx.d/static/udx_svc_supervisor: isy failed ... restarting now! Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: wifi.ops is not being called as a comamnd Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: **** Running UDX Daily Tasks **** Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: pkg.conf already has IGNORE_OSVERSION ... Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: checking for updated packages ...
May 5May 5 Author 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
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.