All right, we’ll wait for your backup file.
I can’t perform a backup. There’s an error.
We’ve received the logs and will begin our investigation immediately.
We’ve identified the root cause: the backup file is too large, and the available storage space on the iHost is insufficient, which leads to the backup failure.
Your current backup size is 1.57 GB, while the iHost reserves 1.5 GB for backup files. This size mismatch is what caused the failure.
There are two possible solutions:
-
Skip backing up Add-on persistent data.
Add-on data usually occupies the most space, and since your issue is unlikely related to any Add-on, you can generate a backup that includes only the iHost data. This should keep the backup size within the allowed limit. -
Manually delete persistent data from large Add-ons
Identify and remove persistent data from Add-ons that you believe consume excessive space. Reducing the Add-on footprint will allow the backup to complete successfully.
We recommend trying Solution 1 first. If that doesn’t work, then use Solution 2 as a fallback.
Additional Note:
Are you using the Node-RED Add-on?
We’ve encountered cases where devices synchronized through Node-RED caused the Matter Bridge to crash. If possible, try deleting any devices synchronized through Node-RED, then restart your iHost to see whether that resolves the issue.
How do I do this? There is no option to select the type of data to be backed up.
Sorry, I misread the situation. iHost backups do not actually support skipping Add-on data.
You can avoid backing up Add-on data by powering off the iHost, removing the TF card, and then booting the iHost without it.
After that, perform the backup. Once the backup is complete, power off the device again and reinsert the TF card.
1 Like
I removed the virtual devices from node-red. The error still persists.
After removing the memory card from ihost. Most matter bridge is now online 
Ticket #ID256953, I have approved access to my log.
I know you are already working with @ociepa.ekotox but if I can be of additional assistance, let me know. I will have sporadic ability to return to this throughout the day.
We’ve received the backup file.
We were quite surprised to see that the Matter Bridge started working normally again after you removed the TF card.
Could you please provide the latest system logs once more, along with the exact time when you rebooted the device after removing the TF card? This will help us understand what happened during that period.
Of course. If we have any additional requirements, we will reach out to you for further details.
Thank you for your generous help.
1 Like
The problem has resurfaced. The ihost is still without a memory card.
Before the 2.8 update I had the iHost, and a Moes Matter hub, both bridging to SmartThings and HomeKit without any issues. After the update, the iHost lost several devices (motion sensors sold as eWeLink-compatible), and I’ve had to move them to the other bridge. This seems to be the result of the update removing the iHost’s ability to expose them through the Matter bridge.
The more serious issue—one I waited on through reboots and retries to see if it would resolve—is with virtual devices. Any virtual switch, contact sensor, etc. created through the Node-RED add-on (using the exact same configuration as before) no longer appears in the Matter bridge. On the iHost they now show:
“The following devices are not supported to be added to Matter-supported platforms yet.”
Older virtual devices still work, but new ones cannot be bridged, which for me is a far bigger limitation than the loss of the physical devices.
EDIT Ticket 257309
Sometimes I have to refresh the page because iHost doesn’t do that.
I have the same problem as you. But yesterday afternoon the devices were working for a while through Matter. I didn’t remove the memory card, but it did work for a few hours.
I think you’ll add heating control.
Do you mean that after removing the TF card, the Matter Bridge only worked briefly and has now become unstable again?
Exactly
It worked for me yesterday for a short time (2 hours) and has stopped working again. I didn’t remove the SD card.
I have had this same problem since iHost Cube software release v2.6.1 reported with Ticket ID 249787 which is outstanding and not been resolved— the warning will eventually disappear after iHost has been on for a while. Please can we have a resolution to the ticket.- Thank you.
Understood. We’ll investigate and work on resolving the issue.