After a long time I’ve finally got round to installing 4.3. I’ve been running 2.5.1 for ages and was absolutely satisfied with it, until I managed to delete the docker container it was running in.
I’m doing a clean install of 4.3 on a Synology Docker container and the installation hangs at the add in stage.
I select the 6 recommended add-ons and then the installing add-on window appears and then nothing. No error message and nothing is installed.
I’m running a Synology NAS DS720+ with DSM version 7.2.2, everything is up to date.
I’ve renamed the old parent folder containing the conf, addons and userdata folders so it’s effectively a clean install from new.
PS. I used the script from Marius Hosting here as I’m not that technical!
If it’s something to do with Java (which seems to be one of the addons that is suggested to be installed) then a simple explanation of what I need to look for would be appreciated.
I’ve got Home Assistant working in another Docker container and really don’t want to have to switch to that as I’m so familiar with OpenHab, and I love Habpanel (which I’m sure you’re going to tell me is outdated given the new UI).
There isn’t any reason why it should be hanging on installing add-ons. Do you see anything relevant in the logs?
I wouldn’t say it’s outdated so much as it hasn’t been updated. But it’s still supported so there’s no need to jump in the immediate future. Though MainUI is more capable and under more active development so a move eventually would probably be a good idea.
I’ve been looking at the container settings and comparing to a working (earlier release) of OpenHab and see that where Marius hosting suggests using root as the user in the script that the working container (with a v3 release of Openhab) shows host as the user. I can’t select host in the user-defined script set-up so not sure here.
Also I’m running Pi-Hole on my network so disabled that to see if that was somehow blocking the container but that doesn’t help.
Feeling quite stuck here
Think I’ll contact Marius as my next step given it’s his script and instructions I’m following.
Yes, and if you are not that technical, adding dealing with the complexities imposed by running on Synology on top of the complexities of using Docker may not be the best choice of deployment.