Home Assistant add-on

[mrw298]

I've done a bit of repackaging of MSR to make it work as an add-on under Home Assistant mostly for my own purposes but hopefully it makes it a bit easier to install and get going.

GitHub - mrw298/hassio-reactor-addon

Contribute to mrw298/hassio-reactor-addon development by creating an account on GitHub.

[RogerO]

Excellent, was hoping it would eventually come to HA. Will you be adding update instructions at some point?

[mrw298]

I'll nudge it along as updates to the MSR docker container are released, it's all using the HA addon framework so it should prompt you automatically to update the addon when an update is available.

[Fanan]

I followed the link and installed the repo, but it's not showing up in HA. All other custom repos are visible, but not this one. Do you know why?

[mrw298]

@Fanan I introduced a bug into the addon config when I added the other architectures, should be sorted now.

[Fanan]

@mrw298 Thank you. It's now visible. Second problem... I'm running MSR under portainer in HA - so my MSR is on the same device (Home Assistant Blue) as HA. When I try to start your addon, after inserting the long lived access token, I get a error, because the port (8111) is already taken, by MSR:
Is this obsticle even possible to overcome?
Best regards,
Fanan

[mrw298]

@Fanan i can’t think of an easy way in the add on framework. Might be easiest to change your published port for your existing instance in portainer (assuming you’re not using host networking)

[Pabla]

@Fanan changing the port for one of the MSR instances should fix your issue. Great work @mrw298 i may eventually run MSR on HA

[gwp1]

Sorry if I'm being dense here this morning - this is to link an existing MSR installation to HA vs having to manually create the long-lived key and manually update configs?

[RogerO]

@gwp1 If I understand your question correctly, this is to allow you to run MSR as a component of your HASS installation on the same hardware.
@mrw298 Does this contain the addons such as MQTT and zwavejs?

[gwp1]

@RogerO Yes, I believe you understand the ask. I already have HA and MSR on sep RPi's, linked via config, and even shared MSR within a HA dashboard. Was looking to see if this streamlined any of that but it sounds like it's not something I would need.

[Pabla]

@gwp1 It makes MSR more accessible for HA users since you won't need a second piece of HW to run MSR on if you are running HassOS

[RogerO]

Hello,
Trying to install this and getting the following in the logs:

2023-02-07 00:26:46,034 INFO exited: reactor (exit status 1; not expected)
2023-02-07 00:26:47,044 INFO spawned: 'reactor' with pid 3569
Using existing set-up
Reactor Token is set, updating config
Reactor latest-23028-ddc3fb14 app 22364 configuration from /config/reactor
NODE_PATH /opt/reactor:/opt/reactor/node_modules
2023-02-07 00:26:48,154 INFO success: reactor entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
node:internal/fs/utils:345
throw err;
^
Error: ENOENT: no such file or directory, open '/config/reactor/logging.yaml'
at Object.openSync (node:fs:585:3)
at Object.readFileSync (node:fs:453:35)
at Function.loadConfig (/opt/reactor/server/lib/Configuration.js:226:68)
at Function.getInstance (/opt/reactor/server/lib/Configuration.js:144:66)
at Object.<anonymous> (/opt/reactor/app.js:105:97)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: '/config/reactor/logging.yaml'

Looked in the/opt directory and it was empty. Getting a bad gateway error when I try to load the page.

Thanks,
Roger

[mrw298]

@RogerO somethings a bit odd has gone on. First time the container starts it copies the files from /opt/reactor/dist-config to /config/reactor and does a basic setup.

You should be able to stop the container, delete the /config/reactor directory and start it back up again to recreate the config.

That does rely on the dist-configs existing and it’s strange that /opt is empty. Do you know which architecture you’re running, perhaps there’s a difference between the images.

[RogerO]

Currently running HASSIO on a RPI4
Home Assistant 2023.2.2
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest

Uninstalled the addin and deleted the reactor.yaml file. Installed the addin and if choked because it couldn't find yaml file. Using winscp I created one and it will not start. /opt/ is empty.

[toggledbits]

The /opt directory contents are inside the container and not visible without attaching to the container. I'm not surprised you don't see anything there; it's expected, actually. Beyond that, @mrw298 will need to respond for the add-on.

[RogerO]

oh yeah, forgot that part.

[RogerO]

@mrw298 Anything I can do to help you troubleshoot or do you have any ideas on how to get this resolved?

[RogerO]

Here is a file list from the container, Sorry that it is a screen shot. Don't want to f up my system by typing something stupid and not a docker expert. If there is a specific directory you want me to look at let me know

Still getting 502 bad gateway from nginx

[kellyjelly32]

I am using the addon for HA, running excellent.
Finally my dream came true, using the excellent reactor engine to automate all my devices, mix and match rules and technologies.
Will offload now finally from my rusty Vera Lite to HA...

Two things: I keep getting the "reminder" to enter the last four digits despite having done it multiple times.
Can I safely update MSR from within the addon or do I need to wait for an update to the addon?