Sorry for the inconvenience, but my ihost doesn't work anymore

iHost Open Source Project
1

Hello, I have encountered a problem with my ihost, following the official procedure to start Ha the latter works well, however, finding slowness I preferred to use an ad hoc device. Here the problem begins. I restart Ihost doing multiple tests even with different sd and nothing, ihost starts I also hear the sound but the lan does not work, done a thousand tests, I put the sd back with HA and everything restarts quietly even the lan. I really can’t understand what happened if the lan was burned it should not work with HA. Nb: I tried to keep it turned on and connected for three days in cube mode but nothing

Sorry for the spelling mistakes, I’m using google translate

2

Based on your report, it’s possible that the iHost sustained damage during experimental configurations involving Home Assistant. There have been documented instances where initializing HA on iHost led to LAN port failure. However, the current description lacks sufficient diagnostic clarity, and it appears machine translation may have introduced inconsistencies or loss of context.
Identifying the root cause from this information alone will be challenging. The eWeLink support team may need to perform additional troubleshooting and will likely follow up with targeted technical questions to narrow down the failure point. Perhaps you should place a support ticket? Cross my fingers :crossed_fingers:t2:

3

Hi, don’t worry, we are here to help.

First things first, if you can describe the issue better in your native language, please do so, and let us handle the translation.

Second, using Home Assistant OS image from iHost Open Source Project won’t break your ethernet hardware (LAN). We are certain of it.

Third, from your description, it seems iHost can’t boot into eWeLink CUBE OS (the build-in OS on internal eMMC), and also can’t boot into Home Assistant OS on the TF card, right?

Let’s troubleshoot the issue:

One: Let’s boot iHost from TF card.

Can you be sure that iHost is booting into Home Assistant on the TF card? Did you see the LED side strip lighting pattern: Marquee Red turns into Breathing Blue, and if there is any error during the booting process, the LED side strip will be in Solid Red.

Here is a demo of showing booting error from TF card:

If you see the LED side strip is in Breathing Blue for about 1 minute, then you can try to find out the IP address of the HA (on the TF card) running on iHost. You should be able to find it on your router’s web dashboard.

If you see the LED side strip is in Breathing Blue for a long time, such as more than 5 minutes, but you are sure that there is no IP address for HA on your router’s DHCP leases list, then the file system of HA on TF card might have been damaged. My suggestion would be to reflash the HA image onto TF card. But this time, use a TF card from SanDisk, Kingston, or Samsung, and use haos_ihost_CoreBox-15.2.1.img.xz instead of haos_ihost-15.2.1.img.xz. Note: Decompress haos_ihost_CoreBox-15.2.1.img.xz before you flash it onto TF card.

Two: Let’s boot iHost from internel eMMC.

When you boot iHost into eWeLink CUBE OS (on the internal eMMC), the LED side strip should be in Marquee Red until it changes to Solid Blue. If you see Solid Red instead of Solid Blue, it means the network (ethernet or Wi-Fi) isn’t working. If you only see Marquee Red, there is no Solid Red, Solid Blue, then you probably has updated the firmware of MG21 chip (the Zigbee adapter) which is incompatible with eWeLink CUBE OS.

Please take your time to try out above methods, and tell me the result, especially the LED side strip lighting pattern.

4

We’re not sure which image (s)he used — it might have been something else, even though the procedure may have been considered ‘official.’ Unfortunately, (s)he didn’t specify :smiling_face_with_sunglasses:

5

Provo a spiegarmi meglio, Home assistant funziona perfettamente con la sua micro sd, riavvio in modalità cube, striscia rossa che scorre, si avvia, luce rossa fissa e sento il suono di quando normalmete si avvia, il problema sta quì la lan non funziona su cube. se rimetto microsd con Home assistant riparte e la lan funziona.

6

quindi la lan non è bruciata, stranamente in modalità cube si avvia e sento il suono, ma la lan non va.
è come se fosse spenta

7

Yes, this is really strange, we haven’t seen this issue before.

