HS3 Pi Installation

[racerfern]

I have an RPi3B+ and a Z-stick by Aeotec. I want to install HS3 and if my son likes HS3 (he is not at all computer literate) then I may buy him a z-net for his house or just use what I want to setup.

I just want to install HS3 on the existing SD card (I have complete mono installed) and have it autostart. Is that possible?

Does the img file I downloaded contain just HS3 or the entire OS as if it's a z-net?

Help appreciated.

[zwolfpack]

Presumably you downloaded from https://www.homeseer.com/updates3/hs...age_070319.zip

This contains HS3-Pi (the version limited to 5 plugins) and the Linux OS. Using this will overwrite anything already on the SD card. The card should be at least 8GB size; however due to slight SD card size differences from vendor to vendor some 8GB cards can be barely too small and won't work. So 16GB may be a safer bet.

HS3-Pi license is different than HS3-Std, if you are planning on using an existing license.

If you want to install either Hs3-Pi or HS3-Std on an existing SD card, I'll recommend this as a fairly painless installation procedure. It includes setting up autostart. An HS3-Linux installer package

[racerfern]

As a follow up to my first post, I realize that I just needed to swap out the SD cards and now HS3 is up and running.

It appears to startup automatically so that's all good.

However, I "think" I prefer installing HS3 onto the raspbian OS that I had on it originally. Can someone help me with that?

[racerfern]

If you want to install either Hs3-Pi or HS3-Std on an existing SD card, I'll recommend this as a fairly painless installation procedure. It includes setting up autostart. An HS3-Linux installer package

zwolfpack - This should be the ticket for me. As always, thanks. I'll report back as I progress.

[racerfern]

zwolfpack No joy, I posted in the HS3-Linux Installer Package thread.

[zwolfpack]

I posted a possible work-around in that thread...

[racerfern]

I'm coming back to this thread because I completed the installation and it's a bit of a challenge. HS3-Pi works seems to be working perfectly but seems to have hijacked Raspbian, I get warnings that "homeseer" is not on the sudoers list and that this will be reported. I can log in through putty but can't log in through VNC because it won't take the same credentials.

I write this because I want to get the dresden zigbee for linux and don't want conflicts that I can't control My plan is to have the zigbee and Aeotec on the same little unit.

Thoughts?

[zwolfpack]

Where are you seeing these warnings?

Are you logging in as pi or homeseer or someone else ?

The installer creates a homeseer userid if one didn't already exist. It doesn't make it a sudo user, maybe it should...

I've never tried logging into a rpi using VNC, only ssh - how did you set that up?

[racerfern]

It's as simple as using putty to log in via SSH. On purpose I mistyped the password the first time. See below


login as: homeseer
homeseer@192.168.1.53's password:
Access denied
homeseer@192.168.1.53's password:
Linux pi 4.19.58-v7+ #1245 SMP Fri Jul 12 17:25:51 BST 2019 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Aug 28 18:16:44 2019 from 192.168.1.38
homeseer@pi:~ $ sudo shutdown
[sudo] password for homeseer:
homeseer is not in the sudoers file. This incident will be reported.
homeseer@pi:~ $

[racerfern]

Using the correct credentials, I cannot login via VNC on WiFi. However, if I plug in the RJ45, I get in just fine.

If I click on Tools > System > Linux Tools I can log in and execute commands such as "dir" for example.

[racerfern]

I've never tried logging into a rpi using VNC, only ssh - how did you set that up?

Darn if I remember. I have a main windows PC in the office, another one in the control center. The control center has a PC with HS3 windows and a z-net. There's another z-net at the other end of the house. Also in the control center I also have another RPi with a raspi zigbee board and the newest RPi with the Aeotec stick and the HS you just helped me setup.

For a year or more, I can either SSH into the PC, either z-net, another RPi with zigbee board or the new RPi. It has all worked wonderfully since I'm not a command line driven guy, even though I used to be. I can also VNC to the windows PC, the zigbee RPi or the new RPI. However when I disconnect the RJ45 to the new RPi I can't get in via Wifi.

I know it's me, but darn if I know where to fix it. Although my immediate concern is the inability to get past this SSH sudousers thing.

[zwolfpack]

The sudousers thing is an easy fix; I'll post it as soon as I get home.

[zwolfpack]

Regarding the Wifi issue - post output of 'ifconfig' command.

[zwolfpack]

To make homeseer a sudo user, paste this line into the Linux Tools command box and execute.

echo "homeseer ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/010_homeseer-nopasswd

[racerfern]

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