Well I did it, I put enough devices on my Vera Secure that it’s starting to get angry at me.
I’ve needed to move over to a more robust platform for a while so I can integrate other devices into my stuff, but still love and cherish my Vera and its mighty Z Wave network.
My first step is to move all of my Reactors (I have 40 running some pretty complex logic) to the Pi. I’m set up. I’ve done a couple of test Reactors on the Pi to make sure I’m doing it right. I’m now READY to make the leap. Is there any good way to copy them all over without having to add each one individually to the Pi? I’m comfortable with SSH and transfers and text editing, but clueless as to how Reactor stores its child device data and logic. Is it in separate files that I can edit directly?
When AltUI controls a remote Vera, it assigns the devices on the remote box a large device number plus a small number that is identical to the remote ID. I’m hoping that I can just replace the old short device numbers in the old reactor files with the new ones with the big Vera addendum and it just works.
Probably really naive, but wanting to save time here. Any advice anyone?
That’s only got me partway, but I’m working on editing the JSON directly with the new device numbers so I don’t have to restore then edit a bunch of reactors with the new device numbers. I’ll post details here if that works out.
That should be pretty easy. I think I’m pretty consistent using the device key in the structure. You can ignore any device names–they are just informational and will be updated from the device number when it matches a real device.
OK. I now have an experimental “Device Repair” tool implemented in the stable branch version of the ReactorSensor UI. It detects broken and suspect device assignments and lets you replace those assignments with another device.
Open the Luup uploader at Apps > Develop apps > Luup files in your Vera web UI.
Turn off the “Reload Luup” checkbox (we don’t need a reload for this).
Drag the downloaded file from wherever you saved it to the “Upload” button in the UI.
Critical step: hard-refresh your browser. The new code will not load unless you do this, it will keep using the old/cached code.
For openLuup, just copy the downloaded file to your openLuup directory over the existing file of the same name. Then do just step 5 (hard refresh) from above (yes, ALTUI needs it, too — it’s a JavaScript thing).
The “Device Repair” section will only show up in the Tools tab if a problem is detected. Otherwise, it’s not visible.
When visible, it will list the problem/suspect devices. You can choose a replacement device from the menu on the same line. Click “Apply and Save” to save the replacement assignments. It fixes the references in all conditions and activities. It does not fix Expressions (including getstate()) — you’ll need to do these manually. If you have a large number of devices, you can do them a few at a time. It will flag devices where it may be the correct device, but the device name has changed since the last time the ReactorSensor configuration was edited. In this case, there will be a menu selection to allow you to just update the stored last-known name in the RS config without changing devices.
MAKE SURE YOU HAVE BACKUPS BEFORE YOU GO CHANGING THINGS!
FYI, this code includes all the hotfixes made on the UI to date as well. Any problems, I’m here to deal with them.
Best Home Automation shopping experience. Shop at Ezlo!