Announcement

Collapse
No announcement yet.

Autostart Homeseer on Linux

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

    #16
    The unit file looks OK. The extra sudo shouldn't make a difference - it does work on a running system, and it didn't work starting up either with or without the sudo.

    I notice one thing about the homeseer dependencies that I have different - my setup has "basic.target" listed in addition to "sysinit.target". I'm running OpenSuSE so this may be specific to me, but you can check to see what targets you have available with:
    Code:
    # systemctl list-units *.target
    Nothing jumps out at me about the details of homeseer.service, but I should have had you use the following command to make it easier to post here:
    Code:
    systemctl --no-pager show homeseer.service
    -A

    Comment


      #17
      Thanks again
      # systemctl list-units *.target:

      Code:
      systemctl list-units *.target
      UNIT                   LOAD   ACTIVE SUB    DESCRIPTION
      basic.target           loaded active active Basic System
      cryptsetup.target      loaded active active Encrypted Volumes
      getty.target           loaded active active Login Prompts
      graphical.target       loaded active active Graphical Interface
      local-fs-pre.target    loaded active active Local File Systems (Pre)
      local-fs.target        loaded active active Local File Systems
      multi-user.target      loaded active active Multi-User System
      network-online.target  loaded active active Network is Online
      network-pre.target     loaded active active Network (Pre)
      network.target         loaded active active Network
      nss-user-lookup.target loaded active active User and Group Name Lookups
      paths.target           loaded active active Paths
      remote-fs-pre.target   loaded active active Remote File Systems (Pre)
      remote-fs.target       loaded active active Remote File Systems
      slices.target          loaded active active Slices
      sockets.target         loaded active active Sockets
      swap.target            loaded active active Swap
      sysinit.target         loaded active active System Initialization
      time-sync.target       loaded active active System Time Synchronized
      timers.target          loaded active active Timers
      
      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.
      
      20 loaded units listed. Pass --all to see loaded but inactive units, too.
      To show all installed unit files use 'systemctl list-unit-files'.

      systemctl --no-pager show homeseer.service:
      Code:
      christian@homeseer:~$ systemctl list-units *.target
      UNIT                   LOAD   ACTIVE SUB    DESCRIPTION
      basic.target           loaded active active Basic System
      cryptsetup.target      loaded active active Encrypted Volumes
      getty.target           loaded active active Login Prompts
      graphical.target       loaded active active Graphical Interface
      local-fs-pre.target    loaded active active Local File Systems (Pre)
      local-fs.target        loaded active active Local File Systems
      multi-user.target      loaded active active Multi-User System
      network-online.target  loaded active active Network is Online
      network-pre.target     loaded active active Network (Pre)
      network.target         loaded active active Network
      nss-user-lookup.target loaded active active User and Group Name Lookups
      paths.target           loaded active active Paths
      remote-fs-pre.target   loaded active active Remote File Systems (Pre)
      remote-fs.target       loaded active active Remote File Systems
      slices.target          loaded active active Slices
      sockets.target         loaded active active Sockets
      swap.target            loaded active active Swap
      sysinit.target         loaded active active System Initialization
      time-sync.target       loaded active active System Time Synchronized
      timers.target          loaded active active Timers
      
      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.
      
      20 loaded units listed. Pass --all to see loaded but inactive units, too.
      To show all installed unit files use 'systemctl list-unit-files'.
      christian@homeseer:~$ systemctl --no-pager show homeseer.service
      Type=simple
      Restart=on-failure
      NotifyAccess=none
      RestartUSec=100ms
      TimeoutStartUSec=1min 30s
      TimeoutStopUSec=1min 30s
      RuntimeMaxUSec=infinity
      WatchdogUSec=0
      WatchdogTimestamp=Tue 2017-09-19 19:59:19 CEST
      WatchdogTimestampMonotonic=110932237
      FailureAction=none
      PermissionsStartOnly=no
      RootDirectoryStartOnly=no
      RemainAfterExit=no
      GuessMainPID=yes
      MainPID=2078
      ControlPID=0
      FileDescriptorStoreMax=0
      NFileDescriptorStore=0
      StatusErrno=0
      Result=success
      UID=4294967295
      GID=4294967295
      ExecMainStartTimestamp=Tue 2017-09-19 19:59:19 CEST
      ExecMainStartTimestampMonotonic=110932203
      ExecMainExitTimestampMonotonic=0
      ExecMainPID=2078
      ExecMainCode=0
      ExecMainStatus=0
      ExecStart={ path=/usr/bin/sudo ; argv[]=/usr/bin/sudo mono /home/christian/HomeSeer/HSConsole.exe --log ; ignore_errors=no ; start_time=[Tue 2017-09-19 19:59:19 CEST] ; stop_time=[n/a] ; pid=2078 ; code=(null) ; status=0/0 }
      Slice=system.slice
      ControlGroup=/system.slice/homeseer.service
      MemoryCurrent=747925504
      CPUUsageNSec=420759819877
      TasksCurrent=230
      Delegate=no
      CPUAccounting=no
      CPUWeight=18446744073709551615
      StartupCPUWeight=18446744073709551615
      CPUShares=18446744073709551615
      StartupCPUShares=18446744073709551615
      CPUQuotaPerSecUSec=infinity
      IOAccounting=no
      IOWeight=18446744073709551615
      StartupIOWeight=18446744073709551615
      BlockIOAccounting=no
      BlockIOWeight=18446744073709551615
      StartupBlockIOWeight=18446744073709551615
      MemoryAccounting=no
      MemoryLow=0
      MemoryHigh=18446744073709551615
      MemoryMax=18446744073709551615
      MemorySwapMax=18446744073709551615
      MemoryLimit=18446744073709551615
      DevicePolicy=auto
      TasksAccounting=yes
      TasksMax=4915
      UMask=0022
      LimitCPU=18446744073709551615
      LimitCPUSoft=18446744073709551615
      LimitFSIZE=18446744073709551615
      LimitFSIZESoft=18446744073709551615
      LimitDATA=18446744073709551615
      LimitDATASoft=18446744073709551615
      LimitSTACK=18446744073709551615
      LimitSTACKSoft=8388608
      LimitCORE=18446744073709551615
      LimitCORESoft=0
      LimitRSS=18446744073709551615
      LimitRSSSoft=18446744073709551615
      LimitNOFILE=4096
      LimitNOFILESoft=1024
      LimitAS=18446744073709551615
      LimitASSoft=18446744073709551615
      LimitNPROC=7815
      LimitNPROCSoft=7815
      LimitMEMLOCK=65536
      LimitMEMLOCKSoft=65536
      LimitLOCKS=18446744073709551615
      LimitLOCKSSoft=18446744073709551615
      LimitSIGPENDING=7815
      LimitSIGPENDINGSoft=7815
      LimitMSGQUEUE=819200
      LimitMSGQUEUESoft=819200
      LimitNICE=0
      LimitNICESoft=0
      LimitRTPRIO=0
      LimitRTPRIOSoft=0
      LimitRTTIME=18446744073709551615
      LimitRTTIMESoft=18446744073709551615
      WorkingDirectory=/home/christian/HomeSeer
      OOMScoreAdjust=0
      Nice=0
      IOScheduling=0
      CPUSchedulingPolicy=0
      CPUSchedulingPriority=0
      TimerSlackNSec=50000
      CPUSchedulingResetOnFork=no
      NonBlocking=no
      StandardInput=null
      StandardOutput=journal
      StandardError=inherit
      TTYReset=no
      TTYVHangup=no
      TTYVTDisallocate=no
      SyslogPriority=30
      SyslogLevelPrefix=yes
      SyslogLevel=6
      SyslogFacility=3
      SecureBits=0
      CapabilityBoundingSet=18446744073709551615
      AmbientCapabilities=0
      DynamicUser=no
      RemoveIPC=no
      MountFlags=0
      PrivateTmp=no
      PrivateDevices=no
      ProtectKernelTunables=no
      ProtectKernelModules=no
      ProtectControlGroups=no
      PrivateNetwork=no
      PrivateUsers=no
      ProtectHome=no
      ProtectSystem=no
      SameProcessGroup=no
      UtmpMode=init
      IgnoreSIGPIPE=yes
      NoNewPrivileges=no
      SystemCallErrorNumber=0
      RuntimeDirectoryMode=0755
      MemoryDenyWriteExecute=no
      RestrictRealtime=no
      RestrictNamespace=2114060288
      KillMode=control-group
      KillSignal=15
      SendSIGKILL=yes
      SendSIGHUP=no
      Id=homeseer.service
      Names=homeseer.service
      Requires=sysinit.target system.slice -.mount
      Conflicts=shutdown.target
      Before=shutdown.target
      After=home-christian.mount -.mount sysinit.target basic.target network.target system.slice systemd-journald.socket
      RequiresMountsFor=/home/christian/HomeSeer
      Description=HomeSeer
      LoadState=loaded
      ActiveState=active
      SubState=running
      FragmentPath=/etc/systemd/system/homeseer.service
      UnitFileState=disabled
      UnitFilePreset=enabled
      StateChangeTimestamp=Tue 2017-09-19 19:59:19 CEST
      StateChangeTimestampMonotonic=110932237
      InactiveExitTimestamp=Tue 2017-09-19 19:59:19 CEST
      InactiveExitTimestampMonotonic=110932237
      ActiveEnterTimestamp=Tue 2017-09-19 19:59:19 CEST
      ActiveEnterTimestampMonotonic=110932237
      ActiveExitTimestampMonotonic=0
      InactiveEnterTimestampMonotonic=0
      CanStart=yes
      CanStop=yes
      CanReload=no
      CanIsolate=no
      StopWhenUnneeded=no
      RefuseManualStart=no
      RefuseManualStop=no
      AllowIsolate=no
      DefaultDependencies=yes
      OnFailureJobMode=replace
      IgnoreOnIsolate=no
      NeedDaemonReload=no
      JobTimeoutUSec=infinity
      JobTimeoutAction=none
      ConditionResult=yes
      AssertResult=yes
      ConditionTimestamp=Tue 2017-09-19 19:59:19 CEST
      ConditionTimestampMonotonic=110931617
      AssertTimestamp=Tue 2017-09-19 19:59:19 CEST
      AssertTimestampMonotonic=110931617
      Transient=no
      Perpetual=no
      StartLimitIntervalSec=10000000
      StartLimitBurst=5
      StartLimitAction=none
      InvocationID=4171dacedceb4c0e821911fb299887e6

      Comment


        #18
        Well, that all looks good, based on what I see it should 'just work'.

        There is a basic.target, but it seems to be pulled in automatically in the "After=" line. We could try adding it as a hard dependency int the unit file with a line:
        Code:
        After=basic.target network.target
        Requires=basic.target network.target
        in the [Unit] section - then enabling the service and testing.

        I forget to ask, what version of systemd do you have?

        -A

        Comment


          #19
          It failed with the same error message after adding the hard dependency too.

          I set up a new virtual machine with Ubuntu 17.04 and installed HomeSeer from the tutorial I used last time located here: https://forums.homeseer.com/showthread.php?t=162813

          And now it worked, but I can't figure out what changes I have made to the other virtual machine that hinders it to autostart. But I think we have troubleshooted enough. Thank you very much! But I think the short route here is a complete reinstall of HS3 on a new virtual machine. Painful yes, but probably faster..

          Code:
          christian@homeseertest:~$ systemctl status homeseer.service
          ● homeseer.service - HomeSeer
             Loaded: loaded (/etc/systemd/system/homeseer.service; enabled; vendor preset:
             Active: active (running) since Tue 2017-09-19 23:43:05 CEST; 2min 5s ago
           Main PID: 1174 ((System)_20-Sep)
             CGroup: /system.slice/homeseer.service
                     └─1174 /usr/bin/mono /home/christian/HomeSeer/HSConsole.exe --log
          
          Sep 20 07:42:29 homeseertest mono[1174]: Copyright (C) 2004-2010 Rolf Bjarne Kvi
          Sep 20 07:42:29 homeseertest mono[1174]: vbnc : Command line : error VBNC2017: T
          Sep 20 07:42:29 homeseertest mono[1174]: There were 1 errors and 0 warnings.
          Sep 20 07:42:29 homeseertest mono[1174]: Compilation took 00:00:00.2068280
          Sep 20 07:42:29 homeseertest mono[1174]: 07:42:29:2303:[Startup]->Starting Event
          Sep 20 07:42:29 homeseertest mono[1174]: 07:42:29:2310:[Startup]->HSSentry is di
          Sep 20 07:42:29 homeseertest mono[1174]: 07:42:29:2320:[Startup]->Start up compl
          Sep 20 07:42:29 homeseertest mono[1174]: Type 'shutdown' to shutdown HomeSeer
          Sep 20 07:42:29 homeseertest mono[1174]: > 07:42:29:5229:[Info]->System connecte
          Sep 20 07:42:30 homeseertest mono[1174]: 07:42:30:2573:[Info]->System connected
          lines 1-17/17 (END)...skipping...
          ● homeseer.service - HomeSeer
             Loaded: loaded (/etc/systemd/system/homeseer.service; enabled; vendor preset: enab
             Active: active (running) since Tue 2017-09-19 23:43:05 CEST; 2min 5s ago
           Main PID: 1174 ((System)_20-Sep)
             CGroup: /system.slice/homeseer.service
                     └─1174 /usr/bin/mono /home/christian/HomeSeer/HSConsole.exe --log
          
          Sep 20 07:42:29 homeseertest mono[1174]: Copyright (C) 2004-2010 Rolf Bjarne Kvinge.
          Sep 20 07:42:29 homeseertest mono[1174]: vbnc : Command line : error VBNC2017: The li
          Sep 20 07:42:29 homeseertest mono[1174]: There were 1 errors and 0 warnings.
          Sep 20 07:42:29 homeseertest mono[1174]: Compilation took 00:00:00.2068280
          Sep 20 07:42:29 homeseertest mono[1174]: 07:42:29:2303:[Startup]->Starting Event Sche
          Sep 20 07:42:29 homeseertest mono[1174]: 07:42:29:2310:[Startup]->HSSentry is disable
          Sep 20 07:42:29 homeseertest mono[1174]: 07:42:29:2320:[Startup]->Start up complete.
          Sep 20 07:42:29 homeseertest mono[1174]: Type 'shutdown' to shutdown HomeSeer
          Sep 20 07:42:29 homeseertest mono[1174]: > 07:42:29:5229:[Info]->System connected to
          Sep 20 07:42:30 homeseertest mono[1174]: 07:42:30:2573:[Info]->System connected to My

          Comment


            #20
            Well, I'm glad to hear you've got it working. But that was a strange behavior - I guess we'll chock it up to 'Computer Science - where you do the same thing each time and get different results'.

            Have fun,
            -A

            Comment


              #21
              Hehe, yupp, I think that is the best approach Thanks for all the help!

              Comment


                #22
                auto start with systemd

                Pete,

                I'm back home trying to get things set up. Been reading and trying to learn more about Linux. It seems it is something one must live to understand it.

                The following changes were made to the file

                NAME='HomeSeer' # Server handle for the screen session
                DIR='usr/local/HomeSeer'
                USER='hseer'

                hseer is a administrator on the system

                I followed these instructions because I am running Ubunto 16.04

                For a systemd service do the following:

                1 - nano /etc/systemd/system/homeseer.service
                2 - chmod u+x /etc/systemd/system/homeseer.service
                2 - systemctl enable homeseer.service or systemctl disable homeseer.service

                The last command returns an error message
                Failed to execute operation: Invalid argument.

                Googleing the error message leads to many links beyond my comprehension. Some saying the homeseer.service if put in the /etc/systemd folder does not require the enable as it will start automatically on reboot. Or the file has to be in /usr/lib/systemd.

                Any clues as to what I am doing wrong?

                Jim

                Comment


                  #23
                  Some saying the homeseer.service is put in the /etc/systemd folder does not require the enable as it will start automatically on reboot.

                  Here is a copy and paste:

                  Where are Systemd Unit Files Found?

                  The files that define how systemd will handle a unit can be found in many different locations, each of which have different priorities and implications.

                  The system's copy of unit files are generally kept in the /lib/systemd/system directory. When software installs unit files on the system, this is the location where they are placed by default.

                  Unit files stored here are able to be started and stopped on-demand during a session. This will be the generic, vanilla unit file, often written by the upstream project's maintainers that should work on any system that deploys systemd in its standard implementation. You should not edit files in this directory. Instead you should override the file, if necessary, using another unit file location which will supersede the file in this location.

                  If you wish to modify the way that a unit functions, the best location to do so is within the /etc/systemd/system directory. Unit files found in this directory location take precedence over any of the other locations on the filesystem. If you need to modify the system's copy of a unit file, putting a replacement in this directory is the safest and most flexible way to do this.

                  If you wish to override only specific directives from the system's unit file, you can actually provide unit file snippets within a subdirectory. These will append or modify the directives of the system's copy, allowing you to specify only the options you want to change.

                  The correct way to do this is to create a directory named after the unit file with .d appended on the end. So for a unit called example.service, a subdirectory called example.service.d could be created. Within this directory a file ending with .conf can be used to override or extend the attributes of the system's unit file.

                  There is also a location for run-time unit definitions at /run/systemd/system. Unit files found in this directory have a priority landing between those in /etc/systemd/system and /lib/systemd/system. Files in this location are given less weight than the former location, but more weight than the latter.

                  The systemd process itself uses this location for dynamically created unit files created at runtime. This directory can be used to change the system's unit behavior for the duration of the session. All changes made in this directory will be lost when the server is rebooted.

                  Here utilize Webmin on my headless Linux boxes. You can manage the base configuration and update it via the web gui.

                  You can see and edit all starting files (and test run them) via Webmin.

                  Here utilize Ubuntu 16.04 desktop on my home office computer and laptops these days and run Windows in Oracle VB's.
                  In Ubuntu utilize file manager (remotely), ssh and Webmin to manage headless computers.

                  Installing on Debian

                  1 - ssh to your new computer then
                  2 - apt-get install perl libnet-ssleay-perl openssl libauthen-pam-perl libpam-runtime libio-pty-perl apt-show-versions python
                  3 - wget hxxp://prdownloads.sourceforge.net/webadmin/webmin_1.870_all.deb *
                  3 - dpkg --install webmin_1.870_all.deb

                  *NOTE: xx=tt

                  Here is the systemd page of webmin.

                  [ATTACH]66559[/ATTACH]
                  Last edited by Pete; February 10, 2018, 03:54 AM.
                  - Pete

                  Auto mator
                  Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                  Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                  HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                  HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                  HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                  X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                  Comment


                    #24
                    Originally posted by ocxoman View Post
                    Pete,

                    I'm back home trying to get things set up. Been reading and trying to learn more about Linux. It seems it is something one must live to understand it.

                    The following changes were made to the file

                    NAME='HomeSeer' # Server handle for the screen session
                    DIR='usr/local/HomeSeer'
                    USER='hseer'

                    hseer is a administrator on the system

                    I followed these instructions because I am running Ubunto 16.04

                    For a systemd service do the following:

                    1 - nano /etc/systemd/system/homeseer.service
                    2 - chmod u+x /etc/systemd/system/homeseer.service
                    2 - systemctl enable homeseer.service or systemctl disable homeseer.service

                    The last command returns an error message
                    Failed to execute operation: Invalid argument.

                    Googleing the error message leads to many links beyond my comprehension. Some saying the homeseer.service if put in the /etc/systemd folder does not require the enable as it will start automatically on reboot. Or the file has to be in /usr/lib/systemd.

                    Any clues as to what I am doing wrong?

                    Jim
                    It's not clear what file you are editing. The snippet you posted appears to be from a SysVinit style script, possibly the one from post #2 of this thread. This is a different animal entirely from a systemd script. (SysVinit scripts live in /etc/init.d/).

                    In any case, this line has an error:
                    DIR='usr/local/HomeSeer'
                    The directory name needs a leading "/",
                    DIR='/usr/local/HomeSeer'

                    So post specifically what file(s) you are trying to use and their entire contents.

                    Comment


                      #25
                      Auto start with systemd

                      Thanks Pete and Wolfpack,

                      I will go over what you both said so I can learn more about how Linux works. It's so overwhelming to learn what all the options there are for so many commands and the overall structure of Linux. It seems books from the library get me only a fraction of what you guys live and breathe.

                      I did get crontab to work by following Pete's advise from #5 above after making the autostart_sh executable. It's scary and dangerous that I figured that out without asking for help as it is missing in the post. I did not install the server version of Ubunto just to make it easier for me to learn some of the file structure using a graphic interface. I've been using terminal in lieu of sshing into the unit. I can see the advantage of using the server version and Webmin, but it's not for me just yet. In a couple of years maybe.

                      I will in the future include the complete file and thanks to both of you for the explanation and catching the syntax error. I will remove my crontab and attempt to make the systemd method work as a learning experience. Until it's working, I'll be going back to crontab after every failed attempt at using the systemd method. I may be back for more help.

                      btw, Pete, I'm tired of shoveling and blowing snow. About 8 inches yesterday and another 2 this morning. Been back home 5 days and battled snow 4 of those. Hard to learn Linux while I'm in the driveway.

                      Jim

                      Comment


                        #26
                        Ubuntu no longer sees smartstick or audio

                        My unit suffered from an abnormal shutdown because I was moving things around like a numbskull. I now get error messages on ubuntu boot that were not there before.

                        EDAC pnd2: Failed to register device with error -19

                        I get two of these errors. Do I need to reinstall everything?

                        of course HS3 cannot communicate with the smartstick so my system is sort of useless at the present.

                        Comment


                          #27
                          I put an install of HS3 on Odroid C1 SBC in the How-To forum and includes the auto start steps. It may cover what you have already done, but does provide another proven step-by-step for reference. It should not matter what Linux flavor is used as long as systemctl is supported.

                          Comment


                            #28
                            @Jim,

                            Don't get frustrated. Just go baby steps. Disable the autostart in cron tab for time being.

                            After a good reboot then SSH to your new Homeseer box. Go to the HS3 directory...and manually start homeseer by typing ./go and then go to your GUI and check you ZWave functions. This part should be fine.

                            Yeah here too we have had a bit of snow.......not as bad over night as what occurred on Friday.

                            After 60 plus years here used to it....a few years back working in London 1/2" of snow took the city to a standstill.

                            Personally in London lived near one train station and work was next to another train station and I walked to work anyhow.....which ended up faster than driving or taking the train to work at the time....
                            Last edited by Pete; February 11, 2018, 06:12 PM.
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                            HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                            HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                            HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                            Comment


                              #29
                              Working again

                              Pete,
                              Thanks for the kind words. I found out that the Synology Virtual Machine Manager turned off the mounting of the USB dongles. I enabled them but still nothing. I then changed the Virtual USB controller to USB 2.0 and restarted Ubuntu. Still no luck. Next I made 2 changes, put the Smartstick on a different port and went back to USB 3.0 on the virtual USB controller. This time it took nearly 3 minutes to iniitialize the interface but it finally worked and my network is complete and working.
                              I have some errors showing up (not new ones) on the interface to my EcoBee thermostats. The install info says to move MonoCSharp.dll and CSScriptLibrary.dll to the bin folder from the root HomeSeer folder. I did this but it didn't fix the errors. "The call failed for an unknown reason" occurs 3 times every 4 minutes when the plugin communicates with the thermostats. I'll work with Spud to iron out the issue.
                              It is fun learning something new but except when my wife asks why the lights didn't turn on like they are supposed to.

                              Spent a couple weeks in London last Spring. My daughter lived in Paris for 3 years so I spent a couple months each year in Paris and got to explore some of Europe.

                              Have the SEL on Ebay and going to save my Zee to run this house if we decide to move to the LA. What's a fair price to ask for the SEL and smartstick?

                              Comment


                                #30
                                Autostart HS3

                                Michael,
                                Thanks for pointing to the place for the step by step. I need all the help I can get trying to learn something totally new. I'll check it out and try to understand what each step does. Right now crontab is working with help from Pete. I mean to try the systemd method again after taxes are done and I have some more time.

                                Jim

                                Comment

                                Working...
                                X