👨‍💻‍【Release Note】eWeLink CUBE Version History

[JMZ]

Did someone managed to do backup and successfully restore it on 2.3.2 ?

[eerke]

I have a Zigbee map but it is full of UFO that make no sense. For instance I have a door sensor on my front door that node Red sends a notification for when it opens. That works but my front door works. Plus it’s not that far from lots of routers. Some of the floaters make sense but some don’t.

[ociepa.ekotox]

@JMZ

Did someone managed to do backup and successfully restore it on 2.3.2 ?

I installed version 2.3.2 but still can’t create a backup.

edit:
I suspect this is a Backup Space Limit bug!

[2024-10-24T23:12:49.919Z] [INFO] default -e[39m [OperationManager] - startBackupOperation backupFilesSize:17600290560 - backupSpaceSize:1610559488
e[32m[2024-10-24T23:12:49.920Z] [INFO] default -e[39m [OperationManager] - startBackupOperation backup Space Limit!

[ociepa.ekotox]

After uninstalling home assistant and homebridge, the backup was successfully made.
The backup file is 346 MB in size.
And here the question arises: what sense does this make?

The backup took 10 minutes. The pink progress bar froze at 6.38% and did not change until the end of the process.

[ward]

@teo.alex

ZigBee Map is blank, reboot, unplug, same blank. Not so important, was full of UFO(floating devices) anyways

Hey

We are still working on Zigbee map issues. You can check this post to track our current progress.

eWeLink CUBE V2.3.2 - What’s Fixed?

Hi eWeLink Community, We want to extend our apologies for the issues some of you experienced with version V2.3.0. We’ve been listening closely to your feedback and logs, and our team has been working tirelessly over the past few days to address these concerns as fast as we can. Here’s the progress till V2.3.2: What’s Fixed Reversed Color Temperature: We’ve resolved the issue with Zigbee lights, including certain IKEA models, where color temperature was inaccurately represented due to a diff…

[ysty89]

I managed to get a backup of 1.08 GB done with 2.3.2 and get it downloaded. Having homeassistant docker installed as well. If I understood it correctly these backups are stored in the internal eMMC chip. Not sure what else can there be there that would reduce your free space.

[ward]

It calculates the backup size before preceeds, which has a limit of 1.5GB

[zdy_78]

after upgrading to version 2.3.2, iHost is no longer available on ihost.local, and now you can only access it from ip 192.168… I tried to reboot the router, IHost, but it didn’t help. Does anyone know why this happened?

[yitie]

Hey, I met the same issue on my MacBook with chrome, accessing back to normal after I delete all the caches and cookies of the Chrome and reboot my Mac, then the Chrome prompts out to asking for permission of network connection when I launch it, everything works fine after ALLOW selected.

[ward]

@john.e.dixon

OK. Only presumably being a large backup it timed out and showed the “Backup Failed” error when it was still in process (15-20 minutes)

Hey

Could you please share some logs with us, we need more information to improve the experience.

Thx in advance!

[zdy_78]

It didn’t help. I tried to enter the name ihost.local in different browsers and it doesn’t work also

[ward]

How about other clients in your local network? Tablet or phone, will they resolve the domain normally (access to the WEB UI)?

[zdy_78]

I tried on android phone and tablet and on iphone. it doesn’t work also. the link to ihost.local/cast/ doesn’t work either

[john.e.dixon]

Of course. How do I send, it´s about 65mb?
DM won´t allow more than 8mb.
Tell me which method you prefer - in an hour or so I could send it.

[bajanich.e]

in version 2.3.0 and 2.3.2 there is a problem with displaying firmware versions of zigbee sensors. The zigbee socket displays the firmware version correctly. Zigbee sensors all show the inscription “unknown”.

[yitie]

If the device is not reported to iHost, there is really no way to know and display the firmware version.

[bajanich.e]

Previously, in the ihost firmware version 2.2.0, the firmware version of these sensors was displayed correctly. Basically, the firmware version of these devices was displayed as v0.5. Now it says “unknown”.

[yitie]

Yea, we developed the Zigbee2CUBE module out of beta on V2.3.0 to extend the compatibility for Zigbee devices, the biggest change is the presentation UI now based on the capabilities and data reported by the device, please refer to our explaner below for more information.

eWeLink CUBE V2.3.0 Update Explainer

Hi eWeLink Community! We know it’s been quiet for a while on the iHost and eWeLink CUBE front. But we’re back with the new V2.3.0, which introduces some important, long-awaited features. Backup and Matter hub are finally here. We want to take this opportunity to explain the details of the past one and a half months’ development. Backup and Restore Functionality: One of the most significant additions in V2.3.0 is the ability to back up and restore iHost settings. This includes a wide range of …

[mario.bianchi]

Hi, updated to 2.3.2 and still see disrepancies with the RGB color picker. I am using ZLD-RCW Zigbee RGB controller from MOES Moes RGB+CCT LED Controller 12-24V ZLD-RCW Zigbee compatibility

Basically can not choose pure colors (like red, green or blue), all colors show washed. Instead of pure red, I got pink.

When picking color in the right lower corner of the picker this is what I get in nodered as status:

{“power”:{“powerState”:“on”,“updated_at”:1729851219198},“color-temperature”:{“colorTemperature”:52,“updated_at”:1729851220737},“color-rgb”:{“red”:255,“green”:28,“blue”:70,“updated_at”:1729851226665},“brightness”:{“brightness”:100,“updated_at”:1729851220355}}

[yitie]

Thanks for feedback, it’s a known issue we are working on, check the release explainer for V2.3.2 here,

@ward

Wrong color mapping for RGB lights: We’ve received several cases on this issue, but have yet to restore the behavior or find any useful information from collected logs. Our dev team is on it and will keep you posted with any updates.