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

Matteburk

@Matteburk
Caution: zwave-js-ui docker 11.4.0 is broken
toggledbitsT
About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier. Ref: Issue 4401
Software
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...is back.... https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA C
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
About
Posts
88
Topics
13
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits

    Big thanx again Patrick!
    Keep up the good work!!

    Now bedtime in Sweden!

    /Mattias

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits
    ok.... I cut the power and restarted the pie and msr got up by it self!!

    Coool!

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    ok... what does that line do?

    got this
    pi@raspberrypi:~ $ sudo systemctl enable reactor
    Created symlink /etc/systemd/system/multi-user.target.wants/reactor.service \u2192 /etc/systemd/system/reactor.service.
    pi@raspberrypi:~ $

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits said in Updated to latest MSR 21243 and no entities are being executed I Hubitat:

    ExecStart=/home/pi/.local/lib/nodejs/node-v14.15.4-linux-armv7l/bin/node app -p

    Changed it and now i can reach msr thrue UI!

    Here is the reactor.log

    2021-09-06T21:05:42.633Z app:null Reactor "1.0.1-21243-ab6d917" starting on v14.15.4
    2021-09-06T21:05:42.636Z app:INFO Process ID 1780; platform linux/arm #1408 SMP Mon Mar 22 12:49:24 GMT 2021; locale [ "sv-SE", "UTF-8" ]
    2021-09-06T21:05:42.637Z app:INFO Basedir /home/pi/reactor; data in /home/pi/reactor/storage
    2021-09-06T21:05:42.637Z app:INFO NODE_PATH /home/pi/reactor; module paths [ "/home/pi/reactor/node_modules", "/home/pi/node_modules", "/home/node_modules", "/node_modules" ]
    2021-09-06T21:05:42.781Z Plugin:null Module Plugin v21173
    2021-09-06T21:05:42.797Z default:INFO Module Entity v21177
    2021-09-06T21:05:42.805Z Controller:null Module Controller v21226
    2021-09-06T21:05:42.806Z default:null Module Structure v21229
    2021-09-06T21:05:42.822Z default:null Module Ruleset v21096
    2021-09-06T21:05:42.823Z default:null Module Rulesets v21096
    2021-09-06T21:05:42.869Z default:null Module Rule v21224
    2021-09-06T21:05:42.880Z default:null Module Engine v21213
    2021-09-06T21:05:42.881Z default:null Module httpapi v21238
    2021-09-06T21:05:42.886Z default:null Module httpproxy v21054
    2021-09-06T21:05:42.925Z default:null Module wsapi v21196
    2021-09-06T21:05:42.928Z app:NOTICE Starting Structure...
    2021-09-06T21:05:42.936Z Structure:INFO Structure#1 starting controller interface vera (VeraController)
    2021-09-06T21:05:42.944Z Structure:INFO Structure#1 starting controller interface hubitat (HubitatController)
    2021-09-06T21:05:42.947Z Structure:INFO Structure#1 starting controller interface reactor_system (SystemController)
    2021-09-06T21:05:43.018Z default:null Module VeraController v21236
    2021-09-06T21:05:43.026Z default:null Module HubitatController v21243
    2021-09-06T21:05:43.029Z default:null Module SystemController v21102
    2021-09-06T21:05:43.037Z VeraController:NOTICE VeraController#vera starting
    2021-09-06T21:05:43.145Z VeraController:INFO VeraController#vera loaded mapping ver 21236 rev 1 format 1 notice
    2021-09-06T21:05:43.148Z VeraController:INFO VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state
    2021-09-06T21:05:43.227Z Controller:NOTICE Controller SystemController#reactor_system is now online.
    2021-09-06T21:05:43.339Z app:INFO Structure running; pausing for controllers' initial ready
    2021-09-06T21:05:43.347Z Controller:NOTICE HubitatController#hubitat not ready; performing initial connect/query
    2021-09-06T21:05:43.896Z VeraController:NOTICE Controller VeraController#vera is now online.
    2021-09-06T21:05:45.291Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.322Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.383Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.387Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.391Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.394Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.409Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.414Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.418Z Controller:ERR HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T21:05:45.510Z Controller:INFO HubitatController#hubitat connecting to hub's eventsocket WebSocket API at ws://192.168.68.145/eventsocket
    2021-09-06T21:05:45.517Z Controller:NOTICE Controller HubitatController#hubitat is now online.
    2021-09-06T21:05:45.522Z app:NOTICE Starting Reaction Engine...
    2021-09-06T21:05:45.524Z Engine:INFO Reaction Engine starting
    2021-09-06T21:05:45.525Z Engine:INFO Checking rule sets...
    2021-09-06T21:05:45.542Z Engine:INFO Checking rules...
    2021-09-06T21:05:45.544Z Engine:INFO Data check complete; no corrections.

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    I edited them directly on the pie in the textfile.

    this is what the var log file said:

    Sep 6 22:17:23 raspberrypi dhcpcd[428]: wlan0: fe80::465:fde6:f33:2344 is reachable again
    Sep 6 22:17:23 raspberrypi avahi-daemon[429]: Withdrawing address record for fe80::2598:15e9:620:fe7d on eth0.
    Sep 6 22:17:26 raspberrypi dhcpcd[428]: eth0: leased 192.168.68.126 for 7200 seconds
    Sep 6 22:17:26 raspberrypi avahi-daemon[429]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.68.126.
    Sep 6 22:17:26 raspberrypi dhcpcd[428]: eth0: adding route to 192.168.68.0/24
    Sep 6 22:17:26 raspberrypi dhcpcd[428]: eth0: adding default route via 192.168.68.1
    Sep 6 22:17:26 raspberrypi avahi-daemon[429]: New relevant interface eth0.IPv4 for mDNS.
    Sep 6 22:17:26 raspberrypi avahi-daemon[429]: Registering new address record for 192.168.68.126 on eth0.IPv4.
    Sep 6 22:17:34 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
    Sep 6 22:50:34 raspberrypi systemd-timesyncd[339]: Synchronized to time server for the first time 178.16.128.13:123 (2.debian.pool.ntp.org).
    Sep 6 22:50:41 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
    Sep 6 22:53:32 raspberrypi dbus-daemon[626]: [session uid=1000 pid=626] Activating service name='ca.desrt.dconf' requested by ':1.28' (uid=1000 pid=1084 comm="mousepad /var/log/syslog ")
    Sep 6 22:53:32 raspberrypi dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'ca.desrt.dconf'
    Sep 6 22:54:50 raspberrypi dbus-daemon[418]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.51' (uid=1000 pid=1100 comm="/usr/lib/chromium-browser/chromium-browser-v7 --fo")
    Sep 6 22:54:50 raspberrypi systemd[1]: Starting Hostname Service...
    Sep 6 22:54:50 raspberrypi dbus-daemon[418]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Sep 6 22:54:50 raspberrypi systemd[1]: Started Hostname Service.
    Sep 6 22:54:50 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:50 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:51 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:51 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:52 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:52 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:53 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:53 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:54 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:54 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:55 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas
    Sep 6 22:54:55 raspberrypi gvfsd[665]: mkdir failed on directory /var/cache/samba: Åtkomst nekas

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits Could not reach thrue UI .

    The reactor.log file is no missing since the rm command.....

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits
    hehe.... went exited

    /etc/systemd/system/reactor.service......

    [Unit]
    Description=Multi System Reactor
    After=network.target
    
    [Service]
    Type=simple
    User=pi
    WorkingDirectory=/home/pi/reactor
    Environment=NODE_PATH=/home/pi/reactor
    ExecStart=/home/pi/.local/lib/nodejs/node-v14.15.4-linux-armv7l/bin/node
    
    
    
    Restart=on-failure
    RestartSec=5s
    
    [Install]
    WantedBy=multi-user.target
    

    Reactor log......

    2021-09-06T20:07:08.063Z <app:null> Reactor "1.0.1-21243-ab6d917" starting on v14.15.4
    2021-09-06T20:07:08.066Z <app:INFO> Process ID 3029; platform linux/arm #1408 SMP Mon Mar 22 12:49:24 GMT 2021; locale [ "sv-SE", "UTF-8" ]
    2021-09-06T20:07:08.067Z <app:INFO> Basedir /home/pi/reactor; data in /home/pi/reactor/storage
    2021-09-06T20:07:08.067Z <app:INFO> NODE_PATH /home/pi/reactor; module paths [ "/home/pi/reactor/node_modules", "/home/pi/node_modules", "/home/node_modules", "/node_modules" ]
    2021-09-06T20:07:08.241Z <Plugin:null> Module Plugin v21173
    2021-09-06T20:07:08.273Z <default:INFO> Module Entity v21177
    2021-09-06T20:07:08.284Z <Controller:null> Module Controller v21226
    2021-09-06T20:07:08.286Z <default:null> Module Structure v21229
    2021-09-06T20:07:08.305Z <default:null> Module Ruleset v21096
    2021-09-06T20:07:08.306Z <default:null> Module Rulesets v21096
    2021-09-06T20:07:08.380Z <default:null> Module Rule v21224
    2021-09-06T20:07:08.397Z <default:null> Module Engine v21213
    2021-09-06T20:07:08.399Z <default:null> Module httpapi v21238
    2021-09-06T20:07:08.406Z <default:null> Module httpproxy v21054
    2021-09-06T20:07:08.450Z <default:null> Module wsapi v21196
    2021-09-06T20:07:08.454Z <app:NOTICE> Starting Structure...
    2021-09-06T20:07:08.463Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController)
    2021-09-06T20:07:08.473Z <Structure:INFO> Structure#1 starting controller interface hubitat (HubitatController)
    2021-09-06T20:07:08.480Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController)
    2021-09-06T20:07:08.622Z <default:null> Module VeraController v21236
    2021-09-06T20:07:08.629Z <default:null> Module HubitatController v21243
    2021-09-06T20:07:08.632Z <default:null> Module SystemController v21102
    2021-09-06T20:07:08.642Z <VeraController:NOTICE> VeraController#vera starting
    2021-09-06T20:07:08.765Z <VeraController:INFO> VeraController#vera loaded mapping ver 21236 rev 1 format 1 notice 
    2021-09-06T20:07:08.767Z <VeraController:INFO> VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state
    2021-09-06T20:07:08.887Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
    2021-09-06T20:07:09.035Z <app:INFO> Structure running; pausing for controllers' initial ready
    2021-09-06T20:07:09.044Z <Controller:NOTICE> HubitatController#hubitat not ready; performing initial connect/query
    2021-09-06T20:07:09.629Z <VeraController:NOTICE> Controller VeraController#vera is now online.
    2021-09-06T20:07:10.118Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.158Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.274Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.281Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.287Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.289Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.318Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.326Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.331Z <Controller:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
    2021-09-06T20:07:10.478Z <Controller:INFO> HubitatController#hubitat connecting to hub's eventsocket WebSocket API at ws://192.168.68.145/eventsocket
    2021-09-06T20:07:10.484Z <Controller:NOTICE> Controller HubitatController#hubitat is now online.
    2021-09-06T20:07:10.489Z <app:NOTICE> Starting Reaction Engine...
    2021-09-06T20:07:10.491Z <Engine:INFO> Reaction Engine starting
    2021-09-06T20:07:10.492Z <Engine:INFO> Checking rule sets...
    2021-09-06T20:07:10.504Z <Engine:INFO> Checking rules...
    2021-09-06T20:07:10.506Z <Engine:INFO> Data check complete; no corrections.
    
    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits

    We have a winner!

    I did
    cd reactor
    NODE_PATH=$(pwd) node app ( this line I totally missed)

    and my house lit up like a Christmas trea!😂

    Thank you for your patience with me Patrick!

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits
    Gaaah..... im tired and beginner.....Sorry....

    ok so this I no get when I run node app.js

    2021-09-06T19:59:36.893Z Rule:5:980:Rule.js Rule#rule-kmst5xze._evaluate() mutex acquired, evaluating
    2021-09-06T19:59:36.894Z Rule:5:984:Rule.js Rule#rule-kmst5xze update rate is 1/min limit 60/min
    2021-09-06T19:59:36.895Z Rule:5:904:Rule.js Rule#rule-kmst5xze evaluateExpressions() with 0 expressions
    2021-09-06T19:59:36.897Z Rule:CRIT Error: Cannot find module 'common/util'
    Require stack:

    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      Error: Cannot find module 'common/util'
      Require stack:
    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
      at Function.Module._load (internal/modules/cjs/loader.js:725:27)
      at Module.require (internal/modules/cjs/loader.js:952:19)
      at require (internal/modules/cjs/helpers.js:88:18)
      at Engine._get_lexp_extensions (/home/pi/reactor/server/lib/Engine.js:862:25)
      at Rule.evaluateExpressions (/home/pi/reactor/server/lib/Rule.js:904:330)
      at Rule._evaluate (/home/pi/reactor/server/lib/Rule.js:994:344)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
      at async /home/pi/reactor/server/lib/Rule.js:963:17
    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits But if I no try to start via node app.js
    I get in terminal window

    pi@raspberrypi:~ $ node app.js
    internal/modules/cjs/loader.js:883
    throw err;
    ^

    Error: Cannot find module '/home/pi/app.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
    at Function.Module._load (internal/modules/cjs/loader.js:725:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47 {
    code: 'MODULE_NOT_FOUND',
    requireStack: []
    }
    pi@raspberrypi:~ $

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits they that you refer to are there but nothing after I now stopped and started

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits
    hmmm nothing is being logged there after stop ,start. the log file has not been updated since I tried node app.js for a couple of hours ago

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits
    I dont see the string reactor version starting on XXXX as you wrote.

    From the var/log syslog I get this after stopped and started reactor via systemctl restart reactor

    Sep 6 20:58:49 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 6 20:58:50 raspberrypi systemd[1]: reactor.service: Succeeded.
    Sep 6 21:00:41 raspberrypi dbus-daemon[402]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.57' (uid=1000 pid=1071 comm="/usr/lib/chromium-browser/chromium-browser-v7 --fo")
    Sep 6 21:00:41 raspberrypi systemd[1]: Starting Hostname Service...
    Sep 6 21:00:41 raspberrypi dbus-daemon[402]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Sep 6 21:00:41 raspberrypi systemd[1]: Started Hostname Service.

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @crille tried .....

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits ok... yes for sure it is me setting something up wrong... will struggle some more... 🙂

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits

    I have followed your instructions but no success.

    Dont no what to do..... Here is the log from msr
    /Mattias

    Require stack:

    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      Error: Cannot find module 'common/util'
      Require stack:
    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
      at Function.Module._load (internal/modules/cjs/loader.js:725:27)
      at Module.require (internal/modules/cjs/loader.js:952:19)
      at require (internal/modules/cjs/helpers.js:88:18)
      at Engine._get_lexp_extensions (/home/pi/reactor/server/lib/Engine.js:862:25)
      at Rule.evaluateExpressions (/home/pi/reactor/server/lib/Rule.js:904:330)
      at Rule._evaluate (/home/pi/reactor/server/lib/Rule.js:994:344)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
      at async /home/pi/reactor/server/lib/Rule.js:963:17
      2021-09-06T16:19:30.352Z Rule:5:980:Rule.js Rule#rule-ksn5u2pn._evaluate() mutex acquired, evaluating
      2021-09-06T16:19:30.352Z Rule:5:984:Rule.js Rule#rule-ksn5u2pn update rate is 0/min limit 60/min
      2021-09-06T16:19:30.353Z Rule:5:904:Rule.js Rule#rule-ksn5u2pn evaluateExpressions() with 0 expressions
      2021-09-06T16:19:30.354Z Rule:CRIT Error: Cannot find module 'common/util'
      Require stack:
    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      Error: Cannot find module 'common/util'
      Require stack:
    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
      at Function.Module._load (internal/modules/cjs/loader.js:725:27)
      at Module.require (internal/modules/cjs/loader.js:952:19)
      at require (internal/modules/cjs/helpers.js:88:18)
      at Engine._get_lexp_extensions (/home/pi/reactor/server/lib/Engine.js:862:25)
      at Rule.evaluateExpressions (/home/pi/reactor/server/lib/Rule.js:904:330)
      at Rule._evaluate (/home/pi/reactor/server/lib/Rule.js:994:344)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
      at async /home/pi/reactor/server/lib/Rule.js:963:17
      2021-09-06T16:19:30.356Z Rule:5:980:Rule.js Rule#rule-ksm11ihr._evaluate() mutex acquired, evaluating
      2021-09-06T16:19:30.356Z Rule:5:984:Rule.js Rule#rule-ksm11ihr update rate is 0/min limit 60/min
      2021-09-06T16:19:30.357Z Rule:5:904:Rule.js Rule#rule-ksm11ihr evaluateExpressions() with 0 expressions
      2021-09-06T16:19:30.358Z Rule:CRIT Error: Cannot find module 'common/util'
      Require stack:
    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      Error: Cannot find module 'common/util'
      Require stack:
    • /home/pi/reactor/server/lib/Engine.js
    • /home/pi/reactor/server/lib/httpapi.js
    • /home/pi/reactor/app.js
      at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
      at Function.Module._load (internal/modules/cjs/loader.js:725:27)
      at Module.require (internal/modules/cjs/loader.js:952:19)
      at require (internal/modules/cjs/helpers.js:88:18)
      at Engine._get_lexp_extensions (/home/pi/reactor/server/lib/Engine.js:862:25)
      at Rule.evaluateExpressions (/home/pi/reactor/server/lib/Rule.js:904:330)
      at Rule._evaluate (/home/pi/reactor/server/lib/Rule.js:994:344)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
      at async /home/pi/reactor/server/lib/Rule.js:963:17
    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    I checked and changed the lines to this ( I guess something is wrong there)
    [Unit]
    Description=Multi System Reactor
    After=network.target

    [Service]
    Type=simple
    User=pi
    WorkingDirectory=/home/pi/reactor
    Environment=NODE_PATH=/home/pi/reactor
    ExecStart=/home/pi/.local/lib/nodejs/node-v14.15.4-linux-armv7l/bin/node

    Restart=on-failure
    RestartSec=5s

    [Install]
    WantedBy=multi-user.target

    and restarted reactor....... then I see this in log.....

    Sep 5 15:26:16 raspberrypi systemd[9870]: reactor.service: Failed to determine user credentials: No such process
    Sep 5 15:26:16 raspberrypi systemd[9870]: reactor.service: Failed at step USER spawning /usr/local/lib/nodejs/bin/node: No such process
    Sep 5 15:26:16 raspberrypi systemd[1]: reactor.service: Main process exited, code=exited, status=217/USER
    Sep 5 15:26:16 raspberrypi systemd[1]: reactor.service: Failed with result 'exit-code'.
    Sep 5 15:26:21 raspberrypi systemd[1]: reactor.service: Service RestartSec=5s expired, scheduling restart.
    Sep 5 15:26:21 raspberrypi systemd[1]: reactor.service: Scheduled restart job, restart counter is at 20060.
    Sep 5 15:26:21 raspberrypi systemd[1]: Stopped Multi System Reactor.
    Sep 5 15:26:21 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 15:26:21 raspberrypi systemd[9871]: reactor.service: Failed to determine user credentials: No such process
    Sep 5 15:26:21 raspberrypi systemd[9871]: reactor.service: Failed at step USER spawning /usr/local/lib/nodejs/bin/node: No such process
    Sep 5 15:26:21 raspberrypi systemd[1]: reactor.service: Main process exited, code=exited, status=217/USER
    Sep 5 15:26:21 raspberrypi systemd[1]: reactor.service: Failed with result 'exit-code'.
    Sep 5 15:26:22 raspberrypi systemd[1]: Reloading.
    Sep 5 15:26:22 raspberrypi systemd[1]: /etc/systemd/system/teamviewerd.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/teamviewerd.pid \u2192 /run/teamviewerd.pid; please update the unit file accordingly.
    Sep 5 15:26:26 raspberrypi systemd[1]: reactor.service: Service RestartSec=5s expired, scheduling restart.
    Sep 5 15:26:26 raspberrypi systemd[1]: reactor.service: Scheduled restart job, restart counter is at 20061.
    Sep 5 15:26:26 raspberrypi systemd[1]: Stopped Multi System Reactor.
    Sep 5 15:26:26 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 15:26:27 raspberrypi systemd[1]: reactor.service: Succeeded.
    Sep 5 15:26:42 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 15:26:43 raspberrypi systemd[1]: reactor.service: Succeeded.
    Sep 5 15:34:06 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 15:34:06 raspberrypi systemd[1]: reactor.service: Succeeded.

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    This is what the log says:
    Sep 5 00:00:00 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="383" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
    Sep 5 00:00:00 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="383" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
    Sep 5 00:00:00 raspberrypi systemd[1]: logrotate.service: Succeeded.
    Sep 5 00:00:00 raspberrypi systemd[1]: Started Rotate log files.
    Sep 5 00:00:00 raspberrypi systemd[1]: man-db.service: Succeeded.
    Sep 5 00:00:00 raspberrypi systemd[1]: Started Daily man-db regeneration.
    Sep 5 00:00:02 raspberrypi colord[955]: failed to get session [pid 17774]: Inga data tillg\u00e4ngliga
    Sep 5 00:00:05 raspberrypi systemd[1]: reactor.service: Service RestartSec=5s expired, scheduling restart.
    Sep 5 00:00:05 raspberrypi systemd[1]: reactor.service: Scheduled restart job, restart counter is at 9474.
    Sep 5 00:00:05 raspberrypi systemd[1]: Stopped Multi System Reactor.
    Sep 5 00:00:05 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 00:00:05 raspberrypi systemd[17799]: reactor.service: Failed to determine user credentials: No such process
    Sep 5 00:00:05 raspberrypi systemd[17799]: reactor.service: Failed at step USER spawning /usr/local/lib/nodejs/bin/node: No such process
    Sep 5 00:00:05 raspberrypi systemd[1]: reactor.service: Main process exited, code=exited, status=217/USER
    Sep 5 00:00:05 raspberrypi systemd[1]: reactor.service: Failed with result 'exit-code'.
    Sep 5 00:00:10 raspberrypi systemd[1]: reactor.service: Service RestartSec=5s expired, scheduling restart.
    Sep 5 00:00:10 raspberrypi systemd[1]: reactor.service: Scheduled restart job, restart counter is at 9475.
    Sep 5 00:00:10 raspberrypi systemd[1]: Stopped Multi System Reactor.
    Sep 5 00:00:10 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 00:00:10 raspberrypi systemd[17800]: reactor.service: Failed to determine user credentials: No such process
    Sep 5 00:00:10 raspberrypi systemd[17800]: reactor.service: Failed at step USER spawning /usr/local/lib/nodejs/bin/node: No such process
    Sep 5 00:00:10 raspberrypi systemd[1]: reactor.service: Main process exited, code=exited, status=217/USER
    Sep 5 00:00:10 raspberrypi systemd[1]: reactor.service: Failed with result 'exit-code'.
    Sep 5 00:00:15 raspberrypi systemd[1]: reactor.service: Service RestartSec=5s expired, scheduling restart.
    Sep 5 00:00:15 raspberrypi systemd[1]: reactor.service: Scheduled restart job, restart counter is at 9476.
    Sep 5 00:00:15 raspberrypi systemd[1]: Stopped Multi System Reactor.
    Sep 5 00:00:15 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 00:00:15 raspberrypi systemd[17801]: reactor.service: Failed to determine user credentials: No such process
    Sep 5 00:00:15 raspberrypi systemd[17801]: reactor.service: Failed at step USER spawning /usr/local/lib/nodejs/bin/node: No such process
    Sep 5 00:00:15 raspberrypi systemd[1]: reactor.service: Main process exited, code=exited, status=217/USER
    Sep 5 00:00:15 raspberrypi systemd[1]: reactor.service: Failed with result 'exit-code'.
    Sep 5 00:00:21 raspberrypi systemd[1]: reactor.service: Service RestartSec=5s expired, scheduling restart.
    Sep 5 00:00:21 raspberrypi systemd[1]: reactor.service: Scheduled restart job, restart counter is at 9477.
    Sep 5 00:00:21 raspberrypi systemd[1]: Stopped Multi System Reactor.
    Sep 5 00:00:21 raspberrypi systemd[1]: Started Multi System Reactor.
    Sep 5 00:00:21 raspberrypi systemd[17802]: reactor.service: Failed to determine user credentials: No such process
    Sep 5 00:00:21 raspberrypi systemd[17802]: reactor.service: Failed at step USER spawning /usr/local/lib/nodejs/bin/node: No such process
    Sep 5 00:00:21 raspberrypi systemd[1]: reactor.service: Main process exited, code=exited, status=217/USER
    Sep 5 00:00:21 raspberrypi systemd[1]: reactor.service: Failed with result 'exit-code'.
    Sep 5 00:00:26 raspberrypi systemd[1]: reactor.service: Service RestartSec=5s expired, scheduling restart.
    Sep 5 00:00:26 raspberrypi systemd[1]: reactor.service: Scheduled restart job, restart counter is at 9478.

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits@
    Followed your instructions to run it under systemd but when i do nr 4 and 5 reactor won't start...
    Should I write sudo systemctl start reactor under pi@raspberrypi as in picture?

    /Mattias

    Skärmavbild 2021-09-04 kl. 10.39.40.png

    Multi-System Reactor

  • Updated to latest MSR 21243 and no entities are being executed I Hubitat
    M Matteburk

    @toggledbits I run it with Node app.js

    Multi-System Reactor
  • Login

  • Don't have an account? Register

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