Announcement

Collapse
No announcement yet.

HS3 Pi Installation

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

    #16
    AFA the sudousers file, I still get homeseer is not the sudoers file. This incident will be reported.

    It also fails when in SSH session.

    Comment


      #17
      To make homeseer a sudo user just type:

      sudo usermod -aG sudo homeseer

      Typically here create a homeseer and personal username user and make them both sudo users.

      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
      HS4 Pro - V4.1.10.0 - Ubuntu 18.04/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono 6.12.x
      HS4 Lite -

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

      Comment


        #18
        Originally posted by racerfern View Post
        zwolfpack The result of ifconfig is:

        ifconfig
        eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        ether b8:27:eb:bf:09:69 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000 (Local Loopback)
        RX packets 41731 bytes 6556042 (6.2 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 41731 bytes 6556042 (6.2 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.1.53 netmask 255.255.255.0 broadcast 192.168.1.255
        inet6 fe80::b165:3d2b:a8a3:6a22 prefixlen 64 scopeid 0x20<link>
        ether b8:27:eb:ea:5c:3c txqueuelen 1000 (Ethernet)
        RX packets 283938 bytes 78566615 (74.9 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 43442 bytes 7153480 (6.8 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        This indicates that the wired interface (eth0) is down (no IP address), and wireless (wlan0) is up with address 192.168.1.53. Does this sound right?

        Comment


          #19
          Originally posted by racerfern View Post
          AFA the sudousers file, I still get homeseer is not the sudoers file. This incident will be reported.

          It also fails when in SSH session.
          Couple things

          1) which user did you use to run the installer? That obviously has sudo capability.

          2) Verify that the file at /etc/sudoers.d/010_homeseer-nopasswd was correctly written with contents

          Code:
          homeseer ALL=(ALL) NOPASSWD: ALL
          I just re-verified it works properly here.

          3) verify that the sudoers file /etc/sudoers hasn't been altered from the distribution and contains this line:

          Code:
          #includedir /etc/sudoers.d
          The solution in post #17 works ok too, after the homeseer user logs out & back in; however it requires the password to be entered each time.

          Comment


            #20
            This indicates that the wired interface (eth0) is down (no IP address), and wireless (wlan0) is up with address 192.168.1.53. Does this sound right?
            That is correct. I disconnected the wired lan because I know my son is probably use it wirelessly.

            Comment


              #21
              I have the wifi VNC working, it wanted the original username and password. No ETH0 required, working fine. thanks.

              Comment

              Working...
              X