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. Multi-System Reactor Developer Preview AVAILABLE
Organizing/ structuring rule sets and rules
R

Hi guys,

Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.

Maybe there are better ways to organize my rule sets.

I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.

Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT

I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.

Screenshot 2025-04-06 201446.png

My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)

I have probably done something stupid or missed a step but I am stuck.

Thanks for any help.

Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M

Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?

Also the landing page after login is empty and seems be have some JS issues on the dev console:

Screenshot from 2025-04-07 18-06-19.png

fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png

Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)

br,
mgvra

Multi-System Reactor
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
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
Deleting widgets
tunnusT

Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266

Multi-System Reactor
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
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
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
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

Multi-System Reactor Developer Preview AVAILABLE

Scheduled Pinned Locked Moved Multi-System Reactor
124 Posts 12 Posters 22.4k 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.
  • MatohlM Offline
    MatohlM Offline
    Matohl
    wrote on last edited by
    #2

    Up and running on my my RPi 4 with SSD. Will continue tomorrow with adding my Veras

    1 Reply Last reply
    1
    • toggledbitsT Away
      toggledbitsT Away
      toggledbits
      wrote on last edited by
      #3

      Nice. Any issues with the install?

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

      MatohlM 1 Reply Last reply
      0
      • ElcidE Offline
        ElcidE Offline
        Elcid
        wrote on last edited by
        #4

        Ok system up and running under termux on android 8.

        Some error in start up console log

        Tried first reactor rule and reaction, seems fast.
        reaction to set dimming does not work but on and off do.

        Would you prefer this to be logged in bug tracker or here.

        toggledbitsT 1 Reply Last reply
        0
        • K Offline
          K Offline
          kfxo
          wrote on last edited by kfxo
          #5

          Got it up an running and connected both openluup and home assistant. Noticing that if category_num attribute is not set in openluup then it does not recognize supported commands for the device. I'm guessing Reactor relies on this attribute?

          edit. updated Z-way plugin to latest which now provides category_num and issue is resolved

          1 Reply Last reply
          0
          • ElcidE Offline
            ElcidE Offline
            Elcid
            wrote on last edited by
            #6

            Ok the dimming is 0 to 1 , that threw me. So 5% is 0.05.

            1 Reply Last reply
            0
            • toggledbitsT Away
              toggledbitsT Away
              toggledbits
              replied to Elcid on last edited by
              #7

              @elcid said in Multi-System Reactor Developer Preview AVAILABLE:

              Some error in start up console log

              Known error, it already has a PR, and is already fixed for the next build. That's just the preloader that I use to pull in data for testing. I'm usually looking at the end of the log, not the beginning, so I missed it before packaging the release. 🙂

              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
              • K Offline
                K Offline
                kfxo
                wrote on last edited by
                #8

                Some first impressions. Having all home assistant and openluup entities together in a Reactor interface is a game changer. Install was super easy and went smoothly following the directions. Installed on a Debian10 VM. Looks like just about every entity from both systems were discovered. Performed a couple test rules with a HA entity being controlled based the state of an openluup entity and it was very responsive. Having trouble with the import tool, keep getting a syntax error. Definitely going to miss Run_Lua actions. Is there plans for anything to replace that? All and all looking great.

                toggledbitsT 1 Reply Last reply
                0
                • Black CatB Offline
                  Black CatB Offline
                  Black Cat
                  wrote on last edited by
                  #9

                  I'm stuck...(surprised I made it this far..):)
                  Uploaded and expanded OK...but there is no config/reactor.yaml file to edit.

                  aka Zedrally

                  toggledbitsT 1 Reply Last reply
                  0
                  • toggledbitsT Away
                    toggledbitsT Away
                    toggledbits
                    replied to Black Cat on last edited by
                    #10

                    @black-cat said in Multi-System Reactor Developer Preview AVAILABLE:

                    Uploaded and expanded OK...but there is no config/reactor.yaml file to edit.

                    If you're using a Pi, you should have run the install script in the tools directory, which copies the files from dist-config to config. If you are installing on other Linux, there's a step in the instructions to do the copy manually. But that's all you need to do: cp dist-config/* config/

                    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
                    • toggledbitsT Away
                      toggledbitsT Away
                      toggledbits
                      replied to kfxo on last edited by
                      #11

                      @kfxo said in Multi-System Reactor Developer Preview AVAILABLE:

                      Having trouble with the import tool,

                      Can you paste some output? Let's have a look at that...

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

                      K 1 Reply Last reply
                      0
                      • K Offline
                        K Offline
                        kfxo
                        replied to toggledbits on last edited by
                        #12

                        @toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:

                        @kfxo said in Multi-System Reactor Developer Preview AVAILABLE:

                        Having trouble with the import tool,

                        Can you paste some output? Let's have a look at that...

                        I posted an issue on MantisBT but maybe I did it wrong. Should I try there again?

                        toggledbitsT 1 Reply Last reply
                        0
                        • toggledbitsT Away
                          toggledbitsT Away
                          toggledbits
                          replied to kfxo on last edited by toggledbits
                          #13

                          @kfxo said in Multi-System Reactor Developer Preview AVAILABLE:

                          I posted an issue on MantisBT but maybe I did it wrong. Should I try there again?

                          Good on ya! I see it...

                          OK. Easy enough. Not sure how that snuck by... Probably the easiest is to have you just open it in a text editor, find the line (192) that says case 'interval': { and just remove that curly brace from the end of it. Save, and try again.

                          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
                          • MatohlM Offline
                            MatohlM Offline
                            Matohl
                            replied to toggledbits on last edited by
                            #14

                            @toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:

                            Nice. Any issues with the install?

                            Yes, but only due to myself. Following your instructions it went well 🙂 Will continue the testing later today ...

                            1 Reply Last reply
                            0
                            • cw-kidC Offline
                              cw-kidC Offline
                              cw-kid
                              wrote on last edited by cw-kid
                              #15

                              Linux Neanderthal here, I tried to install it on my Raspberry Pi2.

                              I got this output not sure what it means, it says I need to commit some file?

                              The version of nodejs currently installed is v12.20.1 (compatible).
                              Checking dependencies...
                              
                              > bufferutil@4.0.3 install /home/pi/Documents/reactor/node_modules/bufferutil
                              > node-gyp-build
                              
                              
                              > utf-8-validate@5.0.4 install /home/pi/Documents/reactor/node_modules/utf-8-validate
                              > node-gyp-build
                              
                              
                              > core-js@3.9.0 postinstall /home/pi/Documents/reactor/node_modules/core-js
                              > node -e "try{require('./postinstall')}catch(e){}"
                              
                              Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
                              
                              The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
                              > https://opencollective.com/core-js
                              > https://www.patreon.com/zloirock
                              
                              Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
                              
                              npm notice created a lockfile as package-lock.json. You should commit this file.
                              npm WARN bootstrap@4.5.3 requires a peer of popper.js@^1.16.1 but none is installed. You must install peer dependencies yourself.
                              
                              added 86 packages from 68 contributors and audited 87 packages in 46.342s
                              
                              4 packages are looking for funding
                                run `npm fund` for details
                              
                              found 0 vulnerabilities
                              
                              OK. Now please LOG OUT, then log back in and continue the installation procedure
                              (see docs/markdown/Installation.md or docs/html/Installation/index.html).
                              
                              

                              The installation Guide here then says to:

                              "Edit the file config/reactor.yaml and, on the line beginning baseurl:, replace the IP address with the actual primary IP address of your system."

                              There is a "config" folder present but it is empty.

                              c194b3a1-2387-4c2c-b195-a5cc5e88ec29-image.png

                              There is a folder called /home/pi/Documents/reactor/dist-config and the reactor.yaml file was in there, so I edited that one and added my Pi's IP address.

                              8c393858-0bac-4df6-b63f-04f94cb43baa-image.png

                              I actually didn't even have a "Documents" folder to begin with, I had to create that folder first in this path: /home/pi/Documents

                              It then says to:

                              "Start up Reactor: node app.js"

                              Looks like there were some errors during startup.

                              pi@raspberrypi:~/Documents/reactor $ node app.js
                              2021-02-19T09:18:37.424Z <app:null> Reactor application v21047 starting on v12.20.2
                              2021-02-19T09:18:37.641Z <Controller:null> Module Controller v21046
                              2021-02-19T09:18:37.643Z <default:null> Module Structure v21025
                              2021-02-19T09:18:37.692Z <default:null> Module Ruleset v21041
                              2021-02-19T09:18:37.694Z <default:null> Module Rulesets v21041
                              2021-02-19T09:18:37.825Z <default:null> Module Rule v21047
                              2021-02-19T09:18:37.868Z <default:null> Module Engine v21047
                              2021-02-19T09:18:37.910Z <default:null> Module httpapi v21041
                              2021-02-19T09:18:37.924Z <default:null> Module httpproxy v20350
                              2021-02-19T09:18:38.093Z <default:null> Module wsapi v21041
                              2021-02-19T09:18:38.246Z <default:CRIT> Error: ENOENT: no such file or directory, open './server/struct_data.json'
                              Error: ENOENT: no such file or directory, open './server/struct_data.json'
                                  at Object.openSync (fs.js:462:3)
                                  at Object.readFileSync (fs.js:364:35)
                                  at Structure.start (/home/pi/Documents/reactor/server/lib/Structure.js:184:49)
                                  at /home/pi/Documents/reactor/app.js:141:72
                                  at processTicksAndRejections (internal/process/task_queues.js:97:5)
                              Error: ENOENT: no such file or directory, open './server/struct_data.json'
                                  at Object.openSync (fs.js:462:3)
                                  at Object.readFileSync (fs.js:364:35)
                                  at Structure.start (/home/pi/Documents/reactor/server/lib/Structure.js:184:49)
                                  at /home/pi/Documents/reactor/app.js:141:72
                                  at processTicksAndRejections (internal/process/task_queues.js:97:5) {
                                errno: -2,
                                syscall: 'open',
                                code: 'ENOENT',
                                path: './server/struct_data.json'
                              }
                              2021-02-19T09:18:38.479Z <default:null> Module SystemController v21025
                              2021-02-19T09:18:38.537Z <app:null> Waiting 10 seconds before starting Engine
                              
                              

                              Will Reactor be started automatically after you reboot the Pi ?

                              Answer = NO

                              "I haven't fully daemon-ized Reactor yet while still in test mode, but eventually it will, of course, be available for startup at boot time."

                              Anyway I have the Reactor up and running it seems, I can access it in the web browser.

                              I then edited the reactor.yaml file and added my location details and the IP for my Vera hub. However after restarting MSR I had nothing listed in Entities other than Reactor System.

                              I had to copy the reator.yaml file from this folder to this folder and then it worked.

                              /home/pi/Documents/reactor/dist-config

                              to

                              /home/pi/Documents/reactor/config

                              7d1640c6-6b9a-4975-8900-3a5a2c41c109-image.png

                              I can now see my Vera device and scenes listed under Entities

                              Thanks

                              cw

                              toggledbitsT 1 Reply Last reply
                              0
                              • cw-kidC Offline
                                cw-kidC Offline
                                cw-kid
                                wrote on last edited by cw-kid
                                #16

                                Will this work for Conditions ?

                                Vera is not in either Away mode (2) or in Vacation mode (4)

                                f277d2cd-c524-418b-89e5-ebd897a86c8e-image.png

                                or like this ?

                                16a5608e-983f-46a5-b758-3b8976ef5814-image.png

                                Or some other way?

                                Thanks

                                toggledbitsT 1 Reply Last reply
                                0
                                • toggledbitsT Away
                                  toggledbitsT Away
                                  toggledbits
                                  replied to cw-kid on last edited by
                                  #17

                                  @cw-kid said in Multi-System Reactor Developer Preview AVAILABLE:

                                  There is a "config" folder present but it is empty.

                                  Just copy the files from dist-config to config manually. Reactor won't read config files unless they are in config.

                                  The startup error can be ignored; it's for loading test data, which isn't present.

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

                                  1 Reply Last reply
                                  1
                                  • toggledbitsT Away
                                    toggledbitsT Away
                                    toggledbits
                                    replied to cw-kid on last edited by toggledbits
                                    #18

                                    @cw-kid said in Multi-System Reactor Developer Preview AVAILABLE:

                                    Vera is not in either Away mode (2) or in Vacation mode (4)

                                    Reactor's "House Mode" entity uses words: home, away, night, vacation. Note what is showing for "Current value" underneath the condition. You can also see this in the Entities list.

                                    EDIT: Also, can we please start threading discussions in this category? It's going to get unruly fast if everyone is talking about everything as replies to one thread.

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

                                    cw-kidC 1 Reply Last reply
                                    1
                                    • cw-kidC Offline
                                      cw-kidC Offline
                                      cw-kid
                                      replied to toggledbits on last edited by cw-kid
                                      #19

                                      @toggledbits

                                      Hi

                                      Thanks for the reply.

                                      I have used the words "away" and "vacation". However when I see this summary it says null or no data for the house mode triggers (conditions).

                                      d2021b2b-33c7-417c-9fc9-dad78eb49f38-image.png

                                      So don't think its working.

                                      EDIT:

                                      Using "Does not contain" rather than "not in" looks better ?

                                      186878ad-3ea1-41bf-a86a-9e702efd0f8f-image.png

                                      1 Reply Last reply
                                      0
                                      • toggledbitsT Away
                                        toggledbitsT Away
                                        toggledbits
                                        wrote on last edited by
                                        #20

                                        That's an unexpected difference. Equals and not equals would also be applicable here.

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

                                        cw-kidC 1 Reply Last reply
                                        0
                                        • cw-kidC Offline
                                          cw-kidC Offline
                                          cw-kid
                                          replied to toggledbits on last edited by cw-kid
                                          #21

                                          @toggledbits In PLEG not equals is != I'm assuming <> is not equals in MSR. I'll change it to that as its better than "does not contain".

                                          1 Reply Last reply
                                          0

                                          Recent Topics

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            540

                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            245

                                          • Organizing/ structuring rule sets and rules
                                            G
                                            gwp1
                                            0
                                            5
                                            318

                                          • Moving MSR from a QNAP container to RP 5 - some issues
                                            G
                                            gwp1
                                            0
                                            5
                                            277

                                          • Widget deletion does not work and landing page (status) is empy
                                            G
                                            gwp1
                                            0
                                            4
                                            251

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            441

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            120
                                            35.1k

                                          • Deleting widgets
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            427

                                          • MQTT configuration question
                                            tunnusT
                                            tunnus
                                            0
                                            11
                                            574

                                          • System Configuration Check - time is offset
                                            G
                                            gwp1
                                            0
                                            8
                                            550
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login

                                          • Don't have an account? Register

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