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. Updated to latest MSR 21243 and no entities are being executed I Hubitat
Need help reducing false positive notifications
T

Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)

- name: "Washing Machine" state: > {% if states("sensor.washer_switch_0_power")|float == 0 %} Off {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} Standby {% else %} Washing {% endif %} icon: > {% if states("sensor.washer_switch_0_power") == "off" %} mdi:washing-machine-alert {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} mdi:washing-machine-off {% else %} mdi:washing-machine {% endif %} minutes: 2

The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.

6774565a-06cc-443f-99c1-e71301b33d83-image.png

What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.

The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.

What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.

I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?

Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0

Multi-System Reactor about 14 hours ago
MQTT configuration question
T

I have the following yaml configuration in local_mqtt_devices file

x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'

While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?

Multi-System Reactor 3 days ago
System Configuration Check - time is offset
F

Hi!

I get this message when I'm on the status tab:

System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.

I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1

I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan

Multi-System Reactor 4 days ago
Programmatically capture HTTP Request action status code or error
T

I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.

While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.

So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.

While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits

Thanks!

Multi-System Reactor 6 days ago
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N

Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945

Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.

I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.

This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.

x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}

The "cold white" and "warm white" settings interfer with the rgb color settings.

Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.

So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have

x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor

In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.

x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33

Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?

x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}

Thanks in advance.

Multi-System Reactor 6 days ago
Problem with simultaneous notifications.
T

Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.

I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.

96b3f7db-ba09-499e-a78c-86903b603857-image.png

36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.

Any idea what could be happening?

Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]

Multi-System Reactor 7 days ago
Problem after upgrading to 25067
R

MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.

Multi-System Reactor 12 days ago
Reactor (Multi-System/Multi-Hub) Announcements
T

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 14 days ago
Global expressions not always evaluated
T

Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.

Consider the following test case:

Screenshot 2025-03-13 at 16.29.42.png

Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.

Screenshot 2025-03-13 at 16.31.43.png

Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).

Multi-System Reactor 14 days ago
[Solved] Local expression evaluation
V

Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...

What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.

Any help would be appreciated

I have the following test rule:

eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png

2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png

Here is the expressioncode:

vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26  and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" end
Multi-System Reactor 24 days ago
[Solved] Runtime error when exiting global reaction that contains a group
S

I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.

The Runtime Error is different in the two browsers
Safari v18.3

@http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

Google Chrome 133.0.6943.142

TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.

I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.

Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks

Multi-System Reactor 27 days ago
Cannot delete Global Expressions
SnowmanS

I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.

I have not created a global expression for some times and just noticed this while doing some clean-up.

I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.

Here's what the log shows.

[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }

Reactor latest-25067-62e21a2d
Docker on Synology NAS

Multi-System Reactor 28 days ago
Local notification methods?
CatmanV2C

Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.

This was prompted by yesterday's fun and games with my ISP.

I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)

I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?

TIA

C

Multi-System Reactor Feb 14, 2025, 5:08 PM
Custom capabilities in MQTT templates
M

Hi,
I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far.
But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter.

So this is what I have in the local_mqtt_devices.yaml

capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int

And this is the template:

templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json

So the speak action should send something like this to topic sonos/cmd/speak

{ "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" }

At startup the MSR seems to be quite unhappy with my configuration:

reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM

This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction.
Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable.

br,
mgvra

MSR latest-25016-d47fea38 / MQTTController [0.2.24293]

Multi-System Reactor Feb 11, 2025, 1:28 PM
[SOLVED]Hass websocket falsely reporting ready on boot??
V

Hi, @toggledbits

I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting.

Here is the sequence of the test case (All time converted to Zulu to match logs):

Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI

From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error.

Here is what I see from the log:

14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready.

Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...).

Questions:

Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas?

Here is the log:

OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?

Multi-System Reactor Feb 10, 2025, 7:45 PM
[SOLVED]Logs permissions for Docker Install
V

