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
MQTT configuration question
tunnusT

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
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
Programmatically capture HTTP Request action status code or error
therealdbT

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
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
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
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
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT

Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Global expressions not always evaluated
tunnusT

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
[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
[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
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
Advice on Storing and Backing Up Bind Mounts - Docker
PablaP

Hello all, after seeing Catman's posts about their disaster recovery and move to Docker I took that as a sign to migrate everything (aside from HA) to Docker. After a small learning curve I had Docker+Portainer up and running in a few days.

Instead of using named Volumes I opted to use Bind Mounts so I can easily edit conf files and any other file needed. I do understand the nuances that come with bind mounts, such as migration to a different host may require changing file structures, the possibility of someone editing the bind mount files and permissions but to me those aren't too big of a deal.

My question is what is the best way to keep a back up of these bind mounts? I currently have them stored in the /etc directory in another directory named on a per container basis. I was thinking to move it all to a /home/user/docker/ directory so that I can use a simple cp command to my mounted SMB share to backup all the container data files. Anyone else do it differently?

Side note: I finally got to flex the benefits of Docker with updating Reactor.. it was dead simple. I had no idea what I was missing out on lol!

Software
Disaster recovery and virtualisation
CatmanV2C

Following on from my last thread, some progress has been made over the weekend.

With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.

Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.

Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.

Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.

Once that hurdle is sorted I'm torn between:

Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)

Decisions, decisions.

C

General Discussion
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
RFC: When disaster strikes (sorry it's a bit verbose)
CatmanV2C

Hi everyone. Thanks for all your input recently on the topic of local notifications. I think we got some really interesting solutions 🙂

Back to more prosaic matters. Most of you will know that I've been messing around with this stuff for some years. My last major change was when I migrated from Vera, which was something like 4-5 years ago.

While my system has grown, it's not really altered very regularly, although I try to keep most of it kind of up to date.

Current set up:
Intel NUC that runs:
Bare metal install of Debian
Z-way server with Z-wave.me USB stick
Openluup
Altui
Multi system reactor
HA Bridge
Mosquito

Raspberry Pi
Running Home Assistant

About 40 varied Z-wave and Wifi devices

I also have a Synology DS224+ which may inform some responses.

Home Assistant recovery is pretty simple. I get a full backup of the system every night dumped onto my SAN and I know from experience that it would simply be a case of booting up a new install and feeding it the backup.

The NUC on the other hand....
Coming from a commercial IT world, I am becoming more and more conscious that I don't really feel I have a suitable disaster recovery plan, and my core system is running on hardware heading for 10 years old.

My initial thought, which I've kept putting off as it's awkward would be to grab a nice SSD, reboot the NUC into Mint or something similar and simply do a dd copy onto a new drive. I can get a replacement NUC on ebay simply enough, and keep it in a cupboard if anything other than the hard drive fails on the existing one, but this feels rather like a stop gap. However one immediate question:

If I had to use the replacement NUC would all the Z-wave devices simply carry on talking to the stick, or would they all need to be re-paired?

How easy would it be to move everything the NUC does (as a start) onto the NAS? Create a VM and clone the disc onto it?

Should I move to Docker? Something else?

What are the hive mind's thoughts?

Apologies if we've done this before, but while it all just works...

Cheers!

C

General Discussion
AltUI sans internet connection
CatmanV2C

Morning world. Looking for some thoughts on recent experience 🙂

Yesterday my ISP had something of a catastrophic failure (in theory not yet fixed but seems OK for now)

While this is annoying for several reasons, one thing that I wasn't expecting was for AltUI to become pretty much un-usable.

Unless I have a tab already open and active, connecting to the Home page is pretty much random / impossible, just presenting with a white page and (sometimes) 'Waiting for initial data' on the bottom. Everything works (i.e. where I have controllers or Reactions I can trigger, they function flawlessly) it's just something of a pain since 99.9% of my control is via Alexa now, and not being able to access devices in AltUI makes things like turning some lights of a bit tricky 😉

I suspect that this is due to AltUI trying to pull licence info and Weather data, and failing. What I should do is probably access the OpelLuup console direct and see if that works better in future.

Does that make sense to anyone, or am I completely off track?

Cheers

C

Software
Eachen No Neutral smart wall switch to lights and Sonoff Mini R4 switch for LEDs
R

Hi all. First post so please be gentle.

I have an Eachen two-gang smart wall switch wired no neutral (with capacitor) connected to existing bathroom lights which works perfectly. It's also wired to a Sonoff Mini R4 Extreme connected to LED lights. I want the LED lights to switch on when the bathroom lights switch on (and vice versa). The Mini R4 works separately on my phone via Ewelink as well as on the Mini R4 itself (physical button). The switch is installed inside the wall and the rest of the components are in the ceiling / attic / roof cavity. The Mini R4 is set to Edge switch mode which works in my example I wired.

How I wired it:

cb919874-6933-460a-8cd0-f063bac88674-image.png

I have a video showcasing the example I wired today works. I could share it if required. Ignore the white cable. I only used it to power the example.

77ebbc23-83de-48ee-a4bf-247bfd24f121-image.png

3827ede6-cf5c-47aa-8fdb-c75470101c4a-image.png

The wiring diagram I used for the mini R4.

485de912-e656-4da3-b6f6-81cb076e0261-image.png

I wired it together with the existing lights of the bathroom so that L1 switches on both the Mini R4 and the bathroom lights:

a3ea5c93-a9ae-4aaf-8dce-24018bcdb4d1-image.png

This is the wiring diagram for the Eachen switch:
b867a3c7-c1ac-428c-a90f-7f0f4b62a609-image.png

The Eachen's first gang (L1) doesn't trigger the Mini R4 in any way.

Any help or advice will be much appreciated.

Thanks,
R

General Discussion
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
[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
[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
About
Posts
88
Topics
13
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

  • 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!

  • 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:~ $

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

  • 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

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

  • 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.
  • 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!

  • 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
  • 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:~ $

  • 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

  • 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

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

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

    @crille tried .....

  • 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... 🙂

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

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

  • 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

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

    @toggledbits I run it with Node app.js

  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved