Moving MSR from a QNAP container to RP 5 - some issues

[apocalypsehobby]

Hey crew,
I'm running into an issue where MSR's reactions aren't successfully running, and I can't figure out what's gone wrong.

Backstory-- we had a big thunderstorm roll through the other day, we lost internet and the storm got bad so I unplugged most items in my homelab, including the Pi that's running MSR.

Now that everything is powered back up, the reactions aren't running correctly. Most of my MSR automations are to use motion sensors to turn lights on/off, and I immediately noticed that even when a motion sensor is tripped, the light doesn't turn on like it's supposed to.

I've tested a bunch of things to see what's broken, here's what I've observed:
-I can successfully flip lights on/off manually within Vera
-I can successfully flip lights on/off manually within MSR's Entities section
-the motion motion sensors are correctly reporting to Vera and MSR (I can see when they're sensing motion)
-the rules within MSR are working correctly, I can see when they flip to 'true' when I walk by a motion sensor
-I can successfully run the Reaction within MSR (by hitting the 'play' button)

But for whatever reason, when everything needs to work together, it doesn't successfully run the action. IE: the motion sensor trips, reports it to MSR, I can see MSR going "true" but the light does not turn on. Open to any suggestions, thank you!

SYSTEM
Vera has all my devices
MSR is running bare metal on Rpi "Reactor (Multi-hub) stable-22004-6d6c6b7"

[SweetGenius]

I don't know what would of broke but that appears to be an old build. Have you thought about upgrading to the newest version? Is there anything in the Logs to give you a clue?

[apocalypsehobby]

@sweetgenius yeah I should— I can probably do that tomorrow.

[Edwin1972]

I had the same problem. After upgrade to new version the problem is solved

[apocalypsehobby]

Of course, that fixed it. Thank you both!

[Motsie]

Hi Guys,
I Have exact the same problem.

My story is that I got a new ISP modem, I corrected everything, set all the IP addresses to the same numbers as before. Restarted all the Home Automation hardware and still no clue.
System: MSR in docker container on Synology NAS, Vera PLus Zwave with all devices and a Home Assistant for some extra information.

The reactions aren't running correctly. Most of my MSR automations are to use motion sensors to turn lights on/off, and time based automations nothing worked where MSR does his magic.

I've also tested a bunch of things to see what's broken, here's what I've observed:
-I can successfully flip lights on/off manually within Vera
-I can successfully flip lights on/off manually within MSR's Entities section
-the motion motion sensors are correctly reporting to Vera and MSR (I can see when they're sensing motion)
-the rules within MSR are working correctly, I can see when they flip to 'true' when I walk by a motion sensor

But I cannot successfully run the "Set Reaction" and "Reset Reaction" within MSR (by hitting the 'play' button)
But the play buttons on the action in the "Set Reaction" and in "Reset Reaction" they work well.

Lastly I updated the Docker Container as you all suggested.

But on my system nothing changes.
Any ideas?

[christian_fabre]

I had the same problem yesterday following a power outage.
I saw that MSR reacted but there was no effective reaction.
I didn't see anything in the logs
I reinstalled MSR and the problem went away.

[Motsie]

I Found something in the docker logs, which II don't understand how to fix:
stream | /var/reactor/logs/reactor.log not open boolean | false

opened file with correct file editor and saved back with docker stopped container, now message is gone, but did not solve issue.

[toggledbits]

You replied on the solution.

[Motsie]

@toggledbits Thanks for your remark, I get that it won't get much attention then
Solved the problem though. It was in the upgrade to 22203 from 22080, where the docker file got renamed. Came here to place this in this thread. Thanks again.

[Motsie]

@motsie
[SOLVED] this problem; it was in the upgrade from 22080 to 22203 where the Docker file got renamed.