Arming Envisalink panel from MSR

[alminsk]

And for some reason the status is "unhealthy"

[toggledbits]

I don't know/use Portainer, but you didn't show your Volumes tab. Did you create a directory for your config and data and bind it, per the installation instructions?

[alminsk]

[alminsk]

Maybe I'm not choosing the right network?
I have it like this now:

[toggledbits]

That volume binding doesn't look right to me. Again, I'm not a Portainer user, but I would think that the path /var/reactor would be mentioned as related to the binding, since this is what Reactor is using internally within the container. It looks like you may have copied something from the Home Assistant configuration, but that's not right. I bet the /mnt/data/supervisor/homeassistant directory does not even exist in your new VM, because Home Assistant is not installed in that VM. You can't copy-paste/borrow from the Home Assistant configuration and get a successful Reactor configuration; different products, different configuration requirements. The Reactor installation instructions for docker show in the examples a Reactor data directory simply created in a regular user home directory. This is what you want. That directory (e.g. /home/username/reactor) should be bound to /var/reactor in the container.

Your network configuration is also suspect/incorrect. Again, it looks like you copied from Home Assistant's instructions, rather than using the Reactor instructions. The network mode is typically "host". If that doesn't work, you can try "bridge".

Can any of the Portainer+Reactor users please chime in here with some help for this user? Screen shots would be helpful. @black-cat @Fanan @vezinpi ...

[alminsk]

I have created such a catologist. /mnt/data/supervisor/homeassistant

I tried to install different networks

"Can any of the Portainer+Reactor users please chime in here with some help for this user? Screen shots would be helpful. @black-cat @Fanan @vezinpi ..." - I would be very grateful to you.

[Fanan]

@alminsk I use portainer succesfully and have the same volumes setting as you. I followed a guide from someone long time ago, and it's been a "do and forget" thing. I'm not a programmer, so I can't tell why somethings are as they are.

My network setting are different:

My setup is on a HA Blue (odroid n2+) and these values are also different:

Under Command & logging everything is the same except for the last line:

I hope this helps... As I wrote, I'm not the expert here, or know what every parameter means. Best of luck!
/Fanan

[toggledbits]

@Fanan Unfortunately, at least one of those differences is incorrect for you. The NODE_PATH would be correct as @alminsk showed in his screen shots; it should be /opt/reactor:/opt/reactor/node_modules. If it is not this exact value, some features of Reactor will not function.

The value of tag is not relevant.

@alminsk In the face of all of this, I decided yesterday to make Portainer a supported environment, so I got it installed on a spare Pi, did a couple of Reactor installs, and wrote down the steps, here: https://reactor.toggledbits.com/docs/Installation-docker-portainer/

[RogerO]

@toggledbits Hi Patrick,
Looking at your Portainer doc, found a minor error I think. In second paragraph in first section you have "For most Linux most systems," . Doesn't make sense.

Also, should "The stable branch builds have seen action for a while and are more... well... stable." Actually be "The stable branch builds have not seen action for a while and are more... well... stable.

[Fanan]

@toggledbits Thanks! As I mentioned before; these things are like greek to me, so I'm very thankful for all assistance. I changed the NODE_PATH. Strange that it has worked as a charm so far!

[alminsk]

Excellent. Everything worked. Thank you so much for the excellent REACTOR. Thank you so much for your support.

[alminsk]

Hello everyone. I ran into a problem: I can't save the rules.

I assume that the problem is in the path of the user file. Created a directory along this path.

The Portainer starts the reactor container . But the rules are not saved.

[alminsk]

I looked at the logs, everything is recorded well. The directory is specified correctly.

[alminsk]

Everything worked. I don't understand what the reason is. The rules are saved.

[alminsk]

Maybe I haven't figured out how to work with MSR yet. I used to work with Reactor in VeraPlus, but it works a little differently.

[toggledbits]

If the save button is faded green as shown in your screen shot, that means you have an error in your rule that you have to fix before saving. Your rule screen shot has everything collapsed/hidden; this is not helpful.

[alminsk]

Thanks. I'm figuring it out a little bit. Yes, there really were mistakes.

[gwp1]

@alminsk Now that you've been working in MSR for a short while it's time to revisit the manual. You'll find things that may not have made sense or that you didn't see a use for now make much more sense.

Focus on how to understand the signs MSR is giving you to help you troubleshoot.

I, too, came from the Vera Reactor plugin. "Same but different" applies here - but in all good ways.