Backup and more 'importantly' restore

Morning, chap.

So having migration to Openluup and it’s all going well.

I’m hitting something like an issue with my understanding of Reactor restore:
Currently openluup running verabridge. All my existing reactor instances are there, present and correct, but of course not working due to the device numbers changing. As expected.

I can (and have) installed a Reactor master locally on the Openluup machine. I’ve created a backup of the Vera Reactor instances, and that’s available to restore.

But I can’t restore to a ‘new’ sensor? As soon as I try it wants to overwrite the existing device ID.

What are my options here? Delete the Sensor instance on Vera (which I assume will delete it on Oepnluup) then restore on the local Openluup host? Then fix the numbers?

Cheers

C

As ever, thinking out loud :slight_smile: I tried it with one of my basically never used Reactors, and it seems to work, but I never get to ‘Done’ from the Backup / Restore tab. Currently elapsed 5 minutes to restore two conditions and an action?

No we end up with some really odd configuration

Even if I change the activity the newly restored Reactor instance is meant to do, it does the new activity and the original activity somehow.

I can’t for the life of me work out how that happens.

The only way I could prevent it was to delete the newly restored Reactor instance from the Openluup host.

Just tried again. Created a new, blank reactor sensor on the Openluup host. Moved it to the correct room with the correct name. Hit restore for that instance. Never get a ‘done’ notification

Here’s the Openluup log

