HomeAssistance observer - all green but i can't open the log in menu

Installation
1

Hi to all,

i am completely new with HA.

I have a RPi3B, i’ve just download the HA OS 15.2 to my sd.

I’ve connected RPi via Ethernet and i can reach it.

When I open the browser i get
Supervisor: Connected
Support: Supported
Health: Healthy

but i can’t move from this screen on.

Can somebody help me?

RPiB
RPiB2532×1442 153 KB

2

Can you attach a monitor and keyboard ?

3

Hi,

You’ve found the HAOS observer on port 4567, but have you found the main GUI on port 8123?

A Rpi3+ is right on the edge of what HAOS will run on, so my guess is HAOS has booted but HA is still being downloaded and configured.

My RPi3b+ thest system can take 10minutes just to reboot.

4

RPi3 is insufficient with moden versions of HA.
For a while there were a warning with a text saying the RPi3 was on the edge, due to limited ram, but lately the warning have been changed to a text saying the RPi3 is insufficient due to ram.
And now the text have been changed to 2Gb ram is required, which RPi3 can not fulfill.

5

It is very important to be precise about WHICH RPi3 is being discussed:

  • The RPi3b only has 1Mb of RAM which is not enough for HAOS (and has not been for years).
  • The RPi3b+ has 2Mb of RAM 1Mb of RAM which is just enough to run HAOS - although this is not recommended as the 1.4GHz CPU is really a bit old and slow.

Both the RPi3b and RPi3b+ have both been removed from the HAOS documentation, so the RPi3b+ is likely “Not supported”, and personally would not recommend using anything slower than a RPi4.

I still run a RPi3b+ as a pre-production system on HAOS Beta, and accept the slow boot times, and that it will in time become unusable.

EDIT: Corrected the RPi3b+ RAM to 1Mb - really thought the RAM was the HAOS barrier. Can’t be the CPUs as very similar, only clock speed increases.

6

Please check your own links again.

7

They are correct.

8

From the page you linked

Specification

The Raspberry Pi 3 Model B+ is the final revision in the Raspberry Pi 3 range.

Broadcom BCM2837B0, Cortex-A53 (ARMv8) 64-bit SoC @ 1.4GHz
**1GB LPDDR2 SDRAM**
1 Like
9

I meant read the specs on the links you provided.
Francisp provided the important snippet.

1 Like
10

Thanks both for the spot - I really thought the RAM was the HAOS barrier. :flushed:

(Might have been thinking of the RPi3a+ which I used for GPSr camera projects.)

It can’t be the CPUs as they are very similar (both capable of 64b OS), with the clock speed increasing slightly which ISTR was noticeable when the hardware first came out but these days isn’t that much of a jump.

My RPi3b+ test system ticks along on HAOS using 0.7 GB / 1 GB RAM (should have checked earlier…) with HACS, etc but is dog slow to update and reboot. Not recommended!

I think we are all expecting HAOS to really require 2Gb RAM after the HA install docs changed, but the only actual engineering change I’ve seen has been the removal of 32b OS versions (and the foundation lists 64b OS for all RPi3 albeit less efficient for some).

Meanwhile, my production Yellow system moved to a CM5 as large ESPhome compiles need 2.5Gb RAM, even limited to a single thread (default Yellow CM4 was 2Gb RAM).

11

RPi3b+ is the biggest of the RPi3s ramwise, so none of them is suitable for HAOS today.

You might be lucky to run yours, because 0.7 of 1Gb is pretty risky.
The 0.7 is the allocated amount.
If the system tries to allocate more than 0.3, then it or the app/container will crash and you will see it in the state value you read, because it was never successfully allocated.
Even an attempt to allocate less than the 0.3Gb can fail, because sometimes the allocation is required to be continuously addressed and that might not available due to the fragmention of allocated memory for apps, where the memory is allocated for some programs and released for other.