intendevo, ho flashato eWeLink CUBE OS nella tf card, avvio in modalità tf “stessa procedura di HA” lampeggia blu ma non avvia la lan nemmeno così
Mi chiedevo, non è che magari HA ha cambiato qualche impostazione nella lan e questa non viene più riconosciuta da eWeLink CUBE OS?
che ne sò, magari il firmware della lan?
“Nel caso estremo è possibile flashare il firmware di eWeLink CUBE OS da usb con il pc?”
The OS image I provided is not eWeLink CUBE OS. It is a specialized OS image which is just used to collect logs of previously booted eWeLink CUBE OS (from the internal eMMC, not TF card). It will not change the light effect of LED side strip, so you will notice the Breathing Blue light effect keeps going on and on.
You need to find the IP address of this running OS from your router. Did you see the IP on your router’s web console? You may need to wait for about 1 minute until the OS has fully completed its startup.
è come se la lan fosse spenta anche cosi
I see. We will provide an updated OS image tomorrow that could collect logs and store them on the TF card. So if you can’t download logs from the web console, you can get them directly from TF card.
Spero sia questo
Where did you get these logs? Is the logs from eMMC, or just from within HA? Is your HA connected to LAN through ethernet?
TF card, specialized OS image eWeLink CUBE OS
Oh, this is smart. Could you please get the booting logs of HA over iHost, the same way as you get specialized OS logs from TF card.
The logs should be located at TF card's root directory/hassos-data/logs/journal
system.journal (8 MB)
speriamo sia questo “log di homeassistant”
Hi @ReSeCa , the log you uploaded shows that you are not using the Home Assistant OS image provided by iHost Open Source Project, but the HAOS image from darkxst.
The Home Assistant OS version is 12.0, right? Can you please take a screenshot of the web page at Settings -> About.
Yes, you are using Home Assistant OS for iHost from darkxst, not us.
Sadly, breaking the ethernet chip is a known issue of darkxst’s HAOS image for iHost. We can’t do anything about it 
Why did you use the HAOS image from darkxst, not the one from iHost Open Source Project?
ho messo HA al dayone, quindi non capisco, rotta? non dovrebbe piu funzionare nemmeno in HA o sbaglio
As you can see in the issue I posted previously, darkxst’s HAOS image is using a wrong DTS setting (vcc_1v8 instead of vcc3v3_sd for vccio5 and vccio6) which would cause damage to ethernet chip.
In our’s eWeLink CUBE OS and HA over iHost, the value for vccio5 and vccio6 is always vcc_3v3_sd. The sad part is, if you have booted darkxst’s HAOS image once, then the ethernet chip is forced to be powered with 1.8v voltage, next time you boot eWeLink CUBE OS which will power ethernet chip with 3.3v voltage, the ethernet chip won’t work.
You can continue to use darkxst’s HAOS for iHost if the ethernet still works.
viene forzato a funzionare con 1,8volts, quindi con un voltaggio minore. quindi deduco che una volta che va a 3,3volts in eWeLink CUBE OS è come se andasse in protezione e non si avvia.
visto che ormai non lo utilizzerò piu per HA se trovo uno schema del chip voglio vedere se riesco ad abbassare la tensione con uno stepdown dc-dc
We have known this issue for more than 1 year. Our senior hardware engineer told me it can’t be fixed. But maybe you could pull the trigger. I’ll talk to our senior hardware engineer to see whether we could provide you the schematic of the ethernet chip next week.
ok, comunque perdonami per il tempo che ti ho fatto perdere, non conoscevo il problema dell’ os di darkxst’s, Sorry
By the way, if you don’t want to run darkxst’s Home Assistant OS on iHost, what do you want to do with iHost? Using the built-in eWeLink CUBE OS? Using the HAOS from iHost Open Source Project? or running your own custom built Linux OS?
Never mind, I am always glad to help.
trovato, è un chip realtek rtl8201fl accoppiato ad un filtro trasformatore di isolamento di rete.
per adesso l’unica cosa che posso dire è grazie. Se dovessi trovare un rimedio “cosa alquanto improbabile” ti contatterò subito. Grazie ancora
i voltaggi sui 3 pin di alimentazione coincidono sui 3,3volts sia in TF HA che in MMC eWeLink CUBE OS, cerchiamo altrove
