Reactor-Editor / Reactor-ui-Status Errors

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

[toggledbits]

@kellyjelly32 said in Home Assistant add-on:

Two things: I keep getting the "reminder" to enter the last four digits despite having done it multiple times.

Off the top of my head, it sounds like you may not be entering it correctly? They aren't just digits, usually. Check to make sure your browser settings to allow cookies. Also generally, if you're reporting a problem like this, you should include the version information for the browser you are running, and in fact, you should go review the posting guidelines for this category because your post generally doesn't meet the requirements. This question should be separate from your other question in its own thread, also.

[kellyjelly32]

@toggledbits
I am running the addon in v0.0.7 (2023-02-20) [which is using Reactor build 23049 as per changelog] with:
Home Assistant 2023.3.1
Supervisor 2023.03.1
Operating System 9.5
Frontend 20230302.0 - latest

I was more trying to reach @mrw298 as he is the creator of the addon. Judging from the changelog, I can´t update MSR that simple and need to wait for a new version of his addon to be pushed.

The reminder pops up in any browser I tried so far, probably because it can´t really create a cookie. It even pops up in the HA mobile app. But I think the reactor front-end was never designed to run in such an environment. It is a minor cosmetic nuisance.

[mrw298]

@kellyjelly32 I sometimes lag a bit behind @toggledbits packaging it up for HA (especially if I don't notice a new version), I've just pushed a new version of the addon with Reactor build 23063 in it.

I've noticed that prompt coming back too, it's probably something to do with how I've wedged reactor into an HA addon, will see if I can figure out what needs tweaking to make it go away.

[mrw298]

@RogerO sorry for the delay responding, if the files are in dist-config I'm not quite certain how it's going wrong!

On startup it copies those files from /opt/reactor/dist-config -> /config/reactor if the /config/reactor directory doesn't exist.

hassio-reactor-addon/reactor/run.sh at main · mrw298/hassio-reactor-addon

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

If it can't find logging.yaml that steps failed and stopping the addon, deleting /config/reactor and restarting it should get it to retry.

The addon logs of that first start would hopefully contain any error messages.