-
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. -
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?
-
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
[Solved] HASS.OS Install
-
Hi,
Am I correct in assuming that MSR cannot be installed on a pi running HASS.OS?
Thanks.
-
@vezinpi probably doable. I haven't tried it myself, but if you can install either nodejs or docker, you're almost done.
-
Hi,
I am just a regular user with good system understanding but I am not a software person by any means. Therefore, take the following with that in mind.
I feel myself trapped between HASS recommanded install for a Raspberry Pi, and MSR recommanded install. They are not compatible...
HASS recommanded install is using the Home Assistant Operating System, a controlled environment where the user do not have control over the OS. The good point, it is simple, very stable and protected against noice user like me. On the other hand it make it difficult to do anything else like installing MSR. Trough the Portainer Add-On, I manage to install the MSR container and to configure it to see my Vera and HASS devices. The problem is that the configuration is within the container and when we upgrade or remove the container, the configuration is lost.
The fact that the standard MSR container is running just fine (beside the config) means that the configuration is compatible with HASS OS. I understand your approach (not being system dependent like Reactor was with Vera) by providing either a generic container or tar ball but it implies having a device on which we have the control over the OS. Your actual container for Pi is so close from being an official add-on I wonder if it would not worth the effort. I even see a benefit for you when trouble shooting. The Hass OS environment being almost lock, it can become somewhat of a referece when chasing down an issue with MSR. How many problem are due to the user changing something it is not supposed to. The other thing is, how many users out there, like me, are using the Pi image or the Home Assistant BLUE platform.
I have been using (and contributed) Reactor and Virtual switches with my Vera and I definitely want to go that route with MSR and HASS. I will re-install HASS with an alternate method if I have to, but it is not my first choice if I can avoid it. Again, being just a regular user, simplicity is paramount and the HASS image was pretty good. If MSR could be an add-on, it would be fantastic.
For your consideration.
Thanks
-
You are blazing new territory by running under the packaged, container HassOS. But it sounds like you're close.
Generically, docker containers allow you to "mount" a point in the OS' filesystem within the container; this is called a bind mount. This is the mechanism by which the configuration and log files are normally preserved outside the container on all other systems in which MSR docker containers run. In this way, replacement of the container and/or underlying image does not cause data loss (configuration, state, logs, etc.), because the data is no longer stored within the container.
What you need to figure out is how to get the
/var/reactor
directory inside the container mounted to an accessible, persistent location outside the container. For example, you may create a directory in your user home directory/home/username/reactor-data
, and create a bind mount that mounts that directory over/var/reactor
inside the container. Portainer generically allows you to create bind mounts to places in the filesystem, so I assume this is readily possible, but not being familiar with the specifics of how HassOS handles (and more importantly, restricts) its filesystem(s), I can't give you specific guidance. -
Hi again,
Just thought I would provide an update on where I am at. I might also be helpfull to other people.
As you know, I am trying to get the MSR Container work on a Pi-4, configured with the standard HASS operating system (image via balena etcher). Well I finally found a solution to data persistance between reboot. Here is what I did:
-
Installed samba add-on to get accesss to the standard Hass configuration folders
-
Installed Portainer which will be used to install MSR
-
From within Portainer, add an MSR container with the following configuration: image: toggledbits/reactor:latest-raspbian-armv7l, add a TZ variable with the proper region, restart policy define On failure, add a bind volume to map the reactor container /var/reactor to the host /mnt/data/supervisor/homeassistant/reactor. This (reactor) folder will be accessible via the samba addon under the config folder.
-
Restarted the MSR container
The reactor.yaml configuration file is now accessible via samba under homeassistant/config/reactor/config or from a terminal sessison performed from portainer in the var/reactor/config folder.
All seems to work for now. Devices from vera and HASS are being seen by MSR. Configuration persist trough a reboot and I was also able to import (convert using the tool provided) my configuration from Reactor. I am now in the process of making the final adjustment.
Not sure what will the future hold but for now it is working fine.
Many thanks for your work and support.
-
-
In hassos you can install an addon "portainer" and with the needed "settings" you can run your own dockers very easily besides the other containers (of which homeassistant is one).
-
Hi,
That's what I did.See post above. The challenge was to acheive data persistence between reboot, upgrade, etc... Hass OS is pretty tight when it comes to he host file system.
Thanks
-
@vezinpi Have you ran the container and the portainer addon in privileged mode? I have had not trouble in data persistance...
-
- How do I add a TZ-variable? And how do I know how my region (Sweden/Europe) is added?
- My reactions seems to work, but I can't reach the Web UI. The adress in reactor.yaml doesn't work. I also tried the http://127.0.0.1:8111. Can someone point me in the right direction - what adress can it be to reach the Web UI?
Thanks!
-
I don't want to give you bad info, but I believe when you edit a container in Portainer, it actually deletes and publishes the edited one in place.
Check here.
Here are some screen shot from Portainer on my Synology. These are the locations you need to edit for port and TZ.
-
@mikereadington
Thanks!Now it's working!!
-
- SOLVED*
Solved by using Watchtower. Followed this guide:
*OLD POST:
I've been able to update/pull the latest release of MSR a few times within Portainer (running in HA on a HA blue - odroid), but that's not possible anymore.
I only get this message:
I have stopped the MSR as I did before, but nothing seems to help anymore. I have reactor version 21228-05d7497 running, and can't upgrade.
My Portainer version is 2.6.2. Home Assistant is 2021.8.8.
Anyone else having this problem or knows why I can't pull and deploy the latest release?
/Fanan - SOLVED*
-
Your initial problem may have been due to a build error on my part; the build was redone during the course of yesterday and repushed, so that may have had more to do with your success than using WatchTower. You might want to try it the "old" way and see what happens.
-
@Fanan If you are using the HASS.OS then this is a portainer issue in HAAS. See the following link:
Until the problem is resolved in HAAS you will have to install the previous version of the Add-on.
-
@vezinpi Thanks!
I installed alexbelgium repository and his version of Portainer. It was able to update MSR to the latest version (it took a few times with error messages, but then it worked). His version is also 2.6.3. - not 2.6.2. which is the latest available regarding the Portainer add-on i HA. -
Thanks. I will keep that up my sleeve in case HASS fail to address the issue in a timely manner. But for now, the Portainer plugin version 1.5.2 is doing the trick.
-
toggledbits