Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Vera - Attempt to set primary to power_switch.state invalid
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor

Vera - Attempt to set primary to power_switch.state invalid

Scheduled Pinned Locked Moved Multi-System Reactor
12 Posts 2 Posters 1.8k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toggledbitsT 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-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #3

    Thanks

    I've posted the files here

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

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #4

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

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      1 Reply Last reply
      1
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #5

        OK. Build 21203 is available.

        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

        cw-kidC 1 Reply Last reply
        1
        • toggledbitsT toggledbits

          OK. Build 21203 is available.

          cw-kidC Offline
          cw-kidC Offline
          cw-kid
          wrote on last edited by cw-kid
          #6

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

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #7

            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.

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            cw-kidC 1 Reply Last reply
            0
            • toggledbitsT 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-kidC Offline
              cw-kidC Offline
              cw-kid
              wrote on last edited by cw-kid
              #8

              @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:

              a26ed327-0469-41d9-ac88-a5a07e6ae965-image.png

              Thanks

              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #9

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

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                cw-kidC 1 Reply Last reply
                0
                • toggledbitsT toggledbits

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

                  cw-kidC Offline
                  cw-kidC Offline
                  cw-kid
                  wrote on last edited by cw-kid
                  #10

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

                  9b43d461-bbcc-4980-bbe9-2a2fb83968cc-image.png

                  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
                  
                  1 Reply Last reply
                  0
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by
                    #11

                    Add above WorkingDirectory:

                    Environment=NODE_PATH=/home/stuart/reactor
                    

                    and then:

                    sudo systemctl daemon-reload
                    sudo systemctl restart reactor
                    

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    cw-kidC 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      Add above WorkingDirectory:

                      Environment=NODE_PATH=/home/stuart/reactor
                      

                      and then:

                      sudo systemctl daemon-reload
                      sudo systemctl restart reactor
                      
                      cw-kidC Offline
                      cw-kidC Offline
                      cw-kid
                      wrote on last edited by
                      #12

                      @toggledbits

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

                      Thanks

                      1 Reply Last reply
                      1
                      • toggledbitsT toggledbits locked this topic on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

                      • Arming Envisalink panel from MSR
                        T
                        tamorgen
                        0
                        7
                        192

                      • [Solved] DynamicGroupController updating members issue
                        CrilleC
                        Crille
                        0
                        5
                        141

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        148
                        130.5k

                      • DynamicGroupController and attributes
                        therealdbT
                        therealdb
                        1
                        5
                        131

                      • Upgrade Issues
                        T
                        tbully
                        0
                        9
                        245

                      • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                        toggledbitsT
                        toggledbits
                        0
                        10
                        270

                      • [SOLVED] Question regarding "in" vs "contains" vs contents of the string
                        G
                        gwp1
                        0
                        5
                        149

                      • openLuup console disappeared - 500 - Internal Server Error
                        A
                        a-lurker
                        0
                        2
                        178

                      • Logon screen timeout
                        G
                        gwp1
                        0
                        5
                        199

                      • [MSR] Copy&past of actions and/or drag&drop between set/reset
                        toggledbitsT
                        toggledbits
                        0
                        9
                        384

                      • Upgrade advice - upgrade from aarch64 to ARM64 image
                        toggledbitsT
                        toggledbits
                        0
                        4
                        223
                      Powered by NodeBB | Contributors
                      Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Unsolved