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!
Need Testers
-
Not hearing a lot of grumbling, which is a Good Thing so far. Any and all feedback welcome. Please comment on the docs, too, if you have anything. On my end, I'm out of things to do on this feature, nothing to add, so I'm just waiting for fixing/tweaking.
-
@toggledbits thanks for this feature! I sort of had to volunteer as a tester as I originally did a feature request for authentication support...
Anyway, seems to work nicely, although only about an hour of testing behind. Will keep you posted if anything unexpected comes up. You could update docs though:
"1. Copy the template users.yaml-dist from the dist-config distribution directory to your config directory."
--> "1. Copy the template users.yaml-dist from the /opt/reactor/dist-config distribution directory to your config directory. Rename it as users.yaml file."
(at least for me as a Docker user it wasn't immediately clear where to find this template)
-
Hi, I used Portainer to change the image from latest to userauth and it was easy and thanks for this update!
current configuration:
Synology NAS/Docker/Reactor (Multi-hub) userauth-24120-7745fb8dunexpected:
when I try to log in on http://10.0.0.1:8111/dashboard/ as admin:admin, I'm redirect to reactor http://10.0.0.1:8111/reactor/en-US/ and not to dashboard
This happens on Chrome and EdgeFeatures/suggestion that I image:
Guest user has access to:
all dashboard set to public (homescreen - all public group tile - all public single tile)where group tile are rooms/hubs/virtual/weather on homescreen dashboard
and single tile are all the entities: devices/virtual devices/etcAdmin can use option on tile VISIBLE/HIDDEN icon by clicking on it.
If a tile is set to HIDDEN, all entities associated with it will also be hidden. Setting VISIBLE on specific entities will not be respected. Setting hidden on specific entities it will be not visible to guests.
So Public means VISIBLE.imaging it:
-
Not sure if others are experiencing the same, but with this build (userauth-24120-7745fb8d) if I go to Manual (i.e. http://reactor-ip:8111/docs/), it takes a very long time before search can be used as it stays in "initializing search" state. At least I haven't noticed the same with earlier releases. Browser is Chrome.
-
@toggledbits another thing noticed with this build is that deleting global reactions does not work.
How to reproduce:
- create reaction
- delete it
- refresh browser
- reaction is back...
-
@tunnus said in Need Testers:
noticed with this build is that deleting global reactions does not work.
I see it. It's also happening to latest-24115. I've got it fixed on my end and will roll a build on Sunday.
@noelab said in Need Testers:
when I try to log in on http://10.0.0.1:8111/dashboard/ as admin:admin, I'm redirect to reactor http://10.0.0.1:8111/reactor/en-US/ and not to dashboard
I think I've got that nailed down as well. Look for Sunday's build.
@Pabla said in Need Testers:
Yes this would be a good improvement to the docs
I think better still, have Reactor docker containers copy
dist-config
to your data directory (asdist-config
, not overwriting any existing real config), so no special steps are needed to find those files, they are just there. Sunday's build. -
@tunnus said in Need Testers:
Not sure if others are experiencing the same, but with this build (userauth-24120-7745fb8d) if I go to Manual (i.e. http://reactor-ip:8111/docs/), it takes a very long time before search can be used as it stays in "initializing search" state. At least I haven't noticed the same with earlier releases. Browser is Chrome.
Anyone else noticed this? @noelab, @Pabla? Other thing I found out today was that there's some kind of a log problem going on, Docker logs claim that reactor.log file cannot be found:
2024/05/11 21:48:36 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:32 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:48:32 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/11 21:48:09 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:08 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:48:08 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/11 21:46:50 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:46:45 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:46:45 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream
But reactor.log file seems to in place when checked via terminal:
-
@tunnus yes, some problem here too from the reactor log in container manager. Hope this may help too:
2024/05/08 21:20:46 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/08 21:20:46 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:20:46 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/08 21:20:46 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/08 21:20:46 stdout [userauth-24120]2024-05-08T19:20:46.401Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 7ms (from 1715196046401<5/8/2024, 9:20:46 PM> to 1715196046408<5/8/2024, 9:20:46 PM>) 2024/05/08 21:20:45 stdout [userauth-24120]2024-05-08T19:20:45.347Z <Timer:null> Timer#rule-lq1iq5i3 just a note: I'm setting a delay of only 8ms (from 1715196045347<5/8/2024, 9:20:45 PM> to 1715196045355<5/8/2024, 9:20:45 PM>) 2024/05/08 21:20:42 stdout [userauth-24120]2024-05-08T19:20:42.093Z <Timer:null> Timer#rule-lq5ri09p just a note: I'm setting a delay of only 8ms (from 1715196042093<5/8/2024, 9:20:42 PM> to 1715196042101<5/8/2024, 9:20:42 PM>) 2024/05/08 21:19:04 stdout [userauth-24120]2024-05-08T19:19:04.547Z <Timer:null> Timer#rule-lq5rgx5t just a note: I'm setting a delay of only 8ms (from 1715195944547<5/8/2024, 9:19:04 PM> to 1715195944555<5/8/2024, 9:19:04 PM>) 2024/05/08 21:19:02 stdout [userauth-24120]2024-05-08T19:19:02.765Z <Timer:null> Timer#rule-lq5rhvua just a note: I'm setting a delay of only 8ms (from 1715195942765<5/8/2024, 9:19:02 PM> to 1715195942773<5/8/2024, 9:19:02 PM>) 2024/05/08 21:19:02 stdout [userauth-24120]2024-05-08T19:19:02.153Z <EzloController:null> remapped item action to [Object]{ "item": "switch", "value": true, "method": "hub.item.value.set", "parameters": { "value": { "value": true } } } 2024/05/08 21:19:01 stdout [userauth-24120]2024-05-08T19:19:01.110Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715195941110<5/8/2024, 9:19:01 PM> to 1715195941118<5/8/2024, 9:19:01 PM>) 2024/05/08 21:18:59 stdout [userauth-24120]2024-05-08T19:18:59.226Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195939226<5/8/2024, 9:18:59 PM> to 1715195939234<5/8/2024, 9:18:59 PM>) 2024/05/08 21:17:10 stdout [userauth-24120]2024-05-08T19:17:10.678Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715195830678<5/8/2024, 9:17:10 PM> to 1715195830686<5/8/2024, 9:17:10 PM>) 2024/05/08 21:14:44 stdout [userauth-24120]2024-05-08T19:14:44.540Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195684540<5/8/2024, 9:14:44 PM> to 1715195684548<5/8/2024, 9:14:44 PM>) 2024/05/08 21:09:18 stdout [userauth-24120]2024-05-08T19:09:18.150Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715195358150<5/8/2024, 9:09:18 PM> to 1715195358158<5/8/2024, 9:09:18 PM>) 2024/05/08 21:05:44 stdout [userauth-24120]2024-05-08T19:05:44.738Z <Timer:null> Timer#rule-ks56ms0b just a note: I'm setting a delay of only 8ms (from 1715195144738<5/8/2024, 9:05:44 PM> to 1715195144746<5/8/2024, 9:05:44 PM>) 2024/05/08 21:05:44 stdout [userauth-24120]2024-05-08T19:05:44.719Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195144719<5/8/2024, 9:05:44 PM> to 1715195144727<5/8/2024, 9:05:44 PM>) 2024/05/08 21:00:16 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/08 21:00:14 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 21:00:12 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/08 20:59:52 stdout [userauth-24120]2024-05-08T18:59:52.886Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715194792886<5/8/2024, 8:59:52 PM> to 1715194792894<5/8/2024, 8:59:52 PM>) 2024/05/08 20:58:22 stdout [userauth-24120]2024-05-08T18:58:22.585Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715194702585<5/8/2024, 8:58:22 PM> to 1715194702593<5/8/2024, 8:58:22 PM>) 2024/05/08 20:56:26 stdout [userauth-24120]2024-05-08T18:56:26.917Z <Timer:null> Timer#rule-lq5rh1ns just a note: I'm setting a delay of only 8ms (from 1715194586917<5/8/2024, 8:56:26 PM> to 1715194586925<5/8/2024, 8:56:26 PM>) 2024/05/08 20:56:06 stdout [userauth-24120]2024-05-08T18:56:06.581Z <Timer:null> Timer#rule-lq1iq5i3 just a note: I'm setting a delay of only 8ms (from 1715194566581<5/8/2024, 8:56:06 PM> to 1715194566589<5/8/2024, 8:56:06 PM>) 2024/05/08 20:54:49 stdout [userauth-24120]2024-05-08T18:54:49.514Z <Timer:null> Timer#rule-lq5rgx5t just a note: I'm setting a delay of only 8ms (from 1715194489514<5/8/2024, 8:54:49 PM> to 1715194489522<5/8/2024, 8:54:49 PM>) 2024/05/08 20:54:49 stdout [userauth-24120]2024-05-08T18:54:49.058Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715194489058<5/8/2024, 8:54:49 PM> to 1715194489066<5/8/2024, 8:54:49 PM>) 2024/05/08 20:54:43 stdout [userauth-24120]2024-05-08T18:54:43.027Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715194483027<5/8/2024, 8:54:43 PM> to 1715194483035<5/8/2024, 8:54:43 PM>) 2024/05/08 20:50:44 stdout [userauth-24120]2024-05-08T18:50:44.225Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715194244225<5/8/2024, 8:50:44 PM> to 1715194244233<5/8/2024, 8:50:44 PM>) 2024/05/08 20:50:43 stdout [userauth-24120]2024-05-08T18:50:43.256Z <EzloController:null> remapped item action to [Object]{ "item": "dimmer", "value_expr": "min(100,max(0,floor(parameters.level*100+0.5)))", "method": "hub.item.value.set", "parameters": { "value": { "value_expr": "min(100,max(0,floor(parameters.level*100+0.5)))" } } } 2024/05/08 20:47:23 stdout [userauth-24120]2024-05-08T18:47:23.713Z <Timer:null> Timer#rule-ks56ms0b just a note: I'm setting a delay of only 8ms (from 1715194043713<5/8/2024, 8:47:23 PM> to 1715194043721<5/8/2024, 8:47:23 PM>) 2024/05/08 20:47:23 stdout [userauth-24120]2024-05-08T18:47:23.693Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715194043693<5/8/2024, 8:47:23 PM> to 1715194043701<5/8/2024, 8:47:23 PM>) 2024/05/08 20:47:22 stdout [userauth-24120]2024-05-08T18:47:22.392Z <EzloController:null> remapped item action to [Object]{ "item": "switch", "value": false, "method": "hub.item.value.set", "parameters": { "value": { "value": false } } } 2024/05/08 20:46:10 stdout [userauth-24120]2024-05-08T18:46:09.716Z <default:null> Module NotifyAlert v21092 2024/05/08 20:46:10 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/08 20:46:10 stdout [userauth-24120]2024-05-08T18:46:09.704Z <default:null> Module NotifyPushover v21195 2024/05/08 20:46:10 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/08 20:46:10 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/08 20:46:10 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/08 20:46:10 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/08 20:46:10 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 20:46:10 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 20:46:10 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/08 20:46:10 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/08 20:46:09 stdout [userauth-24120]2024-05-08T18:46:09.014Z <Notifier:null> Module Notifier v22283 2024/05/08 20:46:06 stdout at /opt/reactor/server/lib/VirtualEntityController.js:357:319 2024/05/08 20:46:06 stdout at VirtualEntityController._load_devices (/opt/reactor/server/lib/VirtualEntityController.js:644:114) 2024/05/08 20:46:06 stdout at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:563:19) 2024/05/08 20:46:06 stdout Error: Invalid primary attribute assignment; capability not assigned (state_sensor.value) 2024/05/08 20:46:06 stdout [userauth-24120]2024-05-08T18:46:06.542Z <VirtualEntityController:CRIT> Error: Invalid primary attribute assignment; capability not assigned (state_sensor.value) [-] 2024/05/08 20:46:06 stdout at /opt/reactor/server/lib/VirtualEntityController.js:357:319 2024/05/08 20:46:06 stdout at VirtualEntityController._load_devices (/opt/reactor/server/lib/VirtualEntityController.js:644:114) 2024/05/08 20:46:06 stdout at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:563:19) 2024/05/08 20:46:06 stdout Error: Invalid primary attribute assignment; capability not assigned (string_sensor.value) 2024/05/08 20:46:06 stdout [userauth-24120]2024-05-08T18:46:06.541Z <VirtualEntityController:CRIT> Error: Invalid primary attribute assignment; capability not assigned (string_sensor.value) [-] 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:05.410Z <VirtualEntityController:null> Module VirtualEntityController v24117 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:05.391Z <SystemController:null> Module SystemController v24076 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:05.382Z <OWMWeatherController:null> Module OWMWeatherController v22294 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:05.161Z <EzloController:null> Module EzloController v23345 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:05.090Z <VeraController:null> Module VeraController v24050 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:05.089Z <TaskQueue:null> Module TaskQueue 24113 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.993Z <HassController:null> Module HassController v24115 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.726Z <InfluxFeed:null> Module InfluxFeed v23341 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.682Z <wsapi:null> Module wsapi v24115 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.439Z <httpapi:null> Module httpapi v24119 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.231Z <Engine:null> Module Engine v24113 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.229Z <GlobalReaction:null> Module GlobalReaction v24099 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.197Z <Rule:null> Module Rule v24115 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.176Z <AlertManager:null> Module AlertManager v24099 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.107Z <Predicate:null> Module Predicate v23093 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.045Z <GlobalExpression:null> Module GlobalExpression v24099 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.023Z <default:null> Module Rulesets v24099 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:04.022Z <default:null> Module Ruleset v24099 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:03.952Z <Controller:null> Module Controller v24099 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:03.929Z <Entity:null> Module Entity v24108 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:03.925Z <TimerBroker:null> Module TimerBroker v22283 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:03.460Z <Plugin:null> Module Plugin v22300 2024/05/08 20:46:05 stdout [userauth-24120]2024-05-08T18:46:03.311Z <Capabilities:null> Module Capabilities v23331 2024/05/08 20:46:03 stdout [userauth-24120]2024-05-08T18:46:03.269Z <Structure:null> Module Structure v24110 2024/05/08 20:46:03 stdout [userauth-24120]2024-05-08T18:46:03.059Z <app:null> Local date/time using configured timezone and locale formatting is "5/8/2024, 8:46:03 PM" 2024/05/08 20:46:03 stdout [userauth-24120]2024-05-08T18:46:03.058Z <app:null> Loaded locale en-US for en-US 2024/05/08 20:46:02 stdout [userauth-24120]2024-05-08T18:46:02.890Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 2024/05/08 20:46:02 stdout [userauth-24120]2024-05-08T18:46:02.750Z <app:null> Resolved timezone=Europe/Rome, environment TZ=Europe/Rome; offset minutes from UTC=120 2024/05/08 20:46:02 stdout [userauth-24120]2024-05-08T18:46:02.656Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules 2024/05/08 20:46:02 stdout [userauth-24120]2024-05-08T18:46:02.656Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage 2024/05/08 20:46:02 stdout [userauth-24120]2024-05-08T18:46:02.656Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined) 2024/05/08 20:46:02 stdout [userauth-24120]2024-05-08T18:46:02.584Z <app:null> Reactor build userauth-24120-7745fb8d starting on v20.10.0 /usr/local/bin/node 2024/05/08 20:46:02 stdout NODE_PATH /opt/reactor:/opt/reactor/node_modules 2024/05/08 20:46:02 stdout Reactor userauth-24120-7745fb8d app [33m24120[39m configuration from /var/reactor/config
-
It looks like you may have a misconfiguration in your VirtualEntityController config. Can you post the config section for that?
-
@toggledbits
some devices are created for test purpose so maybe there are errorscode_text
-
id: virtual
name: VEC
implementation: VirtualEntityController
enabled: true
config:
entities:HomeMode
- id: v00_Automation template: Binary Sensor name: v00 Automation Mode
Indici Temperatura Umidità
- id: v00_InsideHOT template: Binary Sensor name: v00 Temp Inside HOT - id: v00_OutsideHOT template: Value Sensor name: v00 Temp Outside HOT - id: v00_TempOutsideInside template: Binary Sensor name: v00 Temp Outside>Inside - id: v00_umidita_assoluta_interna name: v00 Umidita Assoluta Interna capabilities: value_sensor: attributes: value: expr: xWeather_Umidita_Assoluta_Interna primary_attribute: value_sensor.value type: ValueSensor - id: v00_umidita_assoluta_esterna name: v00 Umidita Assoluta Esterna capabilities: value_sensor: attributes: value: expr: xWeather_Umidita_Assoluta_Esterna primary_attribute: value_sensor.value type: ValueSensor
IndiceThom
- id: vB1_IndiceThom template: Value Sensor name: vB1 IndiceThom capabilities: value_sensor: attributes: value: expr: xB1_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vB2_IndiceThom name: vB2 IndiceThom capabilities: value_sensor: attributes: value: expr: xB2_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vCS_IndiceThom name: vCS IndiceThom capabilities: value_sensor: attributes: value: expr: xCS_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vH_IndiceThom name: vH IndiceThom capabilities: value_sensor: attributes: value: expr: xH_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vK_IndiceThom name: vK IndiceThom capabilities: value_sensor: attributes: value: expr: xK_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vL_IndiceThom name: vL IndiceThom capabilities: value_sensor: attributes: value: expr: xL_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR1_IndiceThom name: vR1 IndiceThom capabilities: value_sensor: attributes: value: expr: xR1_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR2_IndiceThom name: vR2 IndiceThom capabilities: value_sensor: attributes: value: expr: xR2_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR3_IndiceThom name: vR3 IndiceThom capabilities: value_sensor: attributes: value: expr: xR3_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR4_IndiceThom name: vR4 IndiceThom capabilities: value_sensor: attributes: value: expr: xR4_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor - id: vT_IndiceThom name: vT IndiceThom capabilities: value_sensor: attributes: value: expr: xT_IndiceThom_ID primary_attribute: value_sensor.value type: ValueSensor
LUX Funzionale
- id: vB1_LuxFunzionale name: vB1 LuxFunzionale capabilities: value_sensor: attributes: value: expr: xB1_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vB2_LuxFunzionale name: vB2 LuxFunzionale capabilities: value_sensor: attributes: value: expr: xB2_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vCS_LuxFunzionale name: vCS LuxFunzionale capabilities: value_sensor: attributes: value: expr: xCS_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vH_LuxFunzionale name: vH LuxFunzionale capabilities: value_sensor: attributes: value: expr: xH_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vK_LuxFunzionale name: vK LuxFunzionale capabilities: value_sensor: attributes: value: expr: xK_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vL_LuxFunzionale name: vL LuxFunzionale capabilities: value_sensor: attributes: value: expr: xL_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR1_LuxFunzionale name: vR1 LuxFunzionale capabilities: value_sensor: attributes: value: expr: xR1_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR2_LuxFunzionale name: vR2 LuxFunzionale capabilities: value_sensor: attributes: value: expr: xR2_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR3_LuxFunzionale name: vR3 LuxFunzionale capabilities: value_sensor: attributes: value: expr: xR3_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR4_LuxFunzionale name: vR4 LuxFunzionale capabilities: value_sensor: attributes: value: expr: xR4_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vT_LuxFunzionale name: vT LuxFunzionale capabilities: value_sensor: attributes: value: expr: xT_Lux_Funzionale_ID primary_attribute: value_sensor.value type: ValueSensor
LUX AMBIENTALE
- id: vB1_LuxAmbientale name: vB1 LuxAmbientale capabilities: value_sensor: attributes: value: expr: xB1_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vB2_LuxAmbientale name: vB2 LuxAmbientale capabilities: value_sensor: attributes: value: expr: xB2_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vCS_LuxAmbientale name: vCS LuxAmbientale capabilities: value_sensor: attributes: value: expr: xCS_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vH_LuxAmbientale name: vH LuxAmbientale capabilities: value_sensor: attributes: value: expr: xH_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vK_LuxAmbientale name: vK LuxAmbientale capabilities: value_sensor: attributes: value: expr: xK_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vL_LuxAmbientale name: vL LuxAmbientale capabilities: value_sensor: attributes: value: expr: xL_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR1_LuxAmbientale name: vR1 LuxAmbientale capabilities: value_sensor: attributes: value: expr: xR1_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR2_LuxAmbientale name: vR2 LuxAmbientale capabilities: value_sensor: attributes: value: expr: xR2_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR3_LuxAmbientale name: vR3 LuxAmbientale capabilities: value_sensor: attributes: value: expr: xR3_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vR4_LuxAmbientale name: vR4 LuxAmbientale capabilities: value_sensor: attributes: value: expr: xR4_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor - id: vT_LuxAmbientale name: vT LuxAmbientale capabilities: value_sensor: attributes: value: expr: xT_Lux_Ambientale_ID primary_attribute: value_sensor.value type: ValueSensor
State
EnergyMode10
- id: v00_EnergyMode_Biorario template: Binary Sensor name: v00 EnergyMode Biorario - id: v00_EnergyMode_Sovraccarico_Locale template: Binary Sensor name: v00 EnergyMode Sovraccarico Locale - id: v00_EnergyMode_Lavatrice_State name: v00 EnergyMode Lavatrice State template: String Sensor capabilities: string_sensor: attributes: value: expr: xB1_Lavatrice_State - id: v00_EnergyMode_Oven_State name: v00 EnergyMode Oven State template: String Sensor capabilities: string_sensor: attributes: value: expr: xK_Oven_State - id: v00_EnergyMode_Fridge_State name: v00 EnergyMode Fridge State template: String Sensor capabilities: string_sensor: attributes: value: expr: xK_Fridge_State - id: v00_EnergyMode_Dishwasher_State name: v00 EnergyMode Dishwasher State template: String Sensor capabilities: string_sensor: attributes: value: expr: xK_Dishwasher_State
HVACMode20
TEST100
- id: testA template: Binary Switch name: TestA Binary - id: testB template: Binary Switch name: TestB Binary - id: testC template: Binary Switch name: TestC Binary - id: testD template: Binary Switch name: TestD Binary - id: testE template: Binary Switch name: TestE Binary - id: testF template: Value Sensor name: TestF ValueSensor - id: testG template: Value Sensor name: TestG ValueSensor - id: testH template: String Sensor name: TestH StringSensor - id: testI template: String Sensor name: TestI StringSensor - id: testJ template: String Sensor name: TestJ StringSensor - id: virtual_therm name: Test Virtual Heating Thermostat capabilities: - hvac_control - hvac_heating_unit - temperature_sensor primary_attribute: hvac_control.state - id: color_dimmerA template: Dimmer name: Test Virtual Color DimmerA capabilities: - color_temperature - id: color_dimmerB template: Dimmer name: Test Virtual Color DimmerB - id: testK template: Binary Sensor name: TestK Binary - id: mode name: Test ModeHouse StringSensor template: String Sensor capabilities: string_sensor: attributes: value: expr: x00_HouseMode_StartState - id: testA_dynamic_vec name: TestA Dynamic Vec Binary capabilities: value_sensor: attributes: value: expr: x00_HouseMode_StartState primary_attribute: string_sensor.value type: StringSensor - id: testB_dynamic_vec name: TestB Dynamic Vec Binary capabilities: binary_sensor: attributes: state: expr: primary_attribute: state_sensor.value type: BinarySensor - id: testC_dynamic_vec name: TestC Dynamic Vec Binary capabilities: value_sensor: attributes: value: if_expr: test - id: testD_dynamic_vec name: TEST D Dynamic VEC capabilities: binary_sensor: attributes: state: expr:
END VIRTUAL DEVICE
-
-
@noelab said in Need Testers:
- id: testB_dynamic_vec
name: TestB Dynamic Vec Binary
capabilities:
binary_sensor:
attributes:
state:
expr:
primary_attribute: state_sensor.value
type: BinarySensor
In this config, you are declaring
binary_sensor
as a capability, but then trying to set the primary attribute tostate_sensor.value
-- the capabilitystate_sensor
is not a Reactor-defined capability. That should be corrected.I have other changes coming today to help examine the timer complaints. The logging issue seems like it should be more rare -- it's a race condition in the asynchronous writing of streams. I expect to see this messages occasionally, rarely (as I said), but in runs like you are getting is not cool, but I think it's induced by the timer complaint. Stay tuned.
Also, @noelab and @tunnus the log snippets you posted look heavily filtered. That removes important context, so please don't do that. I'd rather see one error message with full context than 20 with none.
- id: testB_dynamic_vec
-
Build 24133 userauth
- Force logging to be synchronous, to work around many long-standing issues with the naturally asynchronous nature of nodejs streams.
- Enhance diagnostic reporting for short timers (temporarily, in this branch only).
- Fix some issues with post-login redirection (if you were pushed to the login page by the dashboard or admin UI).
- VirtualEntityController: preserve attribute values if possible across system updates that affect capability definitions or implementations.
- DynamicGroupController: it is now possible to set the primary attribute of a dynamic group, and determine its value dynamically. Trivial example: add the
binary_sensor.state
attribute to a group to show true when any light in the group is on. Refer to the docs for DynamicGroupController. - The
dist-config
directory is now copied to the user data virtual path target when running in docker containers so that its contents are more easily accessible to docker users. - Fixed an issue in the core related to deleting certain objects (a Global Reaction was reported, but could have been many object types).
- Dashboard: further improvements to widget type guessing if we're not told by the entity configuration.
- Bring
dist-config
version ofusers.yaml
into line with current reality. - Fix the
rpi-status.sh
tool to work better with HTTPS enabled. - HassController: Bless Hass to 2024.5.2
Note that this build incorporates all changes for
userauth
as well aslatest
branch changes not yet deployed for everyone else. -
@toggledbits I think you also forgot to push userauth-amd64. thanks.
-
@tunnus said in Need Testers:
@tunnus said in Need Testers:
Not sure if others are experiencing the same, but with this build (userauth-24120-7745fb8d) if I go to Manual (i.e. http://reactor-ip:8111/docs/), it takes a very long time before search can be used as it stays in "initializing search" state. At least I haven't noticed the same with earlier releases. Browser is Chrome.
Anyone else noticed this? @noelab, @Pabla? Other thing I found out today was that there's some kind of a log problem going on, Docker logs claim that reactor.log file cannot be found:
Just quickly tested this and yes it says initializing search. I am using Safari
-
@toggledbits can confirm that this new build (24133) fixes "delete problem", i.e. global reactions can now be deleted without them reappearing. Not seeing those "Reactor Log Panic" messages, but other errors:
2024/05/13 18:51:08 stdout at async /opt/reactor/server/lib/Rule.js:885:17 2024/05/13 18:51:08 stdout at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024/05/13 18:51:08 stdout at Rule._evaluate (/opt/reactor/server/lib/Rule.js:943:69) 2024/05/13 18:51:08 stdout at Timer.delayms (/opt/reactor/server/lib/Timer.js:151:132) 2024/05/13 18:51:08 stdout at Timer.at (/opt/reactor/server/lib/Timer.js:147:381) 2024/05/13 18:51:08 stdout Error: Delay Source Traceback 2024/05/13 18:51:08 stdout [userauth-24133]2024-05-13T15:51:08.837Z <Timer:CRIT> Error: Delay Source Traceback [-] 2024/05/13 18:51:08 stdout [userauth-24133]2024-05-13T15:51:08.837Z <Timer:null> Timer#rule-ktmrcd6d just a note: I'm setting a delay of only 8ms (from 1715615468837<5/13/2024, 6:51:08 PM> to 1715615468845<5/13/2024, 6:51:08 PM>) 2024/05/13 18:51:00 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/13 18:51:00 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/13 18:50:03 stdout [userauth-24133]2024-05-13T15:50:03.915Z <wsapi:CRIT> wsapi: client "172.18.0.1#5" sending authreq 2024/05/13 18:50:02 stdout [userauth-24133]2024-05-13T15:50:02.092Z <wsapi:CRIT> wsapi: client "172.18.0.1#4" sending authreq 2024/05/13 18:49:33 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/13 18:49:33 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/13 18:48:15 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/13 18:48:15 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/13 18:47:07 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/13 18:47:07 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/13 18:46:29 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/13 18:46:29 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/13 18:46:25 stdout at async /opt/reactor/server/lib/Rule.js:885:17 2024/05/13 18:46:25 stdout at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024/05/13 18:46:25 stdout at Rule._evaluate (/opt/reactor/server/lib/Rule.js:943:69) 2024/05/13 18:46:25 stdout at Timer.delayms (/opt/reactor/server/lib/Timer.js:151:132) 2024/05/13 18:46:25 stdout at Timer.at (/opt/reactor/server/lib/Timer.js:147:381) 2024/05/13 18:46:25 stdout Error: Delay Source Traceback 2024/05/13 18:46:25 stdout [userauth-24133]2024-05-13T15:46:25.384Z <Timer:CRIT> Error: Delay Source Traceback [-] 2024/05/13 18:46:25 stdout [userauth-24133]2024-05-13T15:46:25.384Z <Timer:null> Timer#rule-ktmrcd6d just a note: I'm setting a delay of only 8ms (from 1715615185384<5/13/2024, 6:46:25 PM> to 1715615185392<5/13/2024, 6:46:25 PM>) 2024/05/13 18:45:10 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/13 18:45:10 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/13 18:44:15 stdout at async /opt/reactor/server/lib/Rule.js:885:17 2024/05/13 18:44:15 stdout at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024/05/13 18:44:15 stdout at Rule._evaluate (/opt/reactor/server/lib/Rule.js:943:69) 2024/05/13 18:44:15 stdout at Timer.delayms (/opt/reactor/server/lib/Timer.js:151:132) 2024/05/13 18:44:15 stdout at Timer.at (/opt/reactor/server/lib/Timer.js:147:381) 2024/05/13 18:44:15 stdout Error: Delay Source Traceback 2024/05/13 18:44:15 stdout [userauth-24133]2024-05-13T15:44:15.282Z <Timer:CRIT> Error: Delay Source Traceback [-] 2024/05/13 18:44:15 stdout [userauth-24133]2024-05-13T15:44:15.281Z <Timer:null> Timer#rule-grp11myuubg just a note: I'm setting a delay of only 5ms (from 1715615055281<5/13/2024, 6:44:15 PM> to 1715615055286<5/13/2024, 6:44:15 PM>) 2024/05/13 18:44:00 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/13 18:44:00 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/13 18:43:44 stdout [userauth-24133]2024-05-13T15:43:44.182Z <wsapi:CRIT> wsapi: client "172.18.0.1#3" sending authreq 2024/05/13 18:43:36 stdout [userauth-24133]2024-05-13T15:43:36.850Z <wsapi:CRIT> wsapi: client "172.18.0.1#2" sending authreq 2024/05/13 18:43:27 stdout [userauth-24133]2024-05-13T15:43:27.574Z <default:null> Module NotifyTelegram v21221 2024/05/13 18:43:27 stdout [userauth-24133]2024-05-13T15:43:27.564Z <wsapi:CRIT> wsapi: client "172.18.0.1#1" sending authreq 2024/05/13 18:43:27 stdout [userauth-24133]2024-05-13T15:43:27.293Z <Notifier:null> Module Notifier v22283 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.989Z <SystemController:null> Module SystemController v24076 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.980Z <OWMWeatherController:null> Module OWMWeatherController v22294 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.893Z <HubitatController:null> Module HubitatController v24076 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.830Z <HassController:null> Module HassController v24128 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.526Z <MQTTController:null> Module MQTTController v24120 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.488Z <VirtualEntityController:null> Module VirtualEntityController v24117 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.431Z <VeraController:null> Module VeraController v24050 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.431Z <TaskQueue:null> Module TaskQueue 24113 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.416Z <InfluxFeed:null> Module InfluxFeed v23341 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.312Z <wsapi:null> Module wsapi v24115 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.284Z <httpapi:null> Module httpapi v24121 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.275Z <Engine:null> Module Engine v24113 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.273Z <GlobalReaction:null> Module GlobalReaction v24099 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.268Z <Rule:null> Module Rule v24115 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.265Z <AlertManager:null> Module AlertManager v24099 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.259Z <Predicate:null> Module Predicate v23093 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.243Z <GlobalExpression:null> Module GlobalExpression v24099 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.232Z <default:null> Module Rulesets v24099 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.231Z <default:null> Module Ruleset v24099 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.219Z <Controller:null> Module Controller v24099 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.215Z <Entity:null> Module Entity v24108 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.208Z <TimerBroker:null> Module TimerBroker v22283 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.180Z <Plugin:null> Module Plugin v22300 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.115Z <Capabilities:null> Module Capabilities v23331 2024/05/13 18:43:21 stdout [userauth-24133]2024-05-13T15:43:21.112Z <Structure:null> Module Structure v24110 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.999Z <app:null> Local date/time using configured timezone and locale formatting is "5/13/2024, 6:43:20 PM" 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.998Z <app:null> Loaded locale en-US for en-US 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.969Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.966Z <app:null> Resolved timezone=Europe/Helsinki, environment TZ=Europe/Helsinki; offset minutes from UTC=180 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.814Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.814Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.813Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined) 2024/05/13 18:43:20 stdout [userauth-24133]2024-05-13T15:43:20.770Z <app:null> Reactor build userauth-24133-a2bf8846 starting on v20.10.0 /usr/local/bin/node 2024/05/13 18:43:20 stdout NODE_PATH /opt/reactor:/opt/reactor/node_modules 2024/05/13 18:43:20 stdout Reactor userauth-24133-a2bf8846 app [33m24127[39m configuration from /var/reactor/config
Also that manual/docs related problem ("initializing search") is still there, but that was expected as there were no mention of it being fixed.
-
@tunnus The log snippets you are posting appear to be from something other than the log files produced by Reactor. This looks like console log for a container, and I'm not interested in looking at that, mostly because they are a limited subset of message severity and, as I said earlier, drop a lot of other context is valuable to me in evaluating what I'm seeing. Reactor produces its own log files for a reason. If you want to post snippets from that, with context in accordance with the posting guidelines, I'm ready to look at those any time.
-
@toggledbits ok, sorry about that snippet, it was indeed a console log for a container.
I looked through reactor logs, but couldn't see any errors there. A bit challenging as there's a lot going on (a couple of variables update very often, every 1-3 seconds and those cause a lot of log events as rules referencing them get evaluated). Btw, there's a related request/question in this thread.