👨‍💻‍【Release Note】eWeLink CUBE V2.5.1 Update

Ladies and Gentlemen, please maintain an appropriate level of discussion even when we disagree. :slight_smile: Thx

1 Like

Oh no, I respect you so very much that I hold your opinion very highly and am deeply upset by your comment. So upset I might cry.

Thank you and good night.

Good morning and happy new year soon

even today I wanted to try a new product on IHOST;

uff connects it but can’t configure and manage it.

Such a pity.

If you google the device you have and Zigbee2MQTT is it supported? (I am assuming it is Zigbee).
I know for sure the MQTT broker can be run in a docker image as I have this.
I know for certain that Zigbee2MQTT can be run inside a docker image.
I know for certain there is a USB port on the back of the iHost and USB Zigbee dongles exist.
I’m pretty sure Zigbee2MQTT can be controlled from nodes in Node Red on the Host. I know for certain they exist but haven’t tested them yet.
What I don’t know is if Zigbee2MQTT running in a docker could access a USB Zigbee Dongle. Maybe someone at Sonoff has tried?

It may be that you can just connect to the device you have just by buying a cheap USB Zigbee dongle.

IHOST sees it, it’s zigbee but then the control panel is reduced to just this:

immagine

Can you google the name and Zigbee2MQTT?
This website is useful for checking compatibility although it has other stuff like ZHA and tasmota.

You could possibly get ZHA to work but it’d be more hassle.

1 Like

THIS IS ANOTHER BOMB UPDATE.

When I updated to v1.13 all my matter devices desappiear.
I can´t see them on matter list., I can´t control them on Google Home.
I’m going to have useless home automation for another month.

Please, implement the roll back function or do more testing before make the release.

I want to install the version v1.12. again.

2 Likes

The last reasonably working version is 1.11.0. Unfortunately, reverting to earlier versions is not supported. Firmware images are not publicly available, at least not officially. Patience is recommended. The dudes at eWeLink got so much feedback that I’m sure they’ll come up with something. I’d bet a good beer that they’ll publish something as soon as early January. The question is whether it will be something radically bugfixing or a sequel to version 1.12.x.

For me he version 1.12.0 was good too, the matter devices was working very nice.

I know that reverting is not possible, that is why I am asking for ir. The config interface should have a checkbox to select the version to install. If the last version was bad, we could choose the version what we want, without make it public.
That is the problem, they send a bomb update and take a long time to make the bugfix (or not, because the software testing is missing).

Have you sent any feedback from your iHost?

ZigBee:

The ZigBee map is a mess.
-End-Devices go offline or even disappear even if they are close to other Router devices (snzb-03 & snzb-02 & snzb-04).
-The only stable devices are those directly connected to iHost.

Docker:
-Deleting the onzu and tailscale containers doesn’t work. They reappear after a reboot.
-Node-Red isn’t stable; after a few days, it simply stops doing what it’s supposed to do, and automations freeze. I can’t find a way to restart the node-red container once a day…

Matter Bridge:
-Can’t be deactivated, I’m not using it…yet.
-Association requests keep popping up repeatedly on phones in the house.

DNS:
-Sometimes the ihost.local domain doesn’t work; it needs to be accessed via IP address.

And the list goes on. I have a big hammer that I think will fix this iHost. It’s not a help in home, sometimes, it’s the opposite.


after update to 1.13.0 Zigbee map not work moust time

HI
I’m sorry, after the update it still works well, aesthetically a little less but it’s not important

Question: why, when pressing the right button (closed), does the shutter not close?

If I click the left button (open), it closes instead.

I wonder if the icon on the picture is reversed or if I need to modify the device?"

Same issue in the cast section.

What does your question have to do with the topic of this thread? Why create mess and confusion?

massimo, you have few sensors there and they are closer to iHost then routers…
In your case there is no need for a mesh zigbee network. Try to expand your ZB network and the troubles will apear…100%, and you will see that your post is irelevant to problems listed here… have a good year…

I would say it’s relevant since we’re on the latest version, and it receives commands in reverse, so it doesn’t work.

Hello,

The other day, I updated to version 13, and after the restart, I saw all the devices on Alexa and Net Hub except those with multiple channels. Oh well.

So, I made up my mind, and today I did some work on the electrical system. Consequently, I turned off the entire network: IHOST, Alexa, Net Hub, Switch, well, everything, and crossed my fingers.

The system remained off for over 2 hours. When I turned it back on, great disappointment: Alexa couldn’t see any devices, and the same for Net Hub.

I checked both the Alexa app and the Google Home app, and the devices were present, but they wouldn’t communicate in any way with IHOST.

What do you think I had to do: disconnect and reconnect each device, a real hassle.

With this, Happy New Year to everyone, and let’s hope for a better start.

I recommend letting it go as it is and wait patiently. Soon the new version will be released. Hopefully it will cure the situation. You can live without home automation. People have managed to do this for the last few thousand years and - perhaps - they were happier :sunglasses:

Love and Peace for a New Year.

1 Like