Not a big issue simply a request if easily doable.

The MSR logs files inside the container are owned by root witch is fine however, the permissions are very restrictive. I do not know if there is something wrong with my installation but the logs permission are set to 222 (write only). Even if the docker volume is set for Read/Write the log files are retaining these values.

I go around the problem by doing a chmod 777 on all reactor logs but every time there is an MSR log rotation the permissions are set back to 222. So unless the permission are implemented in the container there is no permanent solution to this (that I know of).

I do not know much about Docker container so I do not know what is involved here.

Can the logfiles permission be simply chaged in the container to at least allow "other" read permission?

Could the MSR log rotation routine implement a chmod to set the permission?

Just a small anoyance

Thanks

Multi-System Reactor Feb 8, 2025, 6:05 PM
Button.Since Revisited
SnowmanS

@toggledbits In the MSR documentation, under Standard Capabilities, I noticed that the
button.since attribute was deprecated as of version 22256 and the metadata is the preferred way to access the last-modified time of an attribute.

Am I reading this right? Should I stop using it in my rules?

Thanks

Multi-System Reactor Feb 7, 2025, 2:14 AM
[SOLVED] reactor_inet_check script... and containers
G

When on my bare metal RPi with MSR I had a rule that ran every minute to check Internet status via a script in MSR called reactor_inet_check.sh

I've moved to containerized MSR and see in the instructions that this cannot be run from the container.

The script cannot run within the Reactor docker container. If you are using Reactor in a docker container, the script needs to be run by cron or an equivalent facility on the host system (e.g. some systems, like Synology NAS, have separate task managers that may be used to schedule the repeated execution of tasks such as this).

I've put a script on my container host that calls the reator_inet_check.sh script and it isn't erroring... but I still see the internet status within MSR as null.

Before I go diving down the rabbit hole... should this work?

My cronjob on the proxmox host:
909fe6f0-77fd-4734-80a4-c9e354c910b6-image.png

The contents of msr_internet_check_caller.sh
16337528-cf31-4968-bffe-af1149f7103e-image.png

Multi-System Reactor Feb 6, 2025, 1:05 PM
Catch-all lights rule
G

Background: this is a Windows MSR install I've done for our local pool/amenity center just to run some fans and lights (not my daily driver at home). Install went perfectly fine.

Scenario: I want the lights to go on when it's dark enough (even if during a storm, not just after sunset) so I'm using solarRadiation from my weather station to drive that Trigger. Easy stuff.

Issue: sometimes, someone goes in the office and just starts flipping switches and the result can be lights turned on in the daytime or off at night. I'm trying to create a "catch-all" wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF.

I have the following Reaction built:

b30eab5b-5a14-4a3a-8c9a-47e3e7e53dc3-image.png

I also have this Reaction for opposite, ie the lights find themselves turned off after dark and they will turn themselves back on:

5c6946b1-297c-4eb1-9618-74820979df29-image.png

Here are my two rules:

288cba86-f941-4157-86d9-d8e7487905f7-image.png *NOTE that in my manual testing, ie I turn on the light switch at the incorrect time, when the solarRadiation level changes the Lights ON rule flags and shows as SET. On the next change of solarRadiation it goes back to reset again.

My expectation is that Lights OFF rule should see the lights are on, the solarRadiation is above the set limit, and turn them off. Instead, every other run, the ON rule moves to SET and then reset again on the following run.

Logs appear angry:

