HassOS 3 released! Raspberry Pi 4 support

Blog
75

I’m having a problem with Date/Time. I’ve installed Hassos but when the system boots/restarts the system time is set to Fri Dec 21 2018 which naturally causes a few issues!
What is the cause of/cure for this.
Rapsberry Pi 3B+ over WiFi using
StarTech USB3S2SAT3CB SATA to USB Cable, USB 3.0 to 2.5 Inch SATA III Hard Drive Adapter
Kingston Technology A400 SSD 120GB

Update: I believe I have a solution. It works for me anyway
In researching my problem I came upon this:
https://github.com/home-assistant/hassos/blob/dev/Documentation/configuration.md
which states:

"Our default ntp configuration look[s] like:

[Time]
NTP=time1.google.com time2.google.com time3.google.com
FallbackNTP=0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org

Further, I discovered that a) my Synology NAS times out when trying to synchronise time settings with NTP server time.google.com and b) so does ntpquery when querying time1.google.com
So I decided to try reversing the ntp configuration and I used a timesyncd.conf file containing:

[Time]
NTP=0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org 192.168.1.xxxx
FallbackNTP=time1.google.com time2.google.com time3.google.com

where 192.168.1.xxxx is the local IP address of my NAS on which I have enabled the NTP service.
Bingo! My system now boots and reboots fine.

76

I would like to use GSM as failover and send Alarm SMS. But I can’t find clear instructions anywhere - does anyone know more?

I have this GSM HAT:
Waveshare GSM/GPRS/GNSS/Bluetooth HAT for Raspberry Pi
https://www.waveshare.com/wiki/GSM/GPRS/GNSS_HAT

77

And now you see why I have been confused! I an running a RPI4 with raspian and the generic Linux install. So the question is what version of Home Assistant am I running?

I’m so confused!

78

0.103 most likely. The version 3 here is for HassOS not home assistant.

79

??? I’m sorry. I have no idea what this means…

Yes, but every one of those examples is some flavor on Linux. Which is why people talk about installing on a Generic Linux Server (as does the documentation) as opposed to Hassio from a HassOS image.

I would if there was more than one way to install it. If Chrome came as a separate all included package with its own OS as one way to install it or if you could install a similar (but different) OS then install Chrome on it afterwards then I would definitely refer to “Chrome installed on X” if it was pertinent to the conversation. Just Like I do when I say “Hassio installed in Docker” which implies I’m not using a HassOS image of any kind.

And even in the docs to install Hassio on a generic linux server one of the steps to “preparing your machine” to install hassio is to install Docker first.

I think the confusion came in when whoever decided to name Hassio made that decision.

Not only do I end up saying “hassio in docker” to differentiate the different ways to install hassio I also find myself saying “non-hassio HA” when trying to differentiate between HA with and without the add-ons.

The confusion has been created by HA itself.

Exactly.

I would like a simple straight forward answer to that question as well.

1 Like
80

Am I being overly simplistic when I describe my instance as

  • RPi4 (device)
  • Hassos 3.5 (operating system) (including Docker, which runs containers)
  • Hassio 0.103.0 (Application) (a container…)
    ?
81

Yes, it is 0.103, not HASSOS

82

You go to developer tools > info to find the version of Home Assistant you are running.

83

So, I’m still relatively new to HA, and I’ve sifted through all the posts in this thread. At first, I thought HassOS might be another name for the HA server. Now I know better. What I’m taking away from the din is that HassOS is the underlying OS, tailored and specific only to the installation method described in step 1 here:

https://www.home-assistant.io/hassio/installation/

Is my understanding correct? If so, it should be captured somewhere to make it crystal clear.

84

Are you being a smart-@$$ or serious?

if it’s the former…I’ve used HA for over 2 years. I know which release version i’m running. please don’t insult me and treat me like an idiot. I help people on here all the time so I think I can figure out that basic bit of information. Thanks anyway.

If you are serious then let me clarify…

there are (at least) 4 different basic ways to get a version of HA running - HA in a venv, HA in docker, hassio thru HassOS & hassio thru a “generic linux install” (GLI for short) installed in docker.

