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
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?
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!
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: currentColorIn 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=33Is 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.
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]
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.
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.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?).
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" endI 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
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
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
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
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: intAnd 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: jsonSo 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 AMThis 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]
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 GUIFrom 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?
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
@toggledbits In the MSR documentation, under Standard Capabilities, I noticed that the
button.since attribute was deprecated as of version 22256 and the metadata is the preferred way to access the last-modified time of an attribute.
Am I reading this right? Should I stop using it in my rules?
Thanks
When on my bare metal RPi with MSR I had a rule that ran every minute to check Internet status via a script in MSR called reactor_inet_check.sh
I've moved to containerized MSR and see in the instructions that this cannot be run from the container.
The script cannot run within the Reactor docker container. If you are using Reactor in a docker container, the script needs to be run by cron or an equivalent facility on the host system (e.g. some systems, like Synology NAS, have separate task managers that may be used to schedule the repeated execution of tasks such as this).
I've put a script on my container host that calls the reator_inet_check.sh script and it isn't erroring... but I still see the internet status within MSR as null.
Before I go diving down the rabbit hole... should this work?
My cronjob on the proxmox host:
909fe6f0-77fd-4734-80a4-c9e354c910b6-image.png
The contents of msr_internet_check_caller.sh
16337528-cf31-4968-bffe-af1149f7103e-image.png
Background: this is a Windows MSR install I've done for our local pool/amenity center just to run some fans and lights (not my daily driver at home). Install went perfectly fine.
Scenario: I want the lights to go on when it's dark enough (even if during a storm, not just after sunset) so I'm using solarRadiation from my weather station to drive that Trigger. Easy stuff.
Issue: sometimes, someone goes in the office and just starts flipping switches and the result can be lights turned on in the daytime or off at night. I'm trying to create a "catch-all" wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF.
I have the following Reaction built:
b30eab5b-5a14-4a3a-8c9a-47e3e7e53dc3-image.png
I also have this Reaction for opposite, ie the lights find themselves turned off after dark and they will turn themselves back on:
5c6946b1-297c-4eb1-9618-74820979df29-image.png
Here are my two rules:
288cba86-f941-4157-86d9-d8e7487905f7-image.png *NOTE that in my manual testing, ie I turn on the light switch at the incorrect time, when the solarRadiation level changes the Lights ON rule flags and shows as SET. On the next change of solarRadiation it goes back to reset again.
My expectation is that Lights OFF rule should see the lights are on, the solarRadiation is above the set limit, and turn them off. Instead, every other run, the ON rule moves to SET and then reset again on the following run.
Logs appear angry:
[latest-25016]2025-01-26T22:03:31.696Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.712Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.713Z <Engine:INFO> Lights ON<RESET> all actions completed. [latest-25016]2025-01-26T22:03:42.565Z <wsapi:INFO> client "127.0.0.1#3" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:42.753Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:42.754Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:42.790Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:42.839Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#6" authorized [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:48.146Z <wsapi:INFO> client "127.0.0.1#6" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:48.308Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:48.309Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:48.346Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:48.390Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#7" authorized [latest-25016]2025-01-26T22:03:49.412Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:49.413Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:52.734Z <wsapi:INFO> client "127.0.0.1#7" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:52.891Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:52.892Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:52.925Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:52.965Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#8" authorized [latest-25016]2025-01-26T22:03:54.383Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:54.384Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:04:01.590Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25016]2025-01-26T22:04:39.646Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.656Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.663Z <Engine:INFO> Enqueueing "Lights OFF<SET>" (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.665Z <Engine:INFO> Enqueueing "Lights ON<SET>" (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.668Z <Engine:NOTICE> Starting reaction Lights OFF<SET> (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:NOTICE> Starting reaction Lights ON<SET> (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:INFO> Lights ON<SET> all actions completed. [latest-25016]2025-01-26T22:04:39.675Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:04:39.680Z <Engine:NOTICE> ReactionHistory: no entry for [latest-25016]2025-01-26T22:04:39.683Z <Engine:NOTICE> [Engine]Engine#1 entry 256 reaction rule-m6e33ja3:S-1q2f1j0p: [Error] terminated [parent terminating] [latest-25016]2025-01-26T22:04:39.683Z <Engine:CRIT> Error: terminated [parent terminating] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.699Z <Engine:NOTICE> [Engine]Engine#1 entry 254 reaction rule-m6e33ja3:S: [Error] terminated [preempted by rule state change] [latest-25016]2025-01-26T22:04:39.699Z <Engine:CRIT> Error: terminated [preempted by rule state change] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.700Z <Engine:INFO> Enqueueing "Lights OFF<RESET>" (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.704Z <Engine:NOTICE> Starting reaction Lights OFF<RESET> (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.705Z <Engine:INFO> Lights OFF<RESET> all actions completed. [latest-25016]2025-01-26T22:05:48.822Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:05:48.831Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:INFO> Lights ON<RESET> all actions completed.
Hi @toggledbits
I found this very old post that talked about a way to limit device reading to avoid the throttled problem, because it's not a question of logic, it's that the device actually sends a lot of information, in my case the NUT ups installed in HE.
https://smarthome.community/topic/687/flapping-device?_=1737652139854
It mentions engine section of reactor.yaml by setting update_rate_limit, but I looked in the current MSR documentation and I can't find this information, so I don't know if it's still valid, its effect and parameters.
My situation is simple, when I have a UPS problem the NUT is sending dozens of reports per second and then I have the throttled problem. The same rule applies when the power is normal.
This is the rule, and the parameter that fails is the Tripp Lite UPS status.
cf9ddabf-3144-4e5a-80a4-0dc7664b9573-image.png
a813a077-974e-4737-897c-e383085b3d8f-image.png
All error is the same scenario.
[latest-25016]2025-01-23T12:01:32.753Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.756Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.769Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.772Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:32.776Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.780Z <Rule:WARN> UPS On Battery (rule-l4hjuka5 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling> [latest-25016]2025-01-23T12:01:32.781Z <Rule:WARN> UPS Info (rule-l4gheo63 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling... [latest-25016]2025-01-23T12:01:40.757Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.759Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:40.776Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.777Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:40.778Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott>Thanks.
Hello -
Long time. Hope everyone is good.
I have a rule that looks at a number of temperature sensors around the house. It simply sends a general alert if any of them fall below their threshold. (A basic “House is too cold” alert for when we’re away)
Generally, this has worked well. But I was wondering if there’s a way to make the message somewhat dynamic without creating separate rules for each sensor.
E.g. “House is too cold due to Sump Temperature below 45 degrees.”
I thought I remember reading about someone doing this in the past but couldn’t find it.
Thanks for any ideas!
Reactor Start - System Crash/Restart
-
Hello All -
I upgraded my OS to Ubuntu 20.04 today and have been regretting it for several hours. I have most of my system up. However, I've found that, when I start Reactor, it panics / reboots my OS. I've included the syslog during startup below. There's a benign message about not finding a Vera device just before the reboot but that's it.Needless to say, I've learned my lesson regarding OS upgrades.
Bare metal Linux / Ubuntu 20.04 (Running inside VirtualBox)
Reactor Version: stable-22337-1a0a685fDec 30 19:33:46 homeauto03 systemd[1]: Started Multi System Reactor. Dec 30 19:33:46 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:46 EST (1672446826) Dec 30 19:33:46 homeauto03 node[7240]: Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config Dec 30 19:33:46 homeauto03 node[7240]: NODE_PATH /home/tbully/reactor Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325 Dec 30 19:33:47 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334 Dec 30 19:33:48 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306 Dec 30 19:33:48 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:48 EST (1672446828) Dec 30 19:33:49 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:49.110Z <Rule:CRIT> ReferenceError: Can't find entity "vera>device_368" [-] Dec 30 19:33:49 homeauto03 node[7240]: ReferenceError: Can't find entity "vera>device_368" Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37) Dec 30 19:33:49 homeauto03 node[7240]: at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54) Dec 30 19:33:49 homeauto03 node[7240]: at async /home/tbully/reactor/server/lib/Rule.js:830:17 Dec 30 19:33:49 homeauto03 systemd[1]: Stopping Session 14 of User tbully... -
I have the logs but can't find a way to upload them. I don't have permissions to upload a file and if I paste it in here it says the post is too large.
Here's a few pieces:
[stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 [stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 [stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage [stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor [stable-22337]2022-12-31T00:33:46.750Z <app:INFO> Configured locale (undefined); selected locale(s) en_CA.UTF-8 [stable-22337]2022-12-31T00:33:46.761Z <app:INFO> Loaded locale en-US [stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323 [stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283 [stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300 [stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283 [stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314 [stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323 [stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293 [stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096 [stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333 [stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305 [stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283 [stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335 [stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320 [stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320 [stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337 [stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320 [stable-22337]2022-12-31T00:33:46.887Z <app:NOTICE> Starting Structure... [stable-22337]2022-12-31T00:33:46.890Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [stable-22337]2022-12-31T00:33:46.892Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351 [stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325 [stable-22337]2022-12-31T00:33:47.193Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334 [stable-22337]2022-12-31T00:33:48.290Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306 [stable-22337]2022-12-31T00:33:48.297Z <Structure:INFO> Starting controller VeraController#vera [stable-22337]2022-12-31T00:33:48.298Z <VeraController:NOTICE> VeraController#vera starting... [stable-22337]2022-12-31T00:33:48.304Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [stable-22337]2022-12-31T00:33:48.341Z <Controller:INFO> VeraController#vera loaded implementation data ver 22280 rev 8 format 1 [stable-22337]2022-12-31T00:33:48.341Z <Structure:INFO> Starting controller HassController#hass [stable-22337]2022-12-31T00:33:48.341Z <HassController:NOTICE> HassController#hass starting... [stable-22337]2022-12-31T00:33:48.343Z <Controller:INFO> HassController#hass loaded hass capabilities ver 22312 rev 2 format 1 [stable-22337]2022-12-31T00:33:48.354Z <Controller:INFO> HassController#hass loaded implementation data ver 22335 rev 1 format 1 [stable-22337]2022-12-31T00:33:48.354Z <Structure:INFO> Starting controller SystemController#reactor_system [stable-22337]2022-12-31T00:33:48.359Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [stable-22337]2022-12-31T00:33:48.519Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [stable-22337]2022-12-31T00:33:48.520Z <VeraController:NOTICE> VeraController#vera updating capabilities for system entity System#vera>system [stable-22337]2022-12-31T00:33:48.525Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.34.17:8123/api/websocket [stable-22337]2022-12-31T00:33:48.529Z <app:NOTICE> Starting HTTP server and API... [stable-22337]2022-12-31T00:33:48.530Z <httpapi:NOTICE> Starting HTTP API v1 22337 on http://192.168.34.:8111 [stable-22337]2022-12-31T00:33:48.533Z <app:NOTICE> Starting Reaction Engine... [stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Reaction Engine starting [stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Checking rule sets... [stable-22337]2022-12-31T00:33:48.539Z <Engine:INFO> Checking rules...```[stable-22337]2022-12-31T00:33:49.745Z Rule:INFO Master Closet Motion Battery Low (rule-grp17k28ehz in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.761Z Rule:ERR Rule#rule-grp17k28qlp trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_368" [-]
[stable-22337]2022-12-31T00:33:49.762Z Rule:CRIT ReferenceError: Can't find entity "vera>device_368" [-]
ReferenceError: Can't find entity "vera>device_368"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) evaluated; trigger state unchanged (true); rule state remains SET
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.773Z Rule:ERR Rule#rule-grp17k2iotv trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_543" [-]
[stable-22337]2022-12-31T00:33:49.773Z Rule:CRIT ReferenceError: Can't find entity "vera>device_543" [-]
ReferenceError: Can't find entity "vera>device_543"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.773Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.782Z Rule:ERR Rule#rule-grp17k3ui8q trigger evaluation failed: [ReferenceError] Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
[stable-22337]2022-12-31T00:33:49.782Z Rule:CRIT ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:373:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.782Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) started
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) started
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO TurnOffPantryLights (rule-grplt8fpma in Basement Reactor) evaluated; trigger state unchanged (false); rule state remains RESET[stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluated; trigger state unchanged (false); rule state remains RESET [stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Reactor (rule-492 in Garage Reactor) evaluation complete [stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluation complete [stable-22337]2022-12-31T00:33:49.907Z <httpapi:NOTICE> httpapi: listening [stable-22337]2022-12-31T00:33:49.921Z <app:NOTICE> Starting WSAPI... [stable-22337]2022-12-31T00:33:49.922Z <wsapi:NOTICE> wsapi: starting version 22320 [stable-22337]2022-12-31T00:33:50.112Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "12/30/2022, 7:33:50 PM" (TZ offset -300 mins from UTC) [stable-22337]2022-12-31T00:33:50.120Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine... [stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Closing APIs... [stable-22337]2022-12-31T00:33:50.121Z <wsapi:NOTICE> wsapi: closing... [stable-22337]2022-12-31T00:33:50.121Z <httpapi:NOTICE> HTTP API closing... [stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Stopping Engine... [stable-22337]2022-12-31T00:33:50.128Z <Rule:NOTICE> Turn Off Upstairs Hall Light (rule-grprsxsoqm in UpstairsHall Reactor) stopping [stable-22337]2022-12-31T00:33:50.129Z <Rule:NOTICE> Run Hot Water Recirculation (rule-l7ey8s4w in House Reactor) stopping [stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> Run Fans (rule-l6pi77c2 in House Reactor) stopping [stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> VeraSecureTriggered (rule-grplg89w7x in House Reactor) stopping[stable-22337]2022-12-31T00:33:50.329Z <Rule:NOTICE> Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) stopped [stable-22337]2022-12-31T00:33:50.330Z <Rule:NOTICE> Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) stopped [stable-22337]2022-12-31T00:33:50.417Z <Engine:NOTICE> [Engine]Engine#1 has shut down. [stable-22337]2022-12-31T00:33:50.417Z <app:NOTICE> Closing Structure... [stable-22337]2022-12-31T00:33:50.418Z <Structure:INFO> Structure#1 Stopping controllers... [stable-22337]2022-12-31T00:33:50.418Z <Controller:NOTICE> VeraController#vera stopping [stable-22337]2022-12-31T00:33:50.524Z <HassController:NOTICE> HassController#hass stopping [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] WebSocket was closed before the connection was established [-] [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass ws error code (undefined) [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] WebSocket was closed before the connection was established [-] [stable-22337]2022-12-31T00:33:50.527Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.34.17:8123/api/websocket closed during open/negotiation [stable-22337]2022-12-31T00:33:50.527Z <Controller:NOTICE> HassController#hass stopping [stable-22337]2022-12-31T00:33:50.803Z <Controller:NOTICE> SystemController#reactor_system stopping [stable-22337]2022-12-31T00:33:50.811Z <Controller:ERR> Controller SystemController#reactor_system is off-line! [stable-22337]2022-12-31T00:33:50.814Z <Structure:INFO> Structure#1 Final data sync... [stable-22337]2022-12-31T00:33:50.838Z <Structure:NOTICE> Structure Structure#1 stopped [stable-22337]2022-12-31T00:33:50.839Z <app:NOTICE> Stopping timers... [stable-22337]2022-12-31T00:33:50.840Z <app:NOTICE> Shutdown complete, process ID 7240 -
Sorry for talking to myself. Just trying to relay what I know.
I tried running it manually and got the following:
tbully@homeauto03:~/reactor$ npm run deps npm ERR! Missing script: "deps" npm ERR! npm ERR! To see a list of scripts, run: npm ERR! npm run npm ERR! A complete log of this run can be found in: npm ERR! /home/tbully/.npm/_logs/2022-12-31T01_15_30_113Z-debug-0.log tbully@homeauto03:~/reactor$ NODE_PATH=$(pwd) node app.js Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config NODE_PATH /home/tbully/reactor [stable-22337]2022-12-31T01:15:55.631Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 [stable-22337]2022-12-31T01:15:55.632Z <app:null> Process ID 2239 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 [stable-22337]2022-12-31T01:15:55.633Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage [stable-22337]2022-12-31T01:15:55.633Z <app:null> NODE_PATH=/home/tbully/reactor [stable-22337]2022-12-31T01:15:55.651Z <Structure:null> Module Structure v22323 [stable-22337]2022-12-31T01:15:55.652Z <Capabilities:null> Module Capabilities v22283 [stable-22337]2022-12-31T01:15:55.709Z <Plugin:null> Module Plugin v22300 [stable-22337]2022-12-31T01:15:55.716Z <TimerBroker:null> Module TimerBroker v22283 [stable-22337]2022-12-31T01:15:55.720Z <Entity:null> Module Entity v22314 [stable-22337]2022-12-31T01:15:55.724Z <Controller:null> Module Controller v22323 [stable-22337]2022-12-31T01:15:55.734Z <default:null> Module Ruleset v22293 [stable-22337]2022-12-31T01:15:55.735Z <default:null> Module Rulesets v21096 [stable-22337]2022-12-31T01:15:55.743Z <GlobalExpression:null> Module GlobalExpression v21333 [stable-22337]2022-12-31T01:15:55.753Z <Predicate:null> Module Predicate v22305 [stable-22337]2022-12-31T01:15:55.757Z <AlertManager:null> Module AlertManager v22283 [stable-22337]2022-12-31T01:15:55.759Z <Rule:null> Module Rule v22335 [stable-22337]2022-12-31T01:15:55.763Z <GlobalReaction:null> Module GlobalReaction v22320 [stable-22337]2022-12-31T01:15:55.765Z <Engine:null> Module Engine v22320 [stable-22337]2022-12-31T01:15:55.769Z <httpapi:null> Module httpapi v22337 [stable-22337]2022-12-31T01:15:55.783Z <wsapi:null> Module wsapi v22320 [stable-22337]2022-12-31T01:15:55.845Z <TaskQueue:null> Module TaskQueue 21351 [stable-22337]2022-12-31T01:15:55.846Z <VeraController:null> Module VeraController v22325 [stable-22337]2022-12-31T01:15:56.133Z <HassController:null> Module HassController v22334 [stable-22337]2022-12-31T01:15:57.494Z <SystemController:null> Module SystemController v22306 -
I could delete these posts but I won't. In short, I'm an idiot.
I remembered I have a rule which reboots my Linux host when my weather station goes in to error. Reactor lives on that host. (sigh)
My fix was to temporarily rename the "reboot" command in the filesystem to something else. Start Reactor (imagine that, no reboot!). Disable the rule. Fix the command back to "reboot" in the FS.
Happy New Year! (ugh)
-
These things happen. It's easy to forget stuff like this sometimes. A couple of suggestions:
- Send yourself a notification before you reboot the entire system (with the reason for doing it). Alert, email, cloud service... doesn't matter... just leave yourself a trail of crumbs to follow. It's a good idea to do this before any kind of automatically-triggered aggression against a process or system.
- Delay the reboot command by a minute or two in the reaction after that notification. That will give you time to (a) notice the notification and (b) cancel the reaction in the Running Reactions Status panel. You can then go and fix the rule or whatever is triggering it.
Is there a reason you went to 20.04 instead of 22.04 LTS? The latter will have support through April 2027. If you want to take that step, you can just use
do-release-upgradefrom 20.04. -
Been there, done that. I agree with @toggledbits about alerts. I prefer more alerts (I could always ignore them) than black magic routines.
-
In my exhaustion (anger? Lol), I mistyped. I’m at 22.04.
I do fire an email just before the reboot. I took a break to check emails and wrap up for the day and this is what triggered it for me. If it wasn’t for this, I think I’d still be digging. I send lots of emails, perhaps too many, when different things happen. This is a great idea!
I have to go look at the rule today. I thought I set a variable on reboot which would only allow one event/reboot. At least I thought about this possibility but I clearly missed something.
Thanks for the consoling, gents. I’ve appreciated both of your support over the past year as I’ve slowly moved away from Vera to HASS with Reactor being the central rules engine.
-
T toggledbits locked this topic on