[latest-25016]2025-01-26T22:03:31.696Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.712Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.713Z <Engine:INFO> Lights ON<RESET> all actions completed. [latest-25016]2025-01-26T22:03:42.565Z <wsapi:INFO> client "127.0.0.1#3" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:42.753Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:42.754Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:42.790Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:42.839Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#6" authorized [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:48.146Z <wsapi:INFO> client "127.0.0.1#6" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:48.308Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:48.309Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:48.346Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:48.390Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#7" authorized [latest-25016]2025-01-26T22:03:49.412Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:49.413Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:52.734Z <wsapi:INFO> client "127.0.0.1#7" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:52.891Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:52.892Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:52.925Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:52.965Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#8" authorized [latest-25016]2025-01-26T22:03:54.383Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:54.384Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:04:01.590Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25016]2025-01-26T22:04:39.646Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.656Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.663Z <Engine:INFO> Enqueueing "Lights OFF<SET>" (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.665Z <Engine:INFO> Enqueueing "Lights ON<SET>" (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.668Z <Engine:NOTICE> Starting reaction Lights OFF<SET> (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:NOTICE> Starting reaction Lights ON<SET> (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:INFO> Lights ON<SET> all actions completed. [latest-25016]2025-01-26T22:04:39.675Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:04:39.680Z <Engine:NOTICE> ReactionHistory: no entry for [latest-25016]2025-01-26T22:04:39.683Z <Engine:NOTICE> [Engine]Engine#1 entry 256 reaction rule-m6e33ja3:S-1q2f1j0p: [Error] terminated [parent terminating] [latest-25016]2025-01-26T22:04:39.683Z <Engine:CRIT> Error: terminated [parent terminating] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.699Z <Engine:NOTICE> [Engine]Engine#1 entry 254 reaction rule-m6e33ja3:S: [Error] terminated [preempted by rule state change] [latest-25016]2025-01-26T22:04:39.699Z <Engine:CRIT> Error: terminated [preempted by rule state change] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.700Z <Engine:INFO> Enqueueing "Lights OFF<RESET>" (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.704Z <Engine:NOTICE> Starting reaction Lights OFF<RESET> (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.705Z <Engine:INFO> Lights OFF<RESET> all actions completed. [latest-25016]2025-01-26T22:05:48.822Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:05:48.831Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:INFO> Lights ON<RESET> all actions completed.
Multi-System Reactor Jan 29, 2025, 1:47 PM
Throttled problem
wmarcolinW

Hi @toggledbits

I found this very old post that talked about a way to limit device reading to avoid the throttled problem, because it's not a question of logic, it's that the device actually sends a lot of information, in my case the NUT ups installed in HE.

https://smarthome.community/topic/687/flapping-device?_=1737652139854

It mentions engine section of reactor.yaml by setting update_rate_limit, but I looked in the current MSR documentation and I can't find this information, so I don't know if it's still valid, its effect and parameters.

My situation is simple, when I have a UPS problem the NUT is sending dozens of reports per second and then I have the throttled problem. The same rule applies when the power is normal.

This is the rule, and the parameter that fails is the Tripp Lite UPS status.

cf9ddabf-3144-4e5a-80a4-0dc7664b9573-image.png

a813a077-974e-4737-897c-e383085b3d8f-image.png

All error is the same scenario.

