Gradually turn on lights.

[RHCPNG]

Thanks, I'll try it. Didn't find the post when I searched for it.

[RHCPNG]

@toggledbits said in Home assistant addon: Import Vera/Openluup backup:

Please read: https://smarthome.community/post/10340

I can confirm that these instructions work for docker.

This is however not a solution for the HA addon.

@mrw298 Can you take a look at what's necessary to provide the import feature for the addon, please?

[RHCPNG]

@toggledbits said in Home assistant addon: Import Vera/Openluup backup:

Please read: https://smarthome.community/post/10340

@toggledbits Should these instructions still work? I did this successfully earlier, but I started over with a new docker container and now I can't get it to work.

I'm getting an error on the symlink creation:

"/bin/sh: /usr/bin/ln -sf: not found"

but "ln --help" works, so I guess it's not a PATH issue.

The node command doesn't work without the symlink. I'm getting this:

/opt/reactor # node tools/import_reactor_backup.js /var/reactor/20230318-reactor-config-backup.json openluup
Usage: /usr/local/bin/node /opt/reactor/tools/import_reactor_backup.js /var/reactor/20230318-reactor-config-backup.json openluup <reactor-backup-file> <controller-id>

Newer docker version now than last time: latest-23078-d592d400

[toggledbits]

The instructions linked say to use ln -sf not /usr/bin/ln -sf

[RHCPNG]

Yes, I know. Tried that first, of course. This was to check if it was a PATH issue.

[RHCPNG]

Can someone please check if the symbolic link command (ln) still works in the latest docker? I want to know if it's a problem with my container or in the image.

[toggledbits]

You never posted the original command (the one the instructions gave you), and the error message you got from it. You've only posted an experiment that you tried after, which isn't really relevant. Post the original ln command that's not working, and the output/error it generated.

[RHCPNG]

@toggledbits said in Home assistant addon: Import Vera/Openluup backup:

You never posted the original command (the one the instructions gave you), and the error message you got from it. You've only posted an experiment that you tried after, which isn't really relevant. Post the original ln command that's not working, and the output/error it generated.

That's because it is the same error, namely:

/opt/reactor # ln -sf /var/reactor/storage .
/bin/sh: ln -sf: not found

[toggledbits]

Odd. You're using only a space after the ln and before the -sf, right? It seems like it's not seeing the difference between the command and its argument, not separating the two, but in your prior post, the node command did interpret correctly.

Here's what it looks like in a container of mine:

pi@rpi4-1:~/Documents/docker $ docker exec -t -i reactor /bin/sh
/opt/reactor # ls
COPYRIGHT     LICENSE.md    app.sh        client        dashboard     docs          node_modules  reactorui     tools
INSTALL.md    app.js        buildstamp    common        dist-config   locales       package.json  server
/opt/reactor # ln -sf /var/reactor/storage .
/opt/reactor # node tools/import_reactor_backup.js
Usage: /usr/local/bin/node /opt/reactor/tools/import_reactor_backup.js <reactor-backup-file> <controller-id>
/opt/reactor #

No issues. Everything as expected.

[RHCPNG]

Pff, solved. It was a copy/paste issue of some sorts. I removed the space and typed it again and now it works. Thanks for the help!