@dipalomeri You either need to connect to the debug console via the Type-C power port on the iHost or setup host ssh access:
The SSH addons are running in a container and canβt access the host system.
This also needs to be run from debug/host console as above.
However you might be able to trigger the update using this command which will work from SSH Addon (not tested this though):
ha os import
Thanks that youβre trying to help me. It seems that βha os importβ works but after that I have some issues with the key. Probably Iβll soleve it after a few attempts. Could you give me some tips about debug console in case I would fail. For the last two years I was using HA Core on TV Box (armbian) and everything was simple using SSH. Iβm not expirienced and donβt have any expirience with debug console. Itβs obvious I have to connect ihost with USB C, but what then ? Will I connect to ihost from the windows command line or putty or winscp?
Sorry about that questions but Iβm a novice in HAOS and this problem bothers me.I promise not to harass you again.
In this case your logging into armbian which is the host!
Connect the iHost to your computer via the Type C. Once booted it will show up as a COM port. You then connect to that COM port using putty serial, Com port and baudrate 115200 ,you will get a login prompt for which user is root and no password.
Alternatively you can setup as per the link I provided above, in which case the ssh will connect to the same IP As before but on port 22222 (instead of 22)
Thanks again. Using Type C connection and after βjournalctl -b0 | grep mmcβ command I see that:
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: IDMAC supports 32-bit address mode.
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc60000.mmc: IDMAC supports 32-bit address mode.
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: Using internal DMA controller.
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: IDMAC supports 32-bit address mode.
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: Version ID is 270a
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: DW MMC controller at irq 80,32 bit host data width,256 deep fifo
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc60000.mmc: Using internal DMA controller.
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc60000.mmc: Version ID is 270a
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc60000.mmc: DW MMC controller at irq 82,32 bit host data width,256 deep fifo
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: Using internal DMA controller.
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: Version ID is 270a
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: DW MMC controller at irq 83,32 bit host data width,256 deep fifo
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc0: card is non-removable.
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: allocated mmc-pwrseq
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: card is non-removable.
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: card claims to support voltages below defined range
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc1: error -110 whilst initialising SDIO card
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: card claims to support voltages below defined range
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc1: error -110 whilst initialising SDIO card
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: card claims to support voltages below defined range
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc1: error -110 whilst initialising SDIO card
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc70000.mmc: card claims to support voltages below defined range
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc1: error -110 whilst initialising SDIO card
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: Busy; trying anyway
Jan 03 10:45:35 homeassistant kernel: mmc0: error -84 whilst initialising MMC card
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc0: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc60000.mmc: Busy; trying anyway
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc2: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: Busy; trying anyway
Jan 03 10:45:35 homeassistant kernel: mmc0: error -84 whilst initialising MMC card
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc0: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc2: new high speed SDXC card at address b36c
Jan 03 10:45:35 homeassistant kernel: mmcblk2: mmc2:b36c SDABC 58.2 GiB
Jan 03 10:45:35 homeassistant kernel: mmcblk2: p1 p2 p3 p4 p5 p6 p7 p8
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: Busy; trying anyway
Jan 03 10:45:35 homeassistant kernel: mmc0: error -84 whilst initialising MMC card
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc0: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: dwmmc_rockchip ffc50000.mmc: Busy; trying anyway
Jan 03 10:45:35 homeassistant kernel: mmc0: error -84 whilst initialising MMC card
Jan 03 10:45:37 homeassistant systemd-fsck[233]: /dev/mmcblk2p1: 7 files, 40/8167 clusters
Jan 03 10:45:38 homeassistant kernel: EXT4-fs (mmcblk2p7): mounted filesystem with ordered data mode. Quota mode: disabled.
Jan 03 10:45:41 homeassistant hassos-expand[261]: [INFO] Checking if expanding data partition on /dev/mmcblk2p8 is necessary
Jan 03 10:45:41 homeassistant hassos-expand[261]: [INFO] Detected GPT partition label on /dev/mmcblk2
Jan 03 10:45:41 homeassistant kernel: EXT4-fs (mmcblk2p8): mounted filesystem with ordered data mode. Quota mode: disabled.
Jan 03 10:45:42 homeassistant hassos-expand[336]: [INFO] Checking if expanding data partition on /dev/mmcblk2p8 is necessary
Jan 03 10:45:42 homeassistant hassos-expand[336]: [INFO] Detected GPT partition label on /dev/mmcblk2
Jan 03 10:45:42 homeassistant kernel: EXT4-fs (mmcblk2p8): resizing filesystem from 15087995 to 15087995 blocks
Thanks @dipalomeri, this is still the same issues been battling with and some people have been seeing it, but not others. I will reachout again to the eWeLink folks and see if they have any further ideas!
Jan 03 10:45:35 homeassistant kernel: mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
Jan 03 10:45:35 homeassistant kernel: mmc1: error -110 whilst initialising SDIO card
``I purchased my device in March or April last year on pre-order. Maybe they changed something in hardware since that time without informing anybody. This is typical for Chinese manufacturers. I know from my own experience that they sell the same model with a bit different hardware but it is only my suspicion.
Current stock of 4GB version is identical to the pre-order ones. the 2GB version has some minor differences on the main host board, though the wifi module is the same.
Good morning HELPPP MEEE
VUE 2 modified with ESPHOME.
same VUE2.yaml. on home assistant virtual machine works well.
on ihost modified Home assistant returns:
`- Configuring incomplete, errors occurred!
See also β/data/build/vue2-1/.pioenvs/vue2-1/CMakeFiles/CMakeOutput.logβ.
See also β/data/build/vue2-1/.pioenvs/vue2-1/CMakeFiles/CMakeError.logβ.
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Error at /data/cache/platformio/packages/tool-cmake/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message):
The C compiler
"/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /data/build/vue2-1/.pioenvs/vue2-1/CMakeFiles/CMakeTmp
Run Build Command(s):/data/cache/platformio/packages/tool-ninja/ninja cmTC_22cff && [1/2] Building C object CMakeFiles/cmTC_22cff.dir/testCCompiler.c.obj
[2/2] Linking C executable cmTC_22cff
FAILED: cmTC_22cff
: && /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc -mlongcalls -Wno-frame-address CMakeFiles/cmTC_22cff.dir/testCCompiler.c.obj -o cmTC_22cff && :
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: error loading plugin: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
/data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:298 (__project)
CMakeLists.txt:3 (project)
========================= [FAILED] Took 26.35 seconds =========================`
Seems there is an issue with the toolchain, probably not specific to iHost but armv7. There are a few similar bugs here:
Perfect
hardware update via VM
much faster (almost instant)
then I copied the βyamlβ files
My zigbbe network:
12 battery powered (SNZB02)
32 powered 5v (WZ1, ZY-M100-S_2, TS004)
ZHA holds up well, very well indeed
Z2M doesnβt work
during the join it restarts
it hooks the sensors and does not identify them well
the battery status sometimes yes, sometimes no
the wz1 does not always receive commands
I tried switching the firmware :
But nothing has changed
Do you have e any suggestions
Z2M is indispensable to me for the ZY-M100-S
Thanks
Zigbee2MQTT depends on zigbee-herdsman so probably best if you ask in this ezsp adapter issue β [WIP]: EFR32 EZSP adapter implementation and test Β· Issue #319 Β· Koenkk/zigbee-herdsman Β· GitHub
to upgrade
now
For the first time it hasnβt stopped for 60 minutes
Changed settings:
βserial baundrate :115200β filled in and not blank in the βSerialβ settings page
βHome assistant integration: simpleβ
βFront-end :simpleβ
βavailability : simpleβ
No new devices added
I only restarted Z2M
processor as always under 15%
memory as always under 20%
Do you have any further suggestions to make my configuration more stable (it works with room-by-room heating and above all anti-theft and I canβt afford frequent interruptions)
Z2M doesnt yet support for the 7.4.0 firmware unless you use the edge version. Until that is released to stable branch you should stick with 7.3.2 firmware.
I have a problem with the eth0 interface that I canβt reach, this happened unexpectedly and for no reason, I connected locally from terminal via usb port, command nmcli device eth0 ethernet connection failed Supervisor eth0
what could have happened and how can i do a system reset because i have no control over ip
Are you in the debug console there (USB-C port)?
Can you grab kernel logs.
However, I will note @clfberlin had his ihost replaced under warranty due to faulty ethernetβ¦
Have you got any tips from sonoff how to solve the problem that on some iHosts wifi doesnβt work?
yes the debug console works ok
what exactly should i grap in the kernel , do you have a specific command cli ?
Just use:
journalctl -b0 > kernel.log
Yes, ask Sonoff to replace it under warranty 