If I’m running hassio installed via GLI then what do I call the “install version” i’m running?

You are the one who “won’t let it go” so I’d like to know what the wisdom you use that is apparently hidden from the regular people in order to properly communicate which of the different installation versions we are running.

1 Like
85

I hate to further this thread off topic but I may as well add my +1 comment… I too would refer to HassIO as being ‘in Docker’, thus when installing via the ‘Generic Linux install’ we must:

  1. install OS (ie: Ubuntu, Debian, whatever)
  2. install Docker…
  3. install HassIO

… wouldn’t that make HassIO in Docker…? I think the order of installation says it all. The fact that HassIO can’t be installed without Docker is irrelevant when describing the fact that it is in Docker containers.

Again when using HassOS, the installation of HassIO is still in Docker containers, thus HassIO in Docker still describes it.

  • awaiting attack… :wink:
2 Likes
86

the issue with calling them both (installed via from GLI or HassOS) as “hassio in Docker” (but then you could just shorten that to simply “hassio” at that point) is when someone asks “how do I do x in the cli?” Then you need to ask if they installed hassio via HassOS or via a “Generic Linix Install” (or more succinctly “in docker”) since the answer to that, if the former, might be “you can’t” and if it’s the latter then the answer is “like this…”.

If we are just upfront about adding (the apparently officially approved lingo - whatever that might be - ) it saves a bit of back & forth (and therefore time) to get the answer.

1 Like
87

Yes it would Dave. I totally agree…
Still no one has said what we SHOULD call it to distinguish it from HassOS install of Hass.io

88

Unfortunately the officially approved lingo is unknown and referring to it as the obvious Hassio in Docker is verbotten

FURTHER… HassOS is pretty much a full description for that install. Hassio in Docker is also a full description for that kind of install and is differentiated from Home Assistant in Docker… I do not see the problem of saying hassio in docker.

2 Likes
89

Given what all the posts above, especially cognito’s clarification, say about HA is : -
We ALL apparently run hassio.
We ALL apparently run in docker

Given this the use of the above terms almost seem superfluous.
So valid distinctions appear to me (please correct me if I’m wrong) : -

  1. Hardware platform (eg pi, pc)
  2. Base OS (raspbian soon to be withdrawn so - HassOS, Unix, or other OS with a venv layer (apparently not recommended)
  3. Then (they all have, but sometimes you specifically need to install) docker
  4. Then HA

This (to me at least) seems to boil down to 3 routes (finity says 4 but I just don’t see it)

Anyway, irrespective of all that, the people mainly arguing here (apart from me) are VERY experienced HA users who state that the terminology is confusing.
Well God help the newbies then.
Doesn’t this ‘prove’ there is a problem ?

90

no actually.
You can just install HA in a Venv on any linux distro.
Any variety of hassio runs in docker… be it with HassOS or a generic linux install (in docker)
You can also install Home Assistant in Docker - not hassio but Home Assistant.

The issue is there is no ‘approved’ way of referring to the generic linux install of hass.io (other than the whole sentence it seems)

I would see the install as:
HassOS
Hassio in docker
Home Assistant in Docker
Home Assistant in Linux
Home Assistant in venv.

91

That’s running HassIO on docker, which is not the same as running it "in* docker.

HassIO necessitates Docker, since it’s made up of docker containers.

It’s possible (but highly ill advised) to run docker inside docker; so you have HassIO running on docker, all inside docker.

Even trying to put it in words seems to get very confusing very quickly.

92

I honestly truly fail to see the distinction.

But as far as I know not one person means that when they say “hassio in (or on) Docker”. It seems to be generally accepted (amongst the hoi polloi at least) that Hassio in docker is simply just short hand for “hassio in a generic linux server”.

1 Like
93

Hmmm. I would argue that since Docker is the concept of containers (and running things in containers) then we are talking about HassIO being in Docker. We don’t normally put things on a container, we put them in a container.

In this case, we put HassIO spread out in mulitple containers :slight_smile:

94

Not unless you want them to fall off :rofl: