I strongly believe, a backup function would be helpful. At the moment I have the feeling I cannot trust the device with more complex configurations and/or docker containers. Being able to restore configurations would considerably boost my confidence and trust in the system.
I am 100% in favor!
100% in favor!
Yea, I would also like the option to move eWeLink scenes locally and not rewrite them all. Maybe they could have a toggle to move to LAN on the eWeLink app. Then you would have a copy of the scenes in eWeLink too.
The other thing I would like saving is rooms. I do not know why they are not copied between eWeLink and iHost. It’s not like the host will get new rooms when we buy an iHost.
Docker images I think could be copied by putting the card in a Linux machine.
Backup and storage of system and user configurations are planned, but the current technical solution has not been finalized. The backup function of the system is expected to be supported by the end of the year at the earliest.
This is not good news if the user has a large number of devices at home, it is not an easy job to apply everything to iHost.
For example, a small error on the SD card is enough and the creation of the home “ecosystem” can start again and again. As I already wrote somewhere, I myself have around a hundred of these devices.
I can’t make iHost a dominant device without a backup option.
Hi Rossi14, I understand your concern.
We are currently focusing on making iHost more stable, especially when working with all kinds of TF cards. You know backup and restore can also be boring if the system itself is not stable enough.
Backup is definitely on our plan, and we are working hard to implement it as earlier as possible.
Yes, I understand … that was just a sigh, you can’t expect “miracles” from a new thing immediately after its release. ::
What I can recommend in the meantime is setting up a docker with iobroker and using that for automation. Unlike Home Assistant iobroker can restore backups from sources like FTP, NAS or dropbox. Just make sure to backup and store those files regularly. If something goes wrong, you can crate a new container and restore your configuration.
Thanks for the advice, do you mean this?
I have buanet/iobroker running.
That ist the one I have been using for quite a while in Docker (on a Synology NAS). I now have it running as a test installation on iHost. In comparison zu Home Assistant (homeassistant/armv7-homeassistant). The main thing is that you cannot upload files from your PC into the Docker installation. iobroker offers other possibilities, though (FTP, Dropbox etc.)
Thank you for the information !
Perhaps if we had SSH access as root we could make a full backup of the entire filesystem.
Why isn’t it possible to do something like with the Raspberry 3(b):
Make a reference on the TF card, and store everything on a USB SSD.
It should be possible (in this case, because the OS runs internally) to be able to choose between TF storage and USB/SSD storage.
If something like this is not implemented the iHost is doomed to fail(!!!), unless some “hacker” makes it possible.
Until something better comes along, it is possible to backup Node-RED flows by exporting them to the clipboard and pasting them into an editor on the system running your browser. Saving from the editor to a file with a .json extension should make it possible to import the flow later. Not ideal, but it is protection agains TF card failure or corruption.
A slightly neater way to backup Node-RED flows from inside NR is to email the
/data/flows.json file to yourself. I have been sending the file contents in the body of the email, but it should be possible (better) to send the file as an attachment.