Are we going to see a version 13.3.4, or 13.4, or even 14 soon and if so when may it be?
Iâm conscious that China has been enjoying the holidays but for the rest of the world that are stuck with useless iHosts, we are desperately awaiting a working platform.
Please donât keep us waiting much longer!
Get yourself Home Assistant on a stick and youâll be fine 
What do you mean by âon a stickâ?
Does sonoff (not tasmota) also work with home assistant?
Yes, Sonoff devices are supported in various ways, officially by eWeLink and by the community. This support is with minor restrictions. In many cases Sonoff devices are supported much better, especially Zigbee ones.
There is an excellent Home Assistant custom component for control Sonoff devices with original firmware over LAN and/or Cloud. Official support is also available, but as in case of iHost and CAST it is⊠well, you know 
I installed cube v1.13.4 and Paral-sync (v1.1.1) updates.
In node-red I made updates (node-red-contrib-ewelink-cube
v1.2.0).
NODE-RED displays a message that the NSPANEL PRO IP is incorrect.
Update 1.13.4 has broken the iHost. None of my 38 devices are connected and the donât work.
Sorry for the inconvenience.
Please submit your system log in here or via feedback.
Weâll pinpoint whatâs wrong.
ticket with ID203344
Hey,
We will release a new patch to the Node-Red extension to fix this issue ASAP
It is a never-ending story of stumbles and falls 
Meanwhile, the situation with Sonoff on Home Assistant looks like this. Everything works as expected despite the latest series of updates. Yesterday I moved the system from the SD card to the NVME drive and it works too.
Sonoff integration looks like this: WiFi in LAN and/or cloud mode and Zigbee directly with ZHA. The exceptions are TRVZBâs and NSPanel Pro. Overall, Sonoff is covered in Home Assistant surprisingly well.
Hi, ociepa.
The problem is fixed.
Please update the package node-red-contrib-ewelink-cube to v1.2.1.
After the last update 1.13.4, WhatsApp functions no longer work for me in Nodered. I installed the latest update of nodered: NODE_VERSION=16.20.0
YARN_VERSION=1.22.19
And restart the node Red docker. I made the mistake of just updating the palette but for it to take hold you have to restart too. I thought it was broken till I restarted the docker.
Is it safe to install this update 1.13.4 ???
My backup electric heating system is running on my iHost and I donât want any troubles with it.
I use auto and manual scenes + 2x TH Elite Smart Temperature and Humidity Monitoring Switch
after restarting node red in docker it still doesnât work
My Node Red and the updated TRV controls works, but I donât use WhatsApp. Maybe it is a problem between WhatsApp and the developer of the Whatsaop Nodes - I have given up on quite a few nodes. Usually time has passed since the guide you followed was published and there is a collection of Nodes that have been updated more recently. Iâve noticed quite a few NR updates in Home Assistant OS lately, but I donât think there have been so many to this docker version. Maybe this node has just been broken by a Node Red update.
As well as confirming my NR works I can say my notification system works (Pushover) although Iâm fairly sure I donât use the nodes that appear on their website because they are ancient.
it worked until i updated 1.13.4. installed, then it stopped working. So the problem is the sonoff software, not node red or whatsapp nodes.
Iâm waiting for my SD cards, then Home Assistant will start on a Rapberry Pi. I get the feeling that with the ihost updates you first go 4 steps back and then 2 steps forward.
