Announcement

Collapse
No announcement yet.

HS4 SEL does not autostart

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    HS4 SEL does not autostart

    So after upgrading to HS4 and dealing with a couple of interesting quirks, I now find that when i restart or cycle on/off my SEL it no longer automatically starts HomeSeer. I have to putty to ./go to start HS. So thought I would start this new topic.

    ConcordeSeer - output of
    systemctl list-units --type=service -

    homeseer@hometrollerSEL:~$ systemctl list-units --type=service
    UNIT LOAD ACTIVE SUB DESCRIPTION
    accounts-daemon.service loaded active running Accounts Service
    acpid.service loaded active running ACPI event daemon
    apparmor.service loaded active exited AppArmor initialization
    apport.service loaded active exited LSB: automatic crash repor
    avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
    binfmt-support.service loaded active exited Enable support for additio
    bluetooth.service loaded active running Bluetooth service
    console-setup.service loaded active exited Set console font and keyma
    cron.service loaded active running Regular background program
    cups.service loaded active running CUPS Scheduler
    dbus.service loaded active running D-Bus System Message Bus
    getty@tty1.service loaded active running Getty on tty1
    grub-common.service loaded active exited LSB: Record successful boo
    irqbalance.service loaded active running irqbalance daemon
    kerneloops.service loaded active running Tool to automatically coll
    keyboard-setup.service loaded active exited Set the console keyboard l
    kmod-static-nodes.service loaded active exited Create list of required st
    lightdm.service loaded active running Light Display Manager
    ● lighttpd.service loaded failed failed Lighttpd Daemon
    ModemManager.service loaded active running Modem Manager
    networkd-dispatcher.service loaded active running Dispatcher daemon for syst
    networking.service loaded active exited Raise network interfaces
    NetworkManager-wait-online.service loaded active exited Network Manager Wait
    NetworkManager.service loaded active running Network Manager
    polkit.service loaded active running Authorization Manager
    ● rc-local.service loaded failed failed /etc/rc.local Compatibilit
    resolvconf.service loaded active exited Nameserver information man
    rsyslog.service loaded active running System Logging Service
    rtkit-daemon.service loaded active running RealtimeKit Scheduling Pol
    setvtrgb.service loaded active exited Set console scheme
    snapd.apparmor.service loaded active exited Load AppArmor profiles man
    snapd.seeded.service loaded active exited Wait until snapd is fully
    ssh.service loaded active running OpenBSD Secure Shell serve
    systemd-journal-flush.service loaded active exited Flush Journal to Persisten
    systemd-journald.service loaded active running Journal Service
    systemd-logind.service loaded active running Login Service
    systemd-modules-load.service loaded active exited Load Kernel Modules
    systemd-random-seed.service loaded active exited Load/Save Random Seed
    systemd-remount-fs.service loaded active exited Remount Root and Kernel Fi
    systemd-resolved.service loaded active running Network Name Resolution
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-timesyncd.service loaded active running Network Time Synchronizati
    systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device
    systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device
    systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and
    systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
    systemd-udevd.service loaded active running udev Kernel Device Manager
    systemd-update-utmp.service loaded active exited Update UTMP about System B
    systemd-user-sessions.service loaded active exited Permit User Sessions
    thermald.service loaded active running Thermal Daemon Service
    udisks2.service loaded active running Disk Manager
    ufw.service loaded active exited Uncomplicated firewall
    unattended-upgrades.service loaded active running Unattended Upgrades Shutdo
    upower.service loaded active running Daemon for power managemen
    user@1000.service loaded active running User Manager for UID 1000
    user@107.service loaded active running User Manager for UID 107
    whoopsie.service loaded active running crash report submission da
    wpa_supplicant.service loaded active running WPA supplicant
    xrdp-sesman.service loaded active running xrdp session manager
    xrdp.service loaded active running xrdp daemon

    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.

    59 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    lines 45-67/67 (END)
    homeseer@hometrollerSEL:~$

    #2
    Are you trying to run HS4 from that new folder you created. You’ll need to copy the HS4 files back to the original folder /usr/local/HomeSeer for the service to run on boot

    Comment


      #3
      I am running it from /usr/local/HomeSeer I copied everything back from the old folder to the original folder

      Comment


        #4
        You can see from your first post that rc.local service that launches HS4 has failed.

        To get the status of your HomeSeer.service file you need to see if it is trying to run.

        You need to locate the service file so run

        sudo find / -name “*.service”

        Could you paste the output.

        Comment


          #5
          Got many pages of output, hate to paste them all! is there something we're looking for? HomeSeer.service?

          Comment


            #6
            I tried sudo find / -name HomeSeer.service with no luck. Got

            homeseer@hometrollerSEL:~$ sudo find / -name HomeSeer.service
            find: ‘/run/user/107/gvfs’: Permission denied
            find: ‘/run/user/1000/gvfs’: Permission denied

            Comment


              #7
              No run the command exactly as I gave it to you with the wildcard characters.

              Comment


                #8
                Here's what I got from

                homeseer@hometrollerSEL:~$ sudo find / -name “*.service”
                [sudo] password for homeseer:
                find: ‘/run/user/107/gvfs’: Permission denied
                find: ‘/run/user/1000/gvfs’: Permission denied

                When I ran it without the " " 's I got about 20 pages of .service files.

                Comment


                  #9
                  Just go to PM. It’s simpler that way

                  Comment


                    #10
                    Code:
                    ...
                    ● lighttpd.service loaded failed failed Lighttpd Daemon
                    ...
                    ● rc-local.service loaded failed failed /etc/rc.local Compatibilit
                    ...
                    The names of the failing service unit files are right there in the messages; no need to wildcard search thru 500+ others.

                    The rc-local service unit just runs the /etc/rc.local script. On the Hometroller's, HS3/HS4 is started from /etc/rc.local. Starting daemon processes this way is long deprecated, but that's how HST does it.

                    lighttpd is a web server. HST implements their "911" service with this.

                    Included in the 'final' HS3 update, 3.0.0.550, is a script RecoveryInstall.sh that makes some modifications to /etc/rc.local which involve startup of the lighttpd service. I'd suspect there are some issues with this.

                    If you're still working this issue .. what does /etc/rc.local contain?

                    Code:
                    more /etc/rc.local

                    Comment


                      #11
                      I asked the OP to go PM as I wanted to guide him through the more modern SystemD service method. That’s done and running now.

                      He’s still struggling with his HS4 install. He’s cleaned the HomeSeer folder, used the wget and tar instructions you provided earlier but has not confirmed that he can open the device page on the HS4 GUI successfully.

                      Comment


                        #12
                        Great progress!

                        I believe he indicated that the HS Insteon plugin was suspected. I have a test HS4 install here for my Raspberry Pi, maybe I'll add that and see if I can replicate.

                        I see that plugin is in the "Legacy" section in HS3 updater. Installer archive is dated 26 Nov 2014 -- that certainly qualifies it as legacy!!

                        Comment


                          #13
                          No luck, HSInsteon plugin installs and runs fine. No issue with the devices.html page.

                          The plugin needs to connect to a controller that I don't have, so likely not a good test ...

                          Comment


                            #14
                            Originally posted by zwolfpack View Post
                            Great progress!

                            I believe he indicated that the HS Insteon plugin was suspected. I have a test HS4 install here for my Raspberry Pi, maybe I'll add that and see if I can replicate.

                            I see that plugin is in the "Legacy" section in HS3 updater. Installer archive is dated 26 Nov 2014 -- that certainly qualifies it as legacy!!
                            I have no doubt that the Insteon plugin is at the root of the problem. It’s now been confirmed that HS4 installs and loads and a blank Device page opens fine.

                            Next step is to restore the HS3 Configuration backup and see if all is well. Just waiting on that step to be performed now.

                            Im not an Insteon user but as you say it’s gone legacy so it’s down to what testing has been carried out with it on HS4.

                            If we get to that step the OP can go back public for help with that matter.

                            Comment

                            Working...
                            X