[Reactor] Bug when sending MQTT boolean payloads

[gwp1]

@alminsk FWIW, Home Assistant docs recommend a dedicated system to run Home Assistant.

[toggledbits]

OK. Unfortunately, that's probably the install about which we know the least, but it has been done successfully, as documented in this post and those that follow. The idea is to install Portainer in HassOS, and once that's done, you will be able to pull and install Reactor (MSR) as a docker container managed by Portainer.

https://smarthome.community/post/8937

[alminsk]

Thanks for the answers.
I am only at the beginning of the path and can completely reinstall everything. Which version of Home Assistant do you recommend to install so that Reactor would work without problems. And in what way.
I will be very grateful for detailed instructions or for a link to the instructions.

[toggledbits]

I would install Portainer as done under the HassOS you already have running, per the other linked (above) thread, and then you can install Reactor using the available docker images and the information also provided by that thread.

[iRobot]

When portainer is installed on HassOS, this is considered as a not supported HA install. This could give some trouble updating in the future.

Since you are using proxmox, I would make 2 virtual machines.

One to install HA using the HassOS script you have. And the other to install docker and portainer on which you can install MSR as explained by toggledbits.

This way you can also use docker for all other sort of projects which are not related to HA without interfering with it.

[alminsk]

Thanks everyone. So I will try to do so. Docker has already been installed as a second virtual machine. And how to properly install MSR in it.

[alminsk]

Installed in HA Porter through the integration of "HA Add-ons by alexbelgium" . Installed MSR in the Portainer and launched it. It started. But I can't log in to the Reactor web interface.

[alminsk]

[toggledbits]

You need to publish Reactor's port (8111).

[alminsk]

I am publishing a port (:8111) But for some reason it is not displayed. What I'm doing wrong

[alminsk]

I saw errors in the logs. But I do not know what they mean.

[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.