[latest-25016]2025-01-23T12:01:32.753Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.756Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.769Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.772Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:32.776Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.780Z <Rule:WARN> UPS On Battery (rule-l4hjuka5 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling> [latest-25016]2025-01-23T12:01:32.781Z <Rule:WARN> UPS Info (rule-l4gheo63 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling... [latest-25016]2025-01-23T12:01:40.757Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.759Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:40.776Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.777Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:40.778Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott>

Thanks.

Multi-System Reactor Jan 29, 2025, 2:51 AM

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

Scheduled Pinned Locked Moved Multi-System Reactor
47 Posts 6 Posters 2.9k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Matteburk
    wrote on Sep 1, 2021, 9:59 PM last edited by
    #1

    After update no entities are being executed in Hubitat..... I can se in Recently Changed Entities that a motion sensor for example is triggered but the rule in it is not getting set
    im I missing something in the update @toggledbits ?

    getting this in msr log:

    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 {
      code: 'MODULE_NOT_FOUND',
      requireStack: [
      '/home/pi/reactor/server/lib/Engine.js',
      '/home/pi/reactor/server/lib/httpapi.js',
      '/home/pi/reactor/app.js'
      ]
      }
    1 Reply Last reply
    0
    • T Offline
      T Offline
      toggledbits
      wrote on Sep 1, 2021, 10:44 PM last edited by toggledbits Sep 1, 2021, 6:46 PM
      #2

      When posting error messages, please don't (a) edit the error message down to what you think is relevant, and (b) not post context for the error -- several lines, ideally a dozen or two at least, before the error occurred.

      Also I need to know what platform you are on (e.g. are you bare metal, docker, etc. -- don't assume I remember from the last discussion we had, whenever that was).

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

      C 1 Reply Last reply Sep 2, 2021, 12:31 PM
      1
      • M Offline
        M Offline
        Matteburk
        wrote on Sep 2, 2021, 4:05 AM last edited by
        #3

        Hi Sorry.. my bad....

        Im on RPi4 with ssd

        2021-09-02T04:01:04.708Z Rule:5:980:Rule.js Rule#rule-koqsgr9w._evaluate() mutex acquired, evaluating
        2021-09-02T04:01:04.709Z Rule:5:984:Rule.js Rule#rule-koqsgr9w update rate is 1/min limit 60/min
        2021-09-02T04:01:04.710Z Rule:5:904:Rule.js Rule#rule-koqsgr9w evaluateExpressions() with 0 expressions
        2021-09-02T04:01:04.712Z 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
          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 {
          code: 'MODULE_NOT_FOUND',
          requireStack: [
          '/home/pi/reactor/server/lib/Engine.js',
          '/home/pi/reactor/server/lib/httpapi.js',
          '/home/pi/reactor/app.js'
          ]
          }
          2021-09-02T04:01:04.715Z Rule:5:980:Rule.js Rule#rule-knhvm6nr._evaluate() mutex acquired, evaluating
          2021-09-02T04:01:04.716Z Rule:5:984:Rule.js Rule#rule-knhvm6nr update rate is 1/min limit 60/min
          2021-09-02T04:01:04.717Z Rule:5:904:Rule.js Rule#rule-knhvm6nr evaluateExpressions() with 0 expressions
          2021-09-02T04:01:04.719Z 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
          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 {
          code: 'MODULE_NOT_FOUND',
          requireStack: [
          '/home/pi/reactor/server/lib/Engine.js',
          '/home/pi/reactor/server/lib/httpapi.js',
          '/home/pi/reactor/app.js'
          ]
          }
        T 1 Reply Last reply Sep 2, 2021, 8:48 AM
        0
        • T Offline
          T Offline
          tunnus
          replied to Matteburk on Sep 2, 2021, 8:48 AM last edited by
          #4

          @matteburk could check this post, although you probably have some other issue

          Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

          T 1 Reply Last reply Sep 6, 2021, 9:25 PM
          0
          • C Offline
            C Offline
            Crille
            replied to toggledbits on Sep 2, 2021, 12:31 PM last edited by
            #5

            Looks like the same issue I'm having in this post which I haven't been able to solve yet.

            1 Reply Last reply
            0
            • J Offline
              J Offline
              Jaggz
              wrote on Sep 2, 2021, 2:30 PM last edited by
              #6

              Had the same issue. Reaction as a group would not fire but entities within the Reaction would when manually selecting them (hit the little play button next to them). Everything else looked normal from a Status perspective (i.e. motion detected sending the rule into green status, etc). I fixed the problem by installing a fresh copy (leaving the reactor-data folder untouched).

              1 Reply Last reply
              0
              • T Offline
                T Offline
                toggledbits
                wrote on Sep 2, 2021, 3:46 PM last edited by
                #7

                Make sure you are on the latest version, and NODE_PATH (environment variable) is defined correctly (how that is done depends on how you run Reactor).

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

                M 1 Reply Last reply Sep 2, 2021, 4:18 PM
                0
                • M Offline
                  M Offline
                  Matteburk
                  replied to toggledbits on Sep 2, 2021, 4:18 PM last edited by
                  #8

                  @toggledbits I run it with Node app.js

                  T 1 Reply Last reply Sep 2, 2021, 4:35 PM
                  0
                  • T Offline
                    T Offline
                    toggledbits
                    replied to Matteburk on Sep 2, 2021, 4:35 PM last edited by
                    #9

                    @matteburk OK. So the direct solution to your problem is to run it this way: NODE_PATH=$(pwd) node app.js

                    You really should be running it from systemd on the RPi, though. The command line startup is only for initial validation and setup, it's not meant to be the way to run MSR long term.

                    In the tools subdirectory, you'll find a file called reactor.service-example. To install MSR under systemd, do the following:

                    1. Copy the above-named file into your /etc/systemd/system directory and rename it to drop the -example part. For example:

                       sudo cp tools/reactor.service-example /etc/systemd/system/reactor.service

                    2. Edit the new file and change the pathnames to match your install directory. Remember that the file is installed in a restricted directory, so you need to use sudo with your editor:

                       sudo nano /etc/systemd/system/reactor.service

                    3. Once you have the file edited with correct names/parameters, stop your existing Reactor process.

                    4. Make systemd aware of the changed configuration file:

                       sudo systemctl daemon-reload

                    5. Start Reactor under systemd:

                       sudo systemctl start reactor

                    If you need to stop Reactor later, that's systemctl stop reactor. You can also restart a running Reactor with systemctl restart reactor.

                    Running Reactor under systemd will automatically restart it if it crashes, and start it up automatically when your RPi boots up.

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

                    M 1 Reply Last reply Sep 4, 2021, 8:40 AM
                    0
                    • M Offline
                      M Offline
                      Matteburk
                      replied to toggledbits on Sep 4, 2021, 8:40 AM last edited by
                      #10

                      @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

                      1 Reply Last reply
                      0
                      • T Offline
                        T Offline
                        toggledbits
                        wrote on Sep 4, 2021, 1:58 PM last edited by
                        #11

                        This is correct. Check /var/log/syslog for startup errors.

                        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
                        0
                        • M Offline
                          M Offline
                          Matteburk
                          wrote on Sep 5, 2021, 7:25 AM last edited by
                          #12

                          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.

                          1 Reply Last reply
                          0
                          • T Offline
                            T Offline
                            toggledbits
                            wrote on Sep 5, 2021, 1:16 PM last edited by
                            #13

                            Looks like you haven't set the User= line correctly in the reactor.service file. It should be the name of the user that owns the directory in which Reactor is installed. While you are at it, check the pathname to the Reactor install (in the WorkingDirectory and Environment keys), and the pathname to the node executable used in the ExecStart key. If you're not sure where your node lives, just type which node on the command line and it will tell you.

                            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
                            0
                            • M Offline
                              M Offline
                              Matteburk
                              wrote on Sep 5, 2021, 1:45 PM last edited by
                              #14

                              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.

                              1 Reply Last reply
                              0
                              • T Offline
                                T Offline
                                toggledbits
                                wrote on Sep 5, 2021, 9:21 PM last edited by
                                #15

                                It looks like it's referring to a different pathname for nodejs than you have configured in the service file. Did you make a change to that value somewhere along the way? If you make any changes to the config file, you need to do sudo systemctl daemon-reload to get systemd to read the updated config file. So the first step is to try sudo systemctl daemon-reload followed by sudo systemctl restart reactor.

                                If that doesn't work, it is reported elsewhere that sudo systemctl daemon-reexec may resolve this (or perhaps simply rebooting the whole system).

                                Then step three, if you're still not successful, is to see if Reactor is logging anything in its own log files.

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

                                M 1 Reply Last reply Sep 6, 2021, 6:17 PM
                                0
                                • M Offline
                                  M Offline
                                  Matteburk
                                  replied to toggledbits on Sep 6, 2021, 6:17 PM last edited by
                                  #16

                                  @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
                                  C 1 Reply Last reply Sep 6, 2021, 6:29 PM
                                  0
                                  • C Offline
                                    C Offline
                                    Crille
                                    replied to Matteburk on Sep 6, 2021, 6:29 PM last edited by
                                    #17

                                    @matteburk Try installing 21200 just to see if you get MSR running again.

                                    M 1 Reply Last reply Sep 6, 2021, 6:39 PM
                                    0
                                    • T Offline
                                      T Offline
                                      toggledbits
                                      wrote on Sep 6, 2021, 6:36 PM last edited by toggledbits Sep 6, 2021, 2:40 PM
                                      #18

                                      The messages in the log you posted indicate that NODE_PATH is incorrectly set, so I now cannot be sure if we're back at your original problem because you have tried to run it from the command line and this log is from that, or if this log is from an attempted systemd startup, which makes no sense because the service file you published earlier sets the environment variable correctly.

                                      I've given you everything you need to get going again. I'm not sure what else to do. You need to figure it out, though, because this is how this and all future builds will be working, and right now, you're the only person I know of that isn't running, so I'm assuming its a local configuration issue and not a package/software issue.

                                      Can you stop any local startup, start again with systemd, and post the startup portion of the log file? I don't want to see the error message again, I need to see all the messages from a Reactor startup under systemd. That will start with the string Reactor <version> starting on <nodejs version> and give me everything up to Startup complete.

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

                                      M 2 Replies Last reply Sep 6, 2021, 6:39 PM
                                      0
                                      • M Offline
                                        M Offline
                                        Matteburk
                                        replied to toggledbits on Sep 6, 2021, 6:39 PM last edited by
                                        #19

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

                                        1 Reply Last reply
                                        0
                                        • M Offline
                                          M Offline
                                          Matteburk
                                          replied to Crille on Sep 6, 2021, 6:39 PM last edited by
                                          #20

                                          @crille tried .....

                                          1 Reply Last reply
                                          0

                                          4/47

                                          Sep 2, 2021, 8:48 AM

                                          topic:navigator.unread, 43

                                          Recent Topics

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            about 14 hours ago
                                            0
                                            2
                                            31
                                          • Help me with a Smart Home Interview – US Participants Needed
                                            I
                                            Ivan_Razin
                                            2 days ago
                                            0
                                            1
                                            31
                                          • MQTT configuration question
                                            T
                                            tunnus
                                            3 days ago
                                            0
                                            11
                                            228
                                          • System Configuration Check - time is offset
                                            G
                                            gwp1
                                            4 days ago
                                            0
                                            8
                                            78
                                          • Programmatically capture HTTP Request action status code or error
                                            T
                                            therealdb
                                            6 days ago
                                            0
                                            3
                                            68
                                          • ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
                                            T
                                            toggledbits
                                            6 days ago
                                            0
                                            9
                                            278
                                          • Problem with simultaneous notifications.
                                            T
                                            tamorgen
                                            7 days ago
                                            0
                                            1
                                            52
                                          • Problem after upgrading to 25067
                                            R
                                            retireditguy
                                            12 days ago
                                            0
                                            4
                                            166
                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            T
                                            toggledbits
                                            14 days ago
                                            5
                                            119
                                            17.0k
                                          • Global expressions not always evaluated
                                            T
                                            tunnus
                                            14 days ago
                                            0
                                            3
                                            124
                                          • [Solved] Local expression evaluation
                                            T
                                            tunnus
                                            24 days ago
                                            0
                                            13
                                            385
                                          • [Solved] Runtime error when exiting global reaction that contains a group
                                            G
                                            gwp1
                                            27 days ago
                                            0
                                            7
                                            559
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          4 out of 47
                                          • First post
                                            4/47
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Unsolved