After the investigation and analysis of the ethernet malfunction issue, we found that there is a problem with the configuration in this project (0023-dts-pmu_io_domain-set-wifi-to-3.3v.patch). This incorrect voltage domain configuration can damage the IO ports of the RV1126(RV1109) during use, preventing them from outputting proper voltage or data waveforms. This hardware damage issue has been verified and confirmed on the faulty devices received. Rockchip’s official response also indicates that such a misconfiguration carries the risk of causing this damage - as clearly warned in the official Datasheet, advising users to avoid incorrect voltage domain parameters to prevent irreversible hardware damage. Once the IO ports are damaged, they can no longer communicate normally with the external Ethernet chip, which results in the failure of your Ethernet functionality. Even if you switch back to the native system at this point, your hardware has already been damaged by running the system with the incorrect voltage configuration. We have asked @darkxst to correct the pmu_io_domains Ethernet configuration ASAP.
For all the iHost users who would like to run the Home Assistant OS on iHost, please note this potential risk, do not run Home Assistant OS on iHost until this configuration has been corrected to avoid the Ethernet malfunction and hardware damage risk.
After the investigation and analysis of the ethernet malfunction issue, we found that there is a problem with the configuration in this project (0023-dts-pmu_io_domain-set-wifi-to-3.3v.patch) which may cause potentially permanent damage to the Ethernet functionality. We have asked @darkxst to correct the pmu_io_domains Ethernet configuration ASAP.
For all the iHost users who would like to run the Home Assistant OS on iHost, please note this potential risk, do not run Home Assistant OS on iHost until this configuration has been corrected, or the Ethernet will malfunction and the product warranty will be void because of this issue.
This is complete nonsense, there is no way these settings are damaging the IO ports on the SoC.
I don’t know if there are difference in the upstream kernel drivers here, however if I set vccio5-supply to vcc3v3_sd then the MAC fails to communicate with PHY (see below error). This is presumably why I have kept this set on vcc_1v8. Unfortunately the RTL8201F datasheet does not provide any information on the RMII signalling voltages. Phy-supply is correctly set to vcc_3v3 though.
Hi, I just bought an iHost with the intention of running HAOS on it. I’m a little concerned after reading recent posts.
Should I wait for the new improved version of HAOS or are these just excuses from ewelink and I can run the current version without any worries?
I’m trying to find a solution for this, however its not as simple as just changing a config option. Unfortunately the Sonoff folks have completely ignored my replies to their comments in their threads etc.
I can’t verify if in fact HAOS is causing damage, however there are also reports about Ethernet dieing on stock iHost OS.
Do not give up. You did a GREAT job. You saved this device from being thrown into the trash. So now my second device is running HAOS (perfect) and first (warranty exchange) is waiting for even better HAOS. I didn’t even take the warranty exchange device out of the box because stock firmware is so limited and buggy. We believe in you.
Yeah, it is awesome that you even made any of this possible at all, however at this point I would not recommend the Sonoff iHost to anyone as a new purchase.
@darkxst off-topic but wondring if you have considered trying to apply for a job at Nabu Casa? → Nabu Casa / Home Assistant | Remote …My guess is that they would probably be interested in hiring for a unlisted role with broader width than the job listing there now list if you contacted them
As others said, you did an awesome work here. It’s too bad that we don’t have a more concrete answer from the guys at Sonoff. Hopefully they are still investigating and will give more details soon. I now have a replacement on it’s way to my home but probably will keep it in the box until we can be sure that it can run HA safely.
Yeah, other than it only having a single USB port and do not ship with a case the inclusion of an onboard NVME M.2 SSD slot (like the Home Assistant Yellow) makes ODROID-M1S a more attractive hardware solution than the official Home Assistant Green appliance for users who might want to the storage for features like camera recording (NVR).
If they could ship ODROID-M1S pre-packaged with Home Assistant OS pre-installed out-of-the-box as well already fitted into nicer case (preferably all-metal aluminium enclosure) then could it be a hit! …like a new variant of Home Assistant Blue which was based on ODROID-N2+
I bet Nabu Casa would be very interested in you to on many of the same type of the same stuff as agners (who other than working on Home Assistant Operating System also works on a much similar wide range of various different projects related to Home Assistant)
Hello Fabiano! I want to thank you for your development to save the initial Ihost hassio project. I installed it on 3 clients and they all had problems on the eth0 port, so in a way the Chinese guy from Sonoff is right in saying that it burns the network card, but I realized that this only happened on routers that have integrated Wifi 6, a client with Wifi 5 went for months without any problems and when I switched to a router with Wifi 6 it immediately burned ihost’s eth0.
The usb ethernet adapter solution has proven to be great because you can choose the manufacturer’s network card that you think is best, even if the Ihost one is predefined. I discovered that there are some usb-ethernet network adapters that are not compatible with Ihost, it needs to be one that has more affinity with the Linux kernel.
In some cases where eth0 has burned out for good, it is not necessary to change Wired Connection 1 as the card is no longer recognized by Ihost, but when eth0 is half-life, it is essential to deactivate Wired Connection 1.