homeseer doesn't restart after update.

[CraziFuzzy]

So, I know this isn't necessarily the biggest issue, but I recently updated the homeseer software on my hometroller pi, and the update page explicitly says that it will need to reboot, but that if I have a hometroller, homeseer will restart. This did not happen. After the update, homeseer was not up and running. I putty'd into the pi, and was able to reboot it from the command prompt, upon which homeseer did start as usual. Is there something i can look for to find the possible cause? I believe the only thing I've done to the hometroller so far is install nodered on it. Could this perhaps somehow break restarting homeseer?

[CraziFuzzy]

So. Had a small power outage today, and the same thing happened. The pi was up and running, but honest was not running on it. After a reboot, it started normally.

[pseudocode]

Note: I'm a regular Raspbian user rather than Hometroller so I don't know if there are significant differences to how it is set up.

Does your log say anything about Homeseer starting or having problems? (less /var/log/syslog)

You can check your service definition which is probably in /lib/systemd/system/homeseer.service (or run systemctl status homeseer to find the path to the service file), that may give you some other dependencies to check that may also behave differently at power-on vs reboot.

[kenm]

AKAIK, the Hometroller Pi is still using the old initd scripts, not systemd. I suspect the problem isn't startup, it's something keeping it from shutting down for reboot. How are you starting and stopping nodered?

[RFB]

So. Had a small power outage today, and the same thing happened. The pi was up and running, but honest was not running on it. After a reboot, it started normally.

Somewhat a newby, I have something similar to this after a small power outage and restart. The pi comes up and appears ready (Green LED) but will not respond to remote inputs. I am not a Linux guy but suspect some sort of timing problem for the browser setup (headless HS4). I have a satellite internet connection and suspect that the HS4 restart occurs well before the HughesNet modem is back online. Cycling the power on the HS4 fixes everything, but also loses the log so I cannot see the sequence of events that caused the problem. I am wondering if I put a boot_delay in start.elf that is sufficient time for the HughesNet modem to come up if the restart issue would go away. Otherwise, is there a way to delay the server port from starting within HS4 for some selected time?
p.s. Forgot to mention, IP is fixed and not from modem AND local net access also does not work.

[QuikDraw]

...Cycling the power on the HS4 fixes everything, but also loses the log so I cannot see the sequence of events that caused the problem....

If you're on HS4, the logs should be persistent. But upon reboot, the time/date filter gets set to the boot time.
you can click on Start Date in the upper left corner, and set the date. Dates with no logs will be grayed out.

If you choose an earlier date, the time will usually be default to midnight, but you can click Start Time and set that to the hour/minute of your choosing.

[RFB]

Thanks QuickDraw. Changed the filters and got the persistent log. Turns out the Hub IP is still from the DHCP service on the gateway router. I had it static within the modem's table with no expiration, but the pi comes up long before the router is back on-line and assigns itself a local IP (127.0.0.1). I need to configure the pi with a static ip for its eth0 interface, but I cannot figure out how with a headless pi using the HS4 system Linux tools command line. Actually, I have several solutions, but have no idea how to edit a Linux configuration file (/etc/dhcpcd.conf) with this setup. That would work or the delay mentioned above in start.elf would also work. But I have no idea how to use nano or some other editor using the command line tool.

From Log area for restart that fails:

5/13/2023 5:17:29 PM HomeSeer Web Server Web Server started on port 80

5/13/2023 5:17:29 PM HomeSeer Web Server UPNP Discovery started

5/13/2023 5:17:29 PM HomeSeer Web Server Local IP address is: 127.0.0.1

5/13/2023 5:17:29 PM HomeSeer Startup This version of HomeSeer is registered as a HS4ZEES2_PIHUB version.

5/13/2023 5:17:29 PM HomeSeer Startup Creating Speaker Client Interface Object...

5/13/2023 5:17:29 PM HomeSeer Startup HomeSeer version is: 4.2.18.3

5/13/2023 5:17:28 PM HomeSeer Loaded 0 Timers.

5/13/2023 5:17:28 PM HomeSeer Loaded 0 Counters.

5/13/2023 5:17:28 PM HomeSeer Info Loaded 14 Events.

5/13/2023 5:17:27 PM HomeSeer Info Loaded 60 Devices.

5/13/2023 5:17:25 PM HomeSeer Info Loading configuration: /usr/local/HomeSeer/Data/HomeSeerData.json

5/13/2023 5:17:25 PM HomeSeer Startup Local voice recognition class started.

5/13/2023 5:17:25 PM HomeSeer Startup Startup Plug-In Interface class started.

. . .

HomeSeer
startup
************************************************************ ********************

RFB

[zwolfpack]

You should be able to edit a file using SSH from Windows.

https://learn.microsoft.com/en-us/wi.../tutorials/ssh

From the Windows command prompt, run command: ssh homeseer@192.168.1.123

Substitute in your hub's IP address of course.

On the first run it'll issue a security challenge. Answer yes, then enter the homeseer user's password when prompted.

Once logged in, you should be able to run nano. Use "sudo nano" when editing system files.

If that doesn't work out for some reason, consider installing the PuTTY client from https://www.chiark.greenend.org.uk/~...ty/latest.html