If a complete backup/restore function is complicated, as has been commented various times, meanwhile at least a way of saving scenes is necessary if users want to use the iHost with confidence.
Is there no way that scenes could be exported (JSON format?) and saved?
This is the problem that arrived together with the first iHost on Earth. Is there any sense in bringing back the backup question again and again? The eWeLink team expressed its point of view numerous times. Most recently about two days ago:
We are still exploring and trying to find a good solution for backups, but for now, it’s not ready.
You need to be patient and wait or switch to HA and make backups as often as you wish.
I think you should go and pay for something else if you’re not entirely satisfied. I did.
The easiest way to circumvent this limitation until it is implemented would be to use the Node Red for your automations. and with that it creates a stream of Beckup.
At least what I do. I must have simple scenes straight on iHost the complex ones are all on the node-red
Browsed over this a few days ago and didn’t pay much attention. Then attempted to upgrade my ihost to newer release. It never came back online. I lost all my scenes. I recreated everything in ewelink for now trying to decide if it is even worth starting over with ihost.
Agreed, I do that with Node-red in the same way.
But there are many examples of simple routines that are just too tedious to create in Node-red. I have many like that in Smartthings, over 120 - I wouldn’t think of changing those to iHost unless I had some form of backup.
I moved all my scenes to Node Red over a couple of weeks except one. The Zigbee plug turning my internet router back on seemed to work better on the iHost itself. Creating which type of scene is quicker on the iHost - I may have discovered a quicker way in those two weeks of replicating scenes.