Can you post a screenshot showing this? Just in case that shows something that could be the issue? Reaching for straws here…
You do not have to SSH into HA. In fact, out of the box, you cannot SSH to the Green. You can enable SSH, but it’s a process you don’t need at the moment.
Connect a keyboard and monitor to your HA green and you will be at the console where you can enter the commands mentioned earlier to rebuild the Home Assistant Docker container.
Again, network troubleshooting is pointless. You are browsing to a web server on the Green when you check the Observer URL http://192.168.0.236:4357. You have stated you can reach that from another computer on the LAN.
Observer is another Docker container like Home Assistant core (the :8123 web server). If you can reach the Observer web service, then the Host OS must be working, and the networking stack must be working. If the OS and networking stack are working, the problem must lie in the core Docker container itself. The commands given earlier are designed to recover from this specific issue.
You can validate if the core docker container is running once you have access to the console, and if that step is necessary.
Good luck.
Thank you very much and very clear. So I did this and seem to have made things worse! I got a response of “unknown error” from HA CLI and on host reboot I cannot even get into the CLI. I attach the CLI responses. My current screen after rebooting and going through a series of initialization messages [ 5.nnnn] is “Waiting for the HA CLI assistant to be ready…” then "[WARN] Home Assistant CLI not starting! Jump into emergency console…
Is this a screenshot of your current status? It doesn’t say anything about the emergency console.
Common tasks - Operating System - Home Assistant
Check the
supervisor info
and
supervisor logs
commands
If you are lost, you can also try resetting the entire unit:
Resetting Home Assistant Green – Nabu Casa
Or start here:
I can’t access Home Assistant Green via http://homeassistant.local:8123. – Nabu Casa
Thanks, I have now graduated to be able to post more than one image at a time (yay). So after a few reboots I am back in CLI so have run the info and log commands. Not sure what I am looking for but attached.
It doesn’t have an IP address, how are you connecting? If you look at the top end0 it does not have an IP address assigned. I’d strongly recommend you connect via a known cable at least to get it working.
Your list of installed docker containers in the supervisor info list doesn’t match with “Plugged in new HA green and it’s not working”. I see Music Assistant, HACS, ESPHome. You seem to have left out a lot of details and history.
1 Like
Hi there I connect via LAN cable and the router shows the presence of HA as well as being able to connect the Observer. It was as far as I know a brand new HA Green purchased as such. Following one thread I tried to flash with haos_green-16.2.img and then boot with a CONFIG USB Setup. I have no idea if that worked as none of the symptoms changed and that was before i shifted to connecting keyboard and screen direct to the unit. I will look into the LAN cable issue this evening.
Hi there. I have changed the LAN cable and rebooted. Situation is about the same except that HA CLI showed the correct IPV4 address this time. So I am stuck again. Could it be possible that in fact what I have is a defective or refurbished unit? Or are there suggestions of other things I can try to do?
I’d recommend visiting the link I provided earlier and click the “Submit a ticket” button in the top right. You have support for that device.
1 Like
Have you tried
ha core rebuild
ha core restart
Try
ha supervisor reload
Also
ha host info
And look at the RAM and memory.
Where did you buy it?
Thanks very much. Not sure if the attached shows ram or memory, host info. I bought it online at one of the suppliers listed on the Home Assistant page.
This really should be finished by now. At this point I would re-flash Home Assistant.
Yes, but with the instructions for the green instead. https://support.nabucasa.com/hc/en-us/articles/25161225495837-Resetting-Home-Assistant-Green#resetting-the-device
SOLVED. Thought it would be worth summarizing the process and thanking all the helpful posters (spoiler I ran ha os datadisk wipe on the CLI):
On setting up the new Home Assistant Green the android App could not detect the unit automatically nor using all the manual iterations we could think of.
We went through things to do with the IP addresses and the router including changing the Starlink modem to be pass through only thereby ensuring it was not interfering with DHCP or assigning/blocking IPs.
I changed the LAN cable in case this was an issue. And I defined a static IP address for the HA - at all times the HA showed up as a connected device in the router’s list.
I was still not able to connect to Home Assistant on PC on http://homeassistant.local:8123/ but I was able to connect to Home Assistant Observer (http://homeassistant.local:4357)
I tried to flash the operating system by inserting an SD card with an image of v 16.3 or a hard reset as per web guidance but as it turned out later this was not successful.
As suggested by mterry63 I submitted a ticket on page Resetting Home Assistant Green – Nabu Casa The assistance was slow and
methodical and due to timezones limited to about one email a day and not weekends so it dragged out.
Meanwhile all rescue operations switched to the HA console (CLI) by connecting keyboard and screen to the device. Following advice from stevemann I tried to rebuild the docker using ha core rebuild, ha core restart, ha host reboot but got an error and no progress. As suggested I checked status with the HA commands supervisor
info and supervisor logs.
By this stage nabucasa helpdesk had worked their way through the basics (pretty much as above) with me and suggested that first I update the operating system as they spotted that it was version 12.2. The
approach was to run “ha os update” which may take a more than one attempt as it won't be able to update to the most recent version (16.x) all at once.
The success of the update was proof that the connection to internet was working and also brought me to version 16.3 which is important as this version allows an easier way to reflash the OS which was the
suggestion of stevemann but would have required the tweak according to HA green operating system as pointed out by luxia.
I was then asked by Support to perform ha su repair (which completed) and ha rebuild (still gave error). At this point I was given the instruction to perform ha os datadisk wipe - which was not a
big deal given that no installation had taken place yet.
I left ha os datadisk wipe running and went to bed - in the morning the HA android app could detect the HA Green no problem.
1 Like
Woot! Glad it’s sorted. And kudos to you for sticking with it!
1 Like