Just to double check, you know exactly how to switch from eWeLink CUBE OS on the internel eMMC to Home Assistant OS on the TF card, and vice versa, by repeatly single-pressing the mute button within 3 seconds after a power cycle of iHost. And you know how to verify it by checking the LED side strip light effect.

Have you done some configuration in eWeLink CUBE OS, like enabling Wi-Fi, and updating MG21 firmware in Home Assistant?

Could you provide a short video of your iHost LED side strip light effect to show the full booting process of eWeLink CUBE OS.

8

ho fatto il video, ma non so come postarlo. sono capace di fare il cambio fra hassio e cube os, se volete posso farvi vedere anche hassio che si avvia ed è funzionante.

"Have you done some configuration in eWeLink CUBE OS, like enabling Wi-Fi, and updating MG21 firmware in Home Assistant?

questo non l’ho ancora provato, puoi indicarmi perfavore una guida? grazie"

Edit: l’ho uplodato su google drive

9

Thank you very much for the video. I fully believe you know how it works.

The issue is definitely new to us. Please give us some time to conduct a thorough and comprehensive study of this issue.

10

va bene, fatemi sapere voi allora. grazie

11

We have carefully analyzed the booting process and reviewed the code. So far, we haven’t noticed any abnormalities.

We have thought of two ways to see if we can solve this issue.

  1. Reset the eWeLink CUBE OS on the internal eMMC.

  2. Collect the logs of booting process so that we can further analyze the cause of the problem.

We hope to get the log in order to fundamentally solve this issue.

If you are willing to help, we plan to provide a dedicated operating system firmware which can be flashed onto TF card, similar to HA over iHost. You can follow below steps to get the log:

  1. Flash the OS image onto TF card.
  2. Boot iHost from eWeLink CUBE OS (internal eMMC) to generate logs.
  3. Boot iHost from TF card, visit the web console, follow the instructions on the web console to download the log of previously booted eWeLink CUBE OS.
  4. Send the log to us.
12

Proviamoci, almeno non resta un fermacarte

13

mamma mia mi fa diventare pazzo, rimetto HA e funziona :scream:

14

Hi, please download the OS image from URL https://drive.google.com/file/d/1iOi8edA95dKAEOHMSPTxNMKc9vGheqHn/view?usp=sharing

  1. Boot iHost from TF card, visit the web console, follow the instructions on the web console to download the log of previously booted eWeLink CUBE OS.

You should be able to find the IP address of the running OS from your router within 60 seconds after booting. You can then visit the web console at http://IP:8080 (change the IP to the real IP address of iHost, such as http://192.168.1.80:8080 if your iHost’s IP is 192.168.1.80). The web console is simple, just click Download Log Archive and wait for the download to finish.

Web_Console_With_Log_Download
Web_Console_With_Log_Download1366×866 113 KB

15

I don’t understand now. You said HA over iHost works before, and eWeLink CUBE OS on iHost can boot successfully, just doesn’t have a working network (ethernet).

Home assistant funziona perfettamente con la sua micro sd, riavvio in modalità cube, striscia rossa che scorre, si avvia, luce rossa fissa e sento il suono di quando normalmete si avvia, il problema sta quì la lan non funziona su cube. se rimetto microsd con Home assistant riparte e la lan funziona.

16

The Breathing Blue light effect means you are using HA over iHost (actually any OS on TF card)

17

si si, è che la cosa mi fa diventare pazzo

18

That’s why we’ve created a specialized OS image to collect the logs of the booting process of eWeLink CUBE OS (not HA over iHost).

Please take your time and follow previous instructions to download the log archive.

19

non attiva la lan nemmeno cosi :face_with_raised_eyebrow: (lampeggia blu)

possiamo fare qualcosa da HomeAssistant?

Flash the OS image onto TF card con balenaEtcher

20

The Breathing Blue light effect just means you are booting an OS on the TF card whereas Marquee Red light effect means you are booting eWeLink CUBE OS on the internal eMMC.

If you want to control the LED side strip light effect after booting HA over iHost, you can use iHost Hardware Control Add-on.

Actually, we have developed (and open sourced) many add-ons to improve the user experience of HA over iHost. Please refer to Hassio iHost Add-ons for details.