iHost bugs

Hello, after the release of the new update of eWeLink Smart Home Add-on for iHost, autobackup in iHost is not working.

After updating the smart home addons, it is not possible to change the name of the found devices during pairing with a zigbee device. If you try to rename them, it returns the original device name.

The red circle indicates objects that cannot be renamed during the search and pairing of a Zigbee device. It always returns the original device name.

Please send us your system log and eWeLink Smart Home Add-on log via DM or feedback.

We’ll look into it ASAP.

Do you have instructions or where can we find them?

You can find the system log and download it in the settings page.

If the issue with renaming the device persists, could you please provide a video of the process? This would help us better understand the problem

I’ve noticed the naming new Zigbee devices bug too. If you assign them to a room and then go to settings on the device you can still name them though.

I am send log file to your fedback.

Manual backup working corect and autobackup failed again.

I am send log file s on your feedback

Just replicated the naming problem. Here is the video link:

Yes this is main problem in iHost.

Thank you very much for reporting, we will look into it ASAP.

1 Like

Auto refresh in CAST from iHost sometimes it doesn’t refresh. As you can see in the video, the second device has been turned off for a long time but shows that it is on.

You have the wrong list of time zones. I am from Slovakia and here it is UTC+1, in ihost it is UTC+2

Aren’t you in DST (Daylight Saving Time) now? According to Wikipedia, Time zone for Slovakia in DST is UTC+2 (CEST). The DST will end on Oct 26th, right?

I understand now it divides it into summer and winter time. then it’s okay now we are in summer time. You have right.

in the UK it is this sunday 0100 that summer time ends.

Thank you for your feedback. We have identified the cause of the issue preventing device renaming, and it will be fixed in the version released at the beginning of next month.

Thank you for sharing the video. We have identified the cause of the issue preventing device renaming, and it will be resolved in the update scheduled for early next month.

Do you fix the isue with autobackup?