-
Hello Everyone -
I have a peculiar situation that I'm hoping to get some help with.
Running Vera which is still handling my Zwave, MySensors, Zigbee, and still a balance of my Reactors.
However, I've also been running MSR for several months in preparation for an eventual move off of Vera.
Vera had one of its meltdowns this morning related to my Opensprinkler plug in.
After getting that straightened out, I added the OpenSprinkler plugin to HAAS and that's when I started having issues.
My existing MSR reactors (even simple ones) don't seem to fire their reactions. I can see the conditions go "true". If I manually fire the Reaction, it works fine.
I do see this a lot in the logs:
[1.0.2-21350]2022-05-16T19:02:44.518Z <Rule:INFO> Rule#rule-460 evaluation in progress; waiting for completion(Various rules - 460 is just an example)
Is there anything I can do to further troubleshoot?
-
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. -
My MSR has been working flawlessly until a couple of days ago when it stopped sending Telegram Messages (or should I say they stopped getting through!). I have updated to MSR version 22004. The reactor.log is updating and is showing no errors:
[latest-22004]2022-05-15T17:52:31.417Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:31.417Z Engine:INFO Message Test all actions completed.
[latest-22004]2022-05-15T17:52:31.704Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:31.735Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:31.736Z Engine:INFO Message Test all actions completed.
[latest-22004]2022-05-15T17:52:32.007Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:32.035Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:32.036Z Engine:INFO Message Test all actions completed.
[latest-22004]2022-05-15T17:52:41.324Z Engine:INFO Enqueueing "Variable Telegram Test" (re-kvnm57c3)If I use the following in my web browser the telegram message gets through:
https://api.telegram.org/botxxxxx......./sendMessage?chat_id=xxxxx......&text=Test Message HTTPS
I am running MSR on my QNAP network attached storage. Any assistance would be appreciated.
Just another question...... I would like to post in the HOME HARDWARE VERA section of Smarthome, but I do not have the option to set up a new post. Do I need to request access for this?
-
Details of runtime environment:
Reactor (Multi-hub) stable-22055-9b40e12 Running as a service on Windows Server 2022 Std 21H2 Connecting to HASS (HASSOS) Is a migration WIP from OpenLuup/ReactorA complete description of your objective:
Using LetsEncrypt, application "certifyTheWeb", retrieve and apply SSL certificate to Multi System ReactorA description of your approach/solution/implementation so far:
Reviewed Config files, can't seen mention of certificate files in thereActual Question:
How do I apply a certificate to whatever web server Reactor uses? I'm familiar with managing certificates on IIS and Apache but Reactor doesn't use either of these and I have not been able to locat ethe config file that Reactor uses for this. Which config file needs editing to apply a certificate? Does it use the computer certificate store or it's own store (e.g. pem files)The reason I want to achieve this, other than the general goodness of having everything I can in TLS is that I have Reactor as an IFRAME in my HASS console and as HASS is HTTPS and Reactor is HTTP then the iframe refuses to open.
Search for "certificate" or "ssl" did not reveal anything relevant in this forum.
-
@toggledbits
Hi Patrick,
Running HASS 2022.5.3
MSR zwavejs-22126-834c3e9Seeing weird behavior in MSR with regards to my Zen32's. Not sure how to capture info that might be relevent but will describe what I am seeing.
In the example below I pressed scene 001 4 times. It flashed and changed the primary value to "4". The remaining buttons were previously showing the PV as "double" I pushed each button one time and they flashed and displayed the PV as 4.
zen32.JPGIn the zwavejs2mqtt debug screen that sequence looks like this.
2022-05-10 09:38:44.078 INFO ZWAVE: Node 45: value notification: 91-0-scene-001 5 2022-05-10T16:38:44.081Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x898501" } 2022-05-10 09:38:45.982 INFO ZWAVE: Node 45: value notification: 91-0-scene-002 0 2022-05-10T16:38:45.984Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8a8002" } 2022-05-10 09:38:47.807 INFO ZWAVE: Node 45: value notification: 91-0-scene-003 0 2022-05-10T16:38:47.810Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8b8003" } 2022-05-10 09:38:48.858 INFO ZWAVE: Node 45: value notification: 91-0-scene-004 0 2022-05-10T16:38:48.861Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8c8004" }Let me know what other info you would like me to supply.
I have played around with a bunch of other key stroke combo's and it looks like buttons 2-5 display what ever button 1 is set to.
Have tested this on 4 different ZEN32's and it is same on all. -
Running zwavejs-22118-baab576 in MSR, HASSOS 2022.5.1
Due to an unreported issue in HASS, when I upgraded the 2022.5 yesterday, it dropped ZwaveJS2MQTT from my HASSOS build. Finally got it reinstalled and it appears to be working the way it was previously.
MSR is now showing zwavejs down and in entities, nothing is updating.Seeing this in the logs:
ZWaveJSController#zwavejs ws_open caught [Error]Error: connect ECONNREFUSED 192.168.0.16:3000Are there additional steps needed that are not mentioned in the manual?
At a loss to figure out what is causing issue. -
Hi!
After several tests, restarting the computer where the MSR is, and the MSR itself by Tools > Restart, I have a persistent error in the logs.
32d45bc3-51f8-4718-a113-3381e9d7edf2-image.png
Looking at the global expression (screen below), I see that it is highlighted as an error, however, if I look at two other expressions above that have the same structure, they do not present an error, so I do not think the problem is with the expression's code.
ca8a7867-4ac7-4f9a-9913-15a80da18f05-image.png
This expression uses a group, which validates 4 devices of type door sensor, whether the status is true or false, door open or closed.
"dgc_entrance_open": name: DGC Entrance Open select: - include_entity: - "hubitat>37" - "hubitat>38" - "hubitat>99" - "hubitat>130" filter_expression: > entity.attributes?.door_sensor?.state == trueI also compared it with other groups, the structure is identical.
Looking at the 4 devices in this group, I see that all are active in the MSR, have similar variables, are used in other groups and rules that do not present a problem.
52b099f4-b9c4-46cb-ad3d-c873b09b7e13-image.png
Looking at the log, I understand that it refers to some object that would be null, at which point I am lost on what to actually look at.
[latest-22118]2022-05-02T22:33:11.711Z <Engine:INFO> Reaction Engine starting [latest-22118]2022-05-02T22:33:11.719Z <Engine:INFO> Checking rule sets... [latest-22118]2022-05-02T22:33:11.746Z <Engine:INFO> Checking rules... [latest-22118]2022-05-02T22:33:11.748Z <Engine:INFO> Data check complete; no corrections. [latest-22118]2022-05-02T22:33:11.892Z <Engine:ERR> [Engine]Engine#1: error evaluating expression EntranceOPEN: [ReferenceError]ReferenceError: Invalid scope in reference to member attributes of (object)null [latest-22118]2022-05-02T22:33:11.893Z <Engine:ERR> [Engine]Engine#1: expression: sort(each id in ( getEntity('groups>dgc_entrance_open').attributes.sys_group.members ): getEntity(id).name) [latest-22118]2022-05-02T22:33:11.894Z <Engine:CRIT> ReferenceError: Invalid scope in reference to member attributes of (object)null ReferenceError: Invalid scope in reference to member attributes of (object)null at _run (C:\MSR\reactor\common\lexp.js:1449:31) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1536:38) at _run (C:\MSR\reactor\common\lexp.js:1480:33) at C:\MSR\reactor\common\lexp.js:1283:29 at Array.forEach (<anonymous>) at _run (C:\MSR\reactor\common\lexp.js:1282:28) at run (C:\MSR\reactor\common\lexp.js:1663:22) at Object.evaluate (C:\MSR\reactor\common\lexp.js:1699:20) [latest-22118]2022-05-02T22:33:12.232Z <Engine:NOTICE> Reaction Engine running! [latest-22118]2022-05-02T22:33:12.233Z <Rule:INFO> Rule#rule-kxjp2el2 (Mode DAY) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjp7kc8 (Mode EVENING) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjparz7 (Mode NIGHT) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjpd0d6 (Mode AWAY ∆) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqrcr9 (Mode PARTY) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqyhnu (Mode VACATION ∆) startedFinally, if I return the expression and press the Try This Expression button, it is executed and the error disappears.
102e5013-b9aa-4c26-98f5-1ae545f8897f-image.png
This situation started to occur on the latest version of Reactor 22118, on a Windows 10 Bare Metal installation. Does anyone have a similar scenario?
Sorry for the long post, I tried to document as best as possible to try to identify the problem.
Thanks.
-
Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.
-
I just noticed that the new hotness picked up the entities from when I added an integration temporarily to my Home Assistant and popped a lovely info notice into the Alerts pane.
I know the info is new - but when did MSR suddenly become more real-time with devices being added to hubs? This is great!
-
Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.
This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.
"What changed?"
No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSRI did do a z-wave "repair" last night and am waiting to see if this helps.
Is there any maximum or cap on number of devices that should be included in a Global Reaction?
*Marked as solved as the question asked was answered. The issue persists but the question was answered.
-
I've borked my install of reactor-latest-22118-0f0772c.tar.gz for some reason and am retracing steps. Running npm i --no-save --omit dev prompted to update npm and I did (current version now 8.6.0). Currently, attempts to load via browser/s (Brave and Safari) result in "This site can’t be reached192.168.1.xxx refused to connect." I am still able to SSH into the RPi.
I haven't panicked yet but did just pull my config and storage directories - I believe I read where that's enough for a back-up if a clean install ends up being needed.
So the question of the day: which version of nmp should we be running on for the latest Reactor?
-
I’ve looked and can’t find the answer which concerns me that the answer is obvious and thats why I can't find the answer to this.
I’m new to MSR and this is my first post, so please bare with me 🙂
What I’m trying to do is have a global expression that contains the current time so I can use it in Global reactions as well as Rulesets as part of my syslog messages.
Example of what I’m experiencing:
In Expressions, create a global expression: gMyTOD = strftime("%T %D”)
In Rulesets, in a rule, create a local expression: MyTOD = strftime("%T %D”)In that same rule create a Notify type of Syslog.
Set syslog message to: gMyTOD time is ${{gMyTOD}} and MyTOD time is ${{MyTOD}}
Trigger the rule.The result is that the local expression (MyTOD) contains the correct time but the global expression (gMyTOD) does not update and reflects the wrong time in the final syslog message.
Is there a different approach I should be using?
Thank you in advance for any insight.
-bh
-
Hi!
What's the easiest and most effective way to make this work? Do I ping a few websites every ten minutes or so, or is there a better approch? If I'm going to ping, what URL is recommended?
Once a month or so, my internet access is lost, and I have to cut the power to the router, to restart it. When I'm away this become a problem, so I thought that if I got a zigbee switch (in Home Assistant), problem is solved. But how do I (MSR) know if it's offline?For information, I have a set up with Asus routers, Home Assistent with zigbee-, z-wave and wifi devices (a total of appr. 150) and every of my 60-70 automation is done by MSR.
I run MSR ver. 22080-ae7212f (docker on my Home Assistant blue). HA ver 2022.4.6.
Thanks in advance.
Take care, you all!
/Fanan -
-
So, I have a rule set that it's triggered when a local variable changes. Since it's tied to my solar production, it could change very frequently, so I've just added a reset delay to calm it down, but it's not working as intended.
What I really need is a way to, let's say, define a percentage and define a variable to understand if the new value has changed +/- 10% before going true.
I've tried a couple of ways, but I'm posting here anyway, in case anyone has found a better way to tackle this. Thanks!
-
Perhaps a dumb question. Can I check from Home Assistant that MSR is up and running? I would like to see that in a status page in HA. I can of course ping the other Pi but it doesn't say anything about the MSR status.
-
@toggledbits Is there a way to get Current Alerts as an entity so I could monitor those and send notifications if needed.
My usecase is sometimes openLuup crashes and MSR picks that up pretty quick, sending a pushover notification to me would get my attention to restart it.
Of course there are many ways to monitor connectivity but since MSR already is doing that it would be neat to take advantage of it. -
Hey @toggledbits.
From the docs:You cannot control the state of rules via MQTT. Rule state is driven exclusively by the result of its conditions.
And I'm OK when rules are triggered by something else, but I've built a couple of rules to be used by other rules, to streamline the logic, and it'll be useful to invoke a rule via MQTT. It's probably close to what rule/:id/restart is doing in the HTTP api.
Thanks!
-
I'm trying to create some automation so I can control my pool variable speed pump from reactor rather than iAqualink (which sucks). My controller is MQTT enabled so I created several scripts for my desired speeds. (I know reactor has MQTT ability but honestly I read the docs and could not make much sense of it and since I already have it set up in Home Assistant, I figured I would just leverage that instead)
So I created all of my scripts and tested them, they worked perfectly. The I created a rule in reactor and set running the script as the action. The problem is that reactor is telling me that I have to make a selection. I try to click the dropdown and there is nothing to select. I cant save the rule, the only option is to exit.
9e0a3147-5058-4893-9860-2f0d759dfe3c-image.png
Here is my script in Home Assistant. Any advice on how to get this to work? If I am looking at this the wrong way I am open to suggestions (I would rather be able to call a specific action and specify a speed value but I cannot figure out how to do that). Thanks in advance.
-
Hi, I've been using msr for a while now and haven't had timezone issues until today when I updated to latest docker image (latest-22080-ae7212f)
both docker date command and my local date command show the same time, same timezone, but for some reason MSR shows the host time as 2 hours in the past as a result all my timed rules run 2 hours late.
my locale is set correctly in the host machine and is bound into the container as well.
One possible hint I get is maybe this from the container startup log, but other than timezone stuff everything else seems to be working fine and all my settings loaded up just fine.
[latest-22080]2022-04-07T07:52:52.423Z <SystemController:null> Module SystemController v22080 root {} CommonJS loading [latest-22080]2022-04-07T07:52:57.236Z <Engine:CRIT> SyntaxError: Unexpected end of JSON input SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:121:46) at Container.getDataObject (/opt/reactor/server/lib/Container.js:102:53) at new GlobalExpression (/opt/reactor/server/lib/GlobalExpression.js:105:179) at Function.getInstance (/opt/reactor/server/lib/GlobalExpression.js:123:89) at /opt/reactor/server/lib/Engine.js:1349:67 at Array.forEach (<anonymous>) at Engine.initializeGlobalExpressions (/opt/reactor/server/lib/Engine.js:1345:145) at Engine.start (/opt/reactor/server/lib/Engine.js:590:285) at /opt/reactor/app.js:362:103Let me know if I can provide further info to help debug this.
Thanks
How to auto start on Rpi reboot ?
-
Hi
Do we have any instructions yet to follow for auto starting the MSR service on a Raspberry Pi after its rebooted?
Thanks
-
Assuming you are running on raspbian as a systemctl service, shouldn't enabling it do it?
sudo systemctl enable msr.service
Maybe you didn't create a service yet?
-
Yes its Raspbian.
I haven't created or done anything yet.
I am running MSR currently by using this command:
nohup ./app.sh &
Which I am running by using Putty on my Windows 10 laptop.
-
If such is the case, create the service by creating the file
using putty logged in to your rpi:
sudo nano /etc/systemd/system/msr.service
paste in the following file content make sure the path to msr below is correct and change it if necessary:
[Unit] Description=Multi System Reactor After=network.target [Service] Type=simple ExecStart=nohup /home/user/msr/app.sh Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target
Hit ctrl+o then ctrl+x to save and exit from nano.
reload the service daemon:
sudo systemctl daemon-reload
then enable the service
sudo systemctl enable msr
You can then start and top the service with the two commands:
sudo systemctl start msr sudo systemctl stop msr
-
In Nano it says [ Error writing /etc/systemd/system/msr.service: Permission denied ] when trying to save the file.
I then tried this instead:
sudo nano /etc/systemd/system/msr.service
And it saved and I now have a file called msr.service in that directory.
After this command
sudo systemctl enable msr
It says
Failed to enable unit: Invalid argument
-
-
This was the contents of the msr.service file.
I had to change the path slightly.
[Unit] Description=Multi System Reactor After=network.target [Service] Type=simple ExecStart=nohup /home/pi/Documents/reactor/app.sh Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target
-
I would add
User=pi
at a minimum to the service section.I have concerns about the stop action. Investigating...
-
Thanks, I did miss the sudo for the nano command to create the file.
The path does look suspicious too in addition to @toggledbits input. There may be other specificities about raspbian I may be missing.
-
I made a mistake in the msr.service file. Corrected and now the "sudo systemctl enable msr" command runs with no error.
I then rebooted the Pi but some time later I still cannot load MSR in the browser.
-
This is the contents of the msr.service file now
[Unit] Description=Multi System Reactor After=network.target [Service] User=pi Type=simple ExecStart=nohup /home/pi/Documents/reactor/app.sh Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target
-
can you show the error by posting the output of
sudo systemctl status msr
-
There are several things to indicate that the process is not ready for this at this point. Among them is that the nodejs installation done by the installer is local to the
pi
user. There are also issues with the home directory, and the search paths for modules and data relative to the current working directory vs the path of the application.Too soon. Not ready yet. Not going to fix it tonight. This is prelease software. It isn't mean to run like production software at this point.
-
Think I have it working now and MSR is auto starting after a reboot
I placed my msr.service file in this directory:
/home/pi/Documents/reactor
Using WinSCP, on the msr.service file properties, I made its Group and Owner to be pi rather than root.
This is the files contents:
[Unit] Description=Multi System Reactor After=network.target [Service] Type=simple ExecStart=nohup ./app.sh & WorkingDirectory=/home/pi/Documents/reactor Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target
I then ran these commands in the terminal in Putty:
sudo systemctl enable /home/pi/Documents/reactor/msr.service
sudo systemctl start msr
And I can check its status with this command:
sudo systemctl status msr
It says its active and running.
If I reboot the Pi now after the reboot the MSR web page is then available and can be accessed.
-
Yeah, but running the shell script is not correct. You're basically having systemd do what the shell script is also doing (restarting when stopped), and it's going to cause problems. Your exec is also forking, so adding yet another layer of indirection that all but guarantees that systemd is going to be looking at the wrong process ID for what it thinks is a running Reactor. That could lead to problems stopping and restarting, and with the possible effect that an incorrect stop causes data loss.
-
Didn't think I'd set it up correctly
More of a hack to get it auto started.
-
You're not far off, really, but the devilish details require some internal knowledge of how Reactor starts and organizes itself, and it's made a bit more complicated by the necessity to locate things "off shore" for docker containers and make sure that stays working as well. There's a bit of a balancing act there. As I'm sure you know well, features are not strictly governed by their ability to be implemented; they are also very much a function of what it takes to support them. I'd rather there be an "official" way that I know people use, because if ten people do it their own way, I'll have ten different ways I need to figure out any time there's a problem.
-
Can I ask what data one could loose in a power outage? I presume that any setup (rules/expressions) change is written to persistent files on "save"?
-
Right now, all data is written when modified, but that may not always be the case, and there's a high likelihood it will be user-configurable, even.
One of the things designed in is that MSR is "crappy-storage-ready". @rafale77 can tell you at length about the merits and woes of various storage technologies, and an SD card in a Raspberry Pi is no exception (in fact, probably both a good example and a dire warning). MSR has a storage architecture for its data that allows "pluggable" storage disciplines, so you could, for example, choose a cached-with-delayed-write-back mechanism to reduce wear, and you could choose that for everything, or just states, or states and logs, etc. So in that case, as the system shuts down, it is necessary for the cache to write back any "dirty" (modified but unsaved as yet) data, or the modifications would be lost.
That said, you should be thinking about getting your Pi off an SD card if that's what you're running, if you intend to run it full-time with MSR and depend on it. There are only two types of SD cards: those that have failed, and those that are about to. I have my Pi running on a cheap 2.5" SSD, and it's also a good bit faster, although there is some alchemy to getting that working, and while it's much better than it was, it involves some pretty magical incantations still today and can be a bit angst-inducing.
-
With the newer firmwares to the RPi it is fairly straight forward to use a SSD since it has native support now. Not that much alchemy anymore.