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
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
Tuya Wifi to Tasmota flashing
CatmanV2C
Just popping this in here in case it's helpful to anyone else later. I've got several Tuya Wifi sockets that I'm getting rid of / replacing. Looking at which ones, if any, can be flashed to Tasmota: https://www.amazon.co.uk/dp/B09Y212TCK?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 Are NOT flashable C
Zigbee
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Zigbee2mqtt installed! sytemctl not happy :(
CatmanV2C
Hello oh great ones. After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi Can connect to the front end and everything Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this: [Unit] Description=zigbee2mqtt After=network.target [Service] Environment=NODE_ENV=production Type=notify ExecStart=/usr/local/bin/node index.js WorkingDirectory=/opt/zigbee2mqtt StandardOutput=inherit # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5) StandardError=inherit WatchdogSec=10s Restart=always RestartSec=10s User=pi [Install] WantedBy=multi-user.target Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using. Running manually pnpm start in /opt/zigbee2mqtt works fine However: catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service Job for zigbee2mqtt.service failed because the control process exited with error code. See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details. Which I have catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service ● zigbee2mqtt.service - zigbee2mqtt Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER) Main PID: 3093 (code=exited, status=217/USER) and -- A start job for unit zigbee2mqtt.service has begun execution. -- -- The job identifier is 17477. Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process -- Subject: Process /usr/local/bin/node could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/local/bin/node could not be executed and failed. -- -- The error number returned by this process is ERRNO. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit zigbee2mqtt.service has exited. -- -- The process' exit code is 'exited' and its exit status is 217. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'. Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt. -- Subject: A start job for unit zigbee2mqtt.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit zigbee2mqtt.service has finished with a failure. Which strikes me as very odd. Any blindingly obvious things I'm missing? TIA! C
Zigbee
Any thoughts on which is better
CatmanV2C
Obviously a quiet forum, but perhaps it's time I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box. My current set up is as follows: One Debian VM on Synology NAS running: Z-wave Server Open Luup Multi system reactor HA bridge Mosquito MQQT broker This machine has a UZB Z-wave stick connected via the USB port on the NAS Another HAOS VM on the same NAS running HAOS I've got some older Z-wave stuff that I keep around until it fails. I have some Tuya stuff integrated in HA My thought was to get either a SMLIGHT SLZB-06M or an Aqara Hub M2 Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR. Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine. Any thoughts from the assembled experts here? TIA C
Zigbee
Single protocol?
CatmanV2C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh. Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else.... C
General Discussion
HDMI oddness
CatmanV2C
Not really Smart Home stuff, but going to ask as we have smart people... Bear with me on this one. Asking here because of the font of knowledge! For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi. Couple of changes of late: Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct. Everything continues to work Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes. Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote. If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine. This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all? TIA C
General Discussion
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
Oh the joy of pairing
CatmanV2C
When I remember the old days Just added a new Tuya plug (OK so it's cloud) Start to finish, visible in HA and MSR < 30 seconds... C
Vera
Home Assistant Connect ZWA-2 & ZBT-2
therealdbT
Topic thumbnail image
Hardware
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Is there a way to turn this section (image in post) off?
toggledbitsT
Topic thumbnail image
Comments & Feedback
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
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