2020-06-22 11:56:32.946   luup_log:11: Reactor START-UP!
2020-06-22 11:56:32.968   luup_log:11: Reactor: Plugin version "3.6" starting on #11 ("Reactor")
2020-06-22 11:56:32.969   luup_log:11: Reactor: Checking required packages for openLuup
2020-06-22 11:56:32.969   luup_log:11: Reactor: Detected openLuup (2)
2020-06-22 11:56:32.969   luup_log:11: Reactor: Can't check Lua interpreter version, returned version string is "Lua 5.1"
2020-06-22 11:56:32.969   luup_log:11: Reactor: Detected ALTUI (3)
2020-06-22 11:56:32.970   luup_log:11: Reactor: Starting ReactorSensors
2020-06-22 11:56:32.971   luup_log:11: Reactor: Starting "Chris Keyfob Reactor" (#13)
2020-06-22 11:57:02.476   luup_log:11: Reactor: GetStatus action failed for #13; rc=501, ra={  }
2020-06-22 11:57:02.476   luup_log:11: Reactor: "Chris Keyfob Reactor" (#13) tick failed: "./dkjson.lua:693: bad argument #2 to 'pegmatch' (string expected, got nil)"
2020-06-22 11:57:02.477   luup_log:11: stack traceback:
	./L_Reactor.lua:5761: in function <./L_Reactor.lua:5757>
	[C]: in function 'pegmatch'
	./dkjson.lua:693: in function 'decode'
	./L_Reactor.lua:4828: in function <./L_Reactor.lua:4809>
	(tail call): ?
	[C]: in function 'xpcall'
	./L_Reactor.lua:5755: in function <./L_Reactor.lua:5728>
	[C]: in function 'pcall'
	./openLuup/scheduler.lua:191: in function 'context_switch'
	./openLuup/scheduler.lua:656: in function 'luup_callbacks'
	./openLuup/scheduler.lua:679: in function 'start'
	openLuup/init.lua:303: in main chunk
	[C]: ?
2020-06-22 11:57:48.136   luup_log:11: Reactor: StopScene action, scene "0"
2020-06-22 11:57:48.146   luup_log:11: Reactor: 13 (#"Chris Keyfob Reactor") configuration change, updating!
2020-06-22 11:57:48.146   luup_log:11: Reactor: Backing up "Chris Keyfob Reactor" (#13) pre-upgrade configuration to "./reactor-dev13-config-v19082-backup.json"
2020-06-22 11:57:48.146   luup_log:11: Reactor: "Chris Keyfob Reactor" (13) condition "condlbwrttb" refers to device 226 ("Keyfob"), does not exist, skipped
2020-06-22 11:57:48.147   luup_log:11: Reactor: "Chris Keyfob Reactor" (13) condition "condlbwsa24" refers to device 226 ("Keyfob"), does not exist, skipped

C

Install the stable brach release of Reactor. Then go to the Tools tab of your RS’s. There will be a list of missing devices and you can make reassignments there. Let me know how that goes; it’s a new tool.

1 Like

On he instances that I’m restoring, or the ‘Vera’ instance?

Cheers

C

Restored instance on openLuup. Also the GetStatus error is irrelevant and unrelated.

1 Like

And the lack of ‘done’ notification on the restore?

Cheers

C

May be fixed in stable. Let me know.

1 Like

Probably user error, but this seems to do nothing when asked to restore.

So I went to More > Plugins
typed stable in the box, hit update
Luup relaoded
cmd-R gave me github.stable on the plugins page for Reactor
Into my Openluup Reactor device. Create a new empty sensor. Rename it, moved it to the correct room.
Then back to the Reactor. Backup / Restore tab. Restore that single sensor to same name
Sits there spinning.
After 5 minutes I reload luup, and cmd-R to go to the devices. No change to the sensor at all. Just empty

This is all I can see in the logs
2020-06-22 13:28:40.900   luup_log:11: Reactor START-UP!
2020-06-22 13:28:40.922   luup_log:11: Reactor: Plugin version "3.7develop-20169" starting on #11 ("Reactor")
2020-06-22 13:28:40.922   luup_log:11: Reactor: Checking required packages for openLuup
2020-06-22 13:28:40.923   luup_log:11: Reactor: Detected openLuup (2)
2020-06-22 13:28:40.923   luup_log:11: Reactor: Can't check Lua interpreter version, returned version string is "Lua 5.1"
2020-06-22 13:28:40.923   luup_log:11: Reactor: Detected ALTUI (3)
2020-06-22 13:28:40.924   luup_log:11: Reactor: Starting ReactorSensors
2020-06-22 13:28:40.924   luup_log:11: Reactor: Starting "Catman Keyfob Reactor" (#15)

Cheers

C

@rigpapa, Just updated to stable and restored the last of my reactors on vera to OpenLuup. The new tool for renaming missing devices worked like a charm. Thank you

1 Like

Like I said, User error :slight_smile:

I think there’s something very odd about these keyfobs on Openluup though. I’m not touching the fob…

2020-06-22 14:17:48.358   luup.variable_set:: 10238.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 4 now: 4 #hooks:0
2020-06-22 14:19:29.972   luup.variable_set:: 10238.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 4 now: 4 #hooks:0
2020-06-22 14:21:11.559   luup.variable_set:: 10238.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 4 now: 4 #hooks:0
2020-06-22 14:22:53.595   luup.variable_set:: 10238.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 4 now: 4 #hooks:0
2020-06-22 14:24:35.115   luup.variable_set:: 10238.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 4 now: 4 #hooks:0
2020-06-22 14:26:16.532   luup.variable_set:: 10238.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 4 now: 4 #hooks:0

C

The sl_ variables are special in Luup. They are the only variables that, when written with the same value they already have, actually get updated (timestamp changes) and send notifications (watches on variable/service are triggered). This was, I believe, a fairly recent revelation for @akbooer, and there may still be interactions between the Vera and the actual device and the bridge that need to be examined.

OK, just tried another one, and this time it worked fine. But looking at the sl_variables for the other pads, I see the same update every 40 seconds.

I assumed it’s the bridge. Thanks Patrick, I think (despite ‘done’) it’s probably working fine.

Not sure where this leaves me migration though. At a guess I’m going to have to unpair and repair those devices at the least to get a working config before the big bang.

Thanks again!

C

So still no “done” when restoring on openLuup? Is that the report?

Umm yes, now :wink:

I just watch the logs and make a call…

Yes, so I just did another one sensor that has no scene controllers on it, and it worked perfectly, with the repair option and everything!

C

OK. Just updated stable branch. There’s some weird bug in ALTUI, not worth chasing as unlikely to be a problem for others and the workaround is easy (same bug manifested in 3.6 save function and was worked around then/there).

1 Like

I just updated on mine.

Still didn’t tell me ‘Done’ :smiley:
C

Hard refresh your browser?

1 Like

Sure I did but will try again with the next one!

C

Hmmm… sorry… apparently merged but forgot to push. It’s up there now. --Patrick

You should see timestamp 20174 on the version/footer.

1 Like

Instantly ‘Succeeded’

Thanks

C

1 Like

Best Home Automation shopping experience. Shop at getvera!

© 2020 Vera Control Ltd., All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules