Reactor (Multi-System/Multi-Hub) Announcements

[LibraSun]

@3rdstng said in How To: Send TCP packet in Reaction:

took my R4V backup file and imported it in

I would have loved to do the same, but with Docker running on a Synology NAS, I recall there being some [command line or required packages] limitation that made the import impossible.

That's why I laboriously re-created all of my old R4V reactions, which turned out to be the best way to learn Reactor for me!!

I was just eager to hear that [uncertain] limitation had been circumvented during the intervening year or so.

[toggledbits]

Here's a way to do it, with credit to @whyfseeguy for the approach.

It's always a good idea to back up your Reactor data directory before doing anything like this.

You can start a shell running in the Reactor docker container, and run the importer from inside the container:

1. Copy your Reactor for Vera backup file into your Reactor (MSR) data directory. This is the directory you have mapped to the container's /var/reactor when setting MSR up (it's the parent of your storage and config directories.

2. Make sure your Reactor docker container is running.

3. Open a shell in the Reactor container. This must be done from the system command line:

    docker exec -it reactor /bin/sh
   

4. Now change directory to the container's Reactor directory:

    cd /opt/reactor
   

5. Create a symbolic link:

    ln -sf /var/reactor/storage .
   

6. Now run the importer:

    node tools/import_reactor_backup.js /var/reactor/<name of your backup file> <controller-id>
   

   In the above command, the <controller-id> is the ID assigned to the VeraController in your reactor.yaml configuration file. The distribution default version of this file includes a sample configuration with the ID vera, so it should be easy to find and confirm.

7. Exit the container's shell with the simple command: exit

If anything goes horribly wrong (i.e. you get a hard error), let me know and I'll try to help you fix it. Also, for anyone who finds this procedure altogether too daunting, I'm happy to run the import for you and send you a ZIP file — contact me via DM for this request.

[LibraSun]

I feel I ought to know what <controller-id> comes from, in the instructions above, but nothing pops into my head.

[toggledbits]

I'll amend that. <controller-id> is the ID you gave the controller in your reactor.yaml file. The distribution default version of the file includes one with the ID vera, and I don't think most people would ever change it (they certainly must if they are adding multiple Veras to their configuration — each must have a unique ID).

[tunnus]

@toggledbits can’t resist saying that for most of us even a single Vera is too much

[toggledbits]

Just wait until you have a house full of little eZLO trinkets, as one big messh...

[3rdStng]

I retired one of my two VeraPlus units. It was satisfying to press the reset button 6 times to factory reset it. Does anyone want it? I wouldn't expect to get very much for it on eBay, so you cover the shipping costs and it's yours.

[LibraSun]

There is (edit: WAS) a guy on the ezlo Forums who said he was looking for a Vera unit to replace his Plus. I'll drum up the link to his post: Nope, it vanished, along with the Message I sent him on that Forum. Wonder if he got booted for talking about equipment failure, lol.

[Buxton]

@3rdstng Ha! if you're in the US, I'll take it. I still have a veralite running in my garage that could do with an upgrade.

[3rdStng]

@buxton said in Import Vera Rules in Docker Containers?:

@3rdstng Ha! if you're in the US, I'll take it. I still have a veralite running in my garage that could do with an upgrade.

I am in So Cal. I'll DM you.