#HA Green with famous "low voltage" issue. I'm out of options.

1 messages · Page 1 of 1 (latest)

teal bough
#

I just bought green.
Opened http://homeassistant.local:8123/ page, started restore from full backup.
I went away and when came back few hours later computer went to sleep and HA Green isnot responding to http. while on router I see it's alive with assigned IP address.
Restarted, nothing.
Following troubleshooting conencted to monitor:

5.1227951 rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.
[5.1238811 rtc-pcf8563 1-0051: registered as rtc
5.1256531 rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.
5.126617] rtc-pcf8563 1-0051: hctosys: unable to read the hardware clock
5.136131] rockchip-vop2 fe040000.op: Adding to ionnu group 2

This stayed on screen for a long time. then finally it loads HA shell.

#

ha› log in

timedatectl

[ 2082.639599] rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.
Failed to query server: Failed to read RTC: Invalid argument

timedatectl Igrep Time

I 2152.935533] rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.
Failed to query server: Failed to read RIC: Invalid argument

date -s "2024-07-30 21:38:50"

Tue Jul 30 21:38:50 UTC 2024

timedatectl Igrep Time

[ 2320.815563] rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.
Failed to query server: Failed to read RTC: Invalid argument

#

I can't understand how to attach image here in thread

outer flint
#

That RTC low voltage error message can be ignored. It just shows, that no battery is used for the real time clock (not mandatory).

teal bough
#

the only recipe for this seems to be setting the date, that's what I tried.

outer flint
#

Recipe for what?

teal bough
#

to get it working

#

to respond on 8123

outer flint
#

For setup an internet connection is required. The time and date will be pulled via NTP.

teal bough
#

it is plugged into internet and on first boot it opened web UI and was working.
then it ingested backup but don't know what happened next because it stopped responding.

Could tit be that with backup restore it ingested some ip configuration of existing HA server (ova running in VM)

outer flint
#

That could be possible

teal bough
#

is it possible for me to see any of that configuration in this shell mode?

outer flint
#

You can run ha network info end0 to see the present network configuration

teal bough
# 
~~ready:  false~~

~~same for ipv6~~~~
#

ops I move it

#

ignore that 🙂

#

yes It's got the ip address of correct network that I onboarded it on initially

outer flint
#

Restarting during rebuild might also have broken it.
If it does not start, I would do the following:
a) do a reset of the Green (https://green.home-assistant.io/guides/reset/)
b) do the full onboarding with temporary login data

#

c) upload the backup on the backup page

#

d) trigger the restore manually from the backup page

teal bough
#

okay will do that
thank you !!!! 🙏

outer flint
#

And wait until it has finished. It can take quite a while (depending on the backup size).
To check if it has finished, use another browser tab to call the HA page from time to time. The one with the backup page might not refresh, but I'd let it be as is.

#

The temporary login data will be overwritten by the ones from the backup.

teal bough
teal bough
#

one question. I've read that since it doesn't have cmos opwer the date setting might have to be done every time there's power loss, theoretically.
Installing CR2032 into Green will help with that?

outer flint
#

The time and date should be set via NTP. The battery should unly be needed during prolonged periods without internet access (which is needed for setup or update anyway)

#

It does not hurt to insert one, but usually it is not needed. Raspberry Pis also don't have a RTC on board.

teal bough
#

got it to work! thank you!!!

#

now I have two HAs on network , should I shut down the old one immediately?

outer flint
teal bough
#

they're on different dns names. I wonder if automations and triggers may cause things executing twice

outer flint
#

I would recommend to check, if all integrations still work - just to be safe.
Two instances doing the same might cause some unintended stuff indeed.

#

I would shut the old one down.
So you would see, if the Green is doing all the stuff it is intended to do (and not the old one) and it would prevent other issues with competing instances

teal bough
#

thank you again! and your advices should be on that troubleshooting page. so less people bothering you 🙂