[Resolved] Hubitat upgrade 2.5.3.123 may have broken login

[toggledbits]

In the config section of the controller configuration (in reactor.yaml ) for this controller (vera, apparently, not vera-edge), please add the following, indented the same as source: in that section:

  dump_entity: ['device_75','device_139']

This will create two files in logs called vera-device_75.json and vera-device_139.json. Please post them here or in a PR.

[cw-kid]

Thanks

I've posted the files here

https://reactor.toggledbits.com/mantisbt/view.php?id=233

[toggledbits]

OK. I think I've got it sorted. Build later today.

[toggledbits]

OK. Build 21203 is available.

[cw-kid]

@toggledbits said in Vera - Attempt to set primary to power_switch.state invalid:

Build 21203 is available.

Just updated to this build and now my Ezlo Plus controller is missing in MSR and I have error alerts about missing devices.

I can see this in the log:

2021-07-23T08:44:19.384Z <Structure:WARN> Structure#1 findEntity ezlo-plus>device_60e4a54a120bab11f9d77f67 controller undefined not found
2021-07-23T08:44:19.384Z <Structure:WARN> Structure#1 promiseEntity(ezlo-plus>device_60e4a54a120bab11f9d77f67,30000) timeout!
2021-07-23T08:44:19.384Z <Rule:CRIT> Rule#rule-kr7n2q7p failed subscription to ezlo-plus>device_60e4a54a120bab11f9d77f67
2021-07-23T08:44:19.385Z <Rule:CRIT> !timeout
2021-07-23T08:44:19.385Z <Rule:5:Rule.js:703> Rule#rule-kr7n2q7p start() dependencies resolved, performing initial evaluation
2021-07-23T08:44:19.386Z <Rule:5:Rule.js:962> Rule#rule-kr7n2q7p (Stairs Cupboard Door Closed) evaluate() acquiring mutex
2021-07-23T08:44:19.387Z <Rule:5:Rule.js:966> Rule#rule-kr7n2q7p._evaluate() mutex acquired, evaluating
2021-07-23T08:44:19.388Z <Rule:5:Rule.js:970> Rule#rule-kr7n2q7p update rate is 0/min limit 60/min
2021-07-23T08:44:19.388Z <Rule:5:Rule.js:892> Rule#rule-kr7n2q7p evaluateExpressions() with 0 expressions
2021-07-23T08:44:19.389Z <Structure:WARN> Structure#1 findEntity ezlo-plus>device_60e4a54a120bab11f9d77f67 controller undefined not found
2021-07-23T08:44:19.392Z <Rule:CRIT> ReferenceError: Can't find entity ezlo-plus>device_60e4a54a120bab11f9d77f67
ReferenceError: Can't find entity ezlo-plus>device_60e4a54a120bab11f9d77f67

I tried rebooting the Ezlo Plus controller but its still the same.

[toggledbits]

That's too late in the log, so it's a downstream effect of whatever else happened. Look up higher, near the startup of Reactor. Look for the string "starting controller interface" and then follow down from there.

[cw-kid]

@toggledbits said in Vera - Attempt to set primary to power_switch.state invalid:

starting controller interface

Patrick

<Structure:ERR> [Structure:start] failed to start controller ezlo-plus: Error: Cannot find module 'server/lib/Configuration'
Require stack:
- /home/stuart/reactor/server/lib/EzloController.js
2021-07-23T15:30:55.837Z <Structure:CRIT> Error: Cannot find module 'server/lib/Configuration'

2021-07-23T15:30:55.261Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController)
2021-07-23T15:30:55.272Z <Structure:INFO> Structure#1 starting controller interface vera-edge (VeraController)
2021-07-23T15:30:55.274Z <Structure:INFO> Structure#1 starting controller interface ezlo-plus (EzloController)
2021-07-23T15:30:55.276Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController)
2021-07-23T15:30:55.279Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController)
2021-07-23T15:30:55.412Z <default:null> Module VeraController v21202
2021-07-23T15:30:55.436Z <default:null> Module OWMWeatherController v21140
2021-07-23T15:30:55.441Z <default:null> Module SystemController v21102
2021-07-23T15:30:55.452Z <VeraController:NOTICE> VeraController#vera starting
2021-07-23T15:30:55.596Z <VeraController:INFO> VeraController#vera loaded mapping ver 21202 rev 1 format 1 notice 
2021-07-23T15:30:55.629Z <VeraController:NOTICE> VeraController#vera-edge starting
2021-07-23T15:30:55.641Z <Controller:CRIT> Controller: failed to load ezlo-plus implementation file:///home/stuart/reactor/server/lib/EzloController.js: Error: Cannot find module 'server/lib/Configuration'
Require stack:
- /home/stuart/reactor/server/lib/EzloController.js
2021-07-23T15:30:55.644Z <Controller:CRIT> Error: Cannot find module 'server/lib/Configuration'
Require stack:
- /home/stuart/reactor/server/lib/EzloController.js
Error: Cannot find module 'server/lib/Configuration'
Require stack:
- /home/stuart/reactor/server/lib/EzloController.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:885:15)
    at Function.Module._load (internal/modules/cjs/loader.js:730:27)
    at Module.require (internal/modules/cjs/loader.js:957:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/home/stuart/reactor/server/lib/EzloController.js:527:157)
    at Module._compile (internal/modules/cjs/loader.js:1068:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
    at Module.load (internal/modules/cjs/loader.js:933:32)
    at Function.Module._load (internal/modules/cjs/loader.js:774:14)
    at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
2021-07-23T15:30:55.704Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
2021-07-23T15:30:55.836Z <Structure:ERR> [Structure:start] failed to start controller ezlo-plus: Error: Cannot find module 'server/lib/Configuration'
Require stack:
- /home/stuart/reactor/server/lib/EzloController.js
2021-07-23T15:30:55.837Z <Structure:CRIT> Error: Cannot find module 'server/lib/Configuration'
Require stack:
- /home/stuart/reactor/server/lib/EzloController.js
Error: Cannot find module 'server/lib/Configuration'
Require stack:
- /home/stuart/reactor/server/lib/EzloController.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:885:15)
    at Function.Module._load (internal/modules/cjs/loader.js:730:27)
    at Module.require (internal/modules/cjs/loader.js:957:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/home/stuart/reactor/server/lib/EzloController.js:527:157)
    at Module._compile (internal/modules/cjs/loader.js:1068:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
    at Module.load (internal/modules/cjs/loader.js:933:32)
    at Function.Module._load (internal/modules/cjs/loader.js:774:14)
    at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
2021-07-23T15:30:55.839Z <app:INFO> Structure running; pausing for controllers' initial ready
2021-07-23T15:30:56.081Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online.
2021-07-23T15:30:57.165Z <VeraController:NOTICE> Controller VeraController#vera-edge is now online.
2021-07-23T15:31:04.144Z <VeraController:NOTICE> Controller VeraController#vera is now online.

I don't know what happened? It was working fine for the Ezlo Plus yesterday on the prior MSR build.

This is what I see in that folder:

Thanks

[toggledbits]

What install method are you using, and how are you starting MSR?

[cw-kid]

@toggledbits

I downloaded the reactor-latest-21203-9503e5d.tar.gz file from this page: https://reactor.toggledbits.com/download/latest/

I copied it to my Linux machine in this folder: /home/stuart

I then SSH in to the box with Putty and run these commands one by one, as root user:

cd /home/stuart
pkill -QUIT node
tar xzvf /home/stuart/reactor-latest-21203-9503e5d.tar.gz
sudo systemctl start reactor

This is the way I've always updated MSR. Except you now have a new download page.

Only slightly different thing about when I did it this morning, was that the downloaded file was called:

reactor-latest-21203-9503e5d.tar.gz

All the other ones prior had "generic" in their names, but I figured it likely didn't matter and maybe you'd just omitted that from the file name etc.

Regarding starting MSR nothing has change there either.

In this directory: /etc/systemd/system

There is a file called: reactor.service

# This file allows you to run your Reactor installation under systemd,
# so it can be started at boot. Copy this file (as root or under sudo)
# to /etc/systemd/system, and then run "systemctl daemon-reload". You
# can then able Reactor to start at boot "systemctl enable reactor".
# The usual systemctl subcommands can also be used to start, stop, and
# restart reactor at will (e.g. "systemctl restart reactor").

[Unit]
Description=Multi System Reactor
After=network.target

[Service]
Type=simple
User=stuart
WorkingDirectory=/home/stuart/reactor
ExecStart=/usr/bin/node app -p
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

[toggledbits]

Add above WorkingDirectory:

Environment=NODE_PATH=/home/stuart/reactor

and then:

sudo systemctl daemon-reload
sudo systemctl restart reactor

[cw-kid]

@toggledbits

Appears to have done the trick the Ezlo-Plus controller is back again in Entities.

Thanks