Yes, that update. I’m not sure if I can install it or if, since it’s a special version of HA for iHost, I might corrupt it by updating from HA. Could you guide me, please?
I updated it! It doesn’t cause any problems! It works great!
I think the OS update will just be downloaded from Releases · iHost-Open-Source-Project/ha-operating-system · GitHub.
I recommend you make a backup first!
Update and enjoy!
2 Likes
Thank you very much! You have been a great help in this process. This is my first time using HA, and it has been a pleasure and very easy thanks to your contributions!
Indeed, it is. It’s a 32-bit custom image (unofficial release). You’ll get updates until this project is alive. There are no official 32-bit images of Home Assistant OS (HAOS). iHost is 32-bit piece of hardware and officially there’s no future for 32-bit HA(OS).
This is a huge concern
iHost Home Assistant OS 15.1
2 Likes
After update eWelink Smart Home to 2.5.5 all scenes work without problems again.
1 Like
Hi everyone
It’s been a couple days since my first attempted to install HA on my Ihost. The first time the installation went ok, and I was able to use HA in less than an hour. However, there was some text missing from various areas on the dashboard, I tried to restart HA but it failed to boot up (Even left it overnight but no luck). At first, I thought something wrong happened during the installation, so I tried to install it again.
This time I ran into some issues where the typical ip:8123 was not responding, but I managed to fix it by factory resetting my Ihost and trying the installation again. It worked and I ran HA for a day without any issues but since I had to physically move the device, I had to turn it off. But after powering it on, it was not booting up again. It was showing the breathing blue pattern on the front, but again no matter how long I waited It did not boot back up (just as the first time). After that, no matter what I try I have not been able to successfully boot HA anymore.
I have tried to Factory reset, tried 3 different SD cards (different capacity and manufacturer), formatted the cards in 2 different computers, tried with both the original HA Ihost release of 14.1 and now 15.1, but nothing.
In some attempts I cannot even ping the device IP and when I can, port :8123 never becomes available. I don’t even get an error red light but constantly breathing blue pattern and quite frankly I’m losing my mind trying to get this to work. Fortunately, it seems like I can return to CUBE without any issues so that’s a plus, but I have run out of ideas to run HA
Any suggestions?
Thank you for sending your questions here. We’re already trying to reproduce your issue. We’ll get back to you soon.
Yes, there is one. Run your HA instance in full flavour (HAOS) in 64-bit on some other piece of hardware; like Raspberry Pi 4.0 with NVMe on USB, if you can afford.
I’m aware doing it on Ihost is not the best option, I own a HA green that basically replaced it many months ago, but right now I have the need for another instance for basic stuff and if it’s officially possible to install it, might as well use it than throw it away and spend more. Just you know… hope it actually works at some point.
Ah, the adventurous route of running Home Assistant (HA) on iHost—a bold expedition indeed, but one might say it’s more like wandering into a cul-de-sac while expecting a highway. A 32-bit modified image, essentially an act of defiance against progress, sounds like a rallying cry for those who insist on squeezing water from a stone. This setup practically relies on the brilliance and sheer stubborn determination of one dedicated enthusiast and the small band of his helpers.
Of course, it is possible to make good use of iHost in conjunction with Home Assistant. But not by installing HA on this hardware. I use a similar solution myself.
It seems that the addition of the ability to run 32-bit HA on iHost is a gesture to those disillusioned by the marketing boast. Some would sarcastically call it a swan song. This theoretically well-intentioned iHost collided with reality and a beautiful disaster occurred 
Hey bro,
HomeAssistant OS has an Observer plugin built into Supervisor, which provides a diagnostic portal (Observer Portal) via TCP 4357 for: Real-time viewing of Supervisor’s running status. When the main interface (port 8123) is inaccessible, basic troubleshooting can still be performed through the browser or API. You can try to access this port to find a solution to the problem. And as far as I know, HomeAssistant’s port 5355 will broadcast mdns, and you can use related mdns tools to confirm whether the system has started successfully. If HAOS starts successfully, but port 8123 is still inaccessible, it may be that the homeassistant core add-on has failed to run.
But the key to all this I said is that your HA device can obtain an IP address.
For me, HA would run perfectly, but after about a day it stops requesting an IP and drops the network while running. The previous installation didn’t recover even after a reboot, and although the current one works after restarting, it’s unfortunately useless if it’s not reliable. HA 15.1.
So I understand that ‘Home Assistant Core’ updates can be done OTA, but for HAOS updates I need to re-flash the TF card, correct?
Thanks for the info, I checked 4357 but it’s also unavailable.
I’m not familiar with mdns so not sure what I could do there, but it does appear as open.
The only ports that are available are 111 (something called SUN Remote Procedure Call) and 5355, everything else is unavailable