Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Need Testers
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor

Need Testers

Scheduled Pinned Locked Moved Multi-System Reactor
78 Posts 8 Posters 9.5k Views 8 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • tunnusT tunnus

    @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.

    Screenshot 2024-05-10 at 13.45.49.png

    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 false
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 false
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 false
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 false
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 false
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 false
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:

    Screenshot 2024-05-11 at 21.54.08.png

    PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #45

    @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.

    Screenshot 2024-05-10 at 13.45.49.png

    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

    1 Reply Last reply
    0
    • toggledbitsT toggledbits

      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 of users.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 as latest branch changes not yet deployed for everyone else.

      tunnusT Offline
      tunnusT Offline
      tunnus
      wrote on last edited by tunnus
      #46

      @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 false
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 false
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 false
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 false
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 false
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 false
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 false
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 24127 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.

      toggledbitsT 1 Reply Last reply
      0
      • tunnusT tunnus

        @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 false
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 false
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 false
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 false
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 false
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 false
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 false
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 24127 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.

        toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by toggledbits
        #47

        @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.

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

        tunnusT 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @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.

          tunnusT Offline
          tunnusT Offline
          tunnus
          wrote on last edited by tunnus
          #48

          @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.

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by toggledbits
            #49

            @tunnus If your specific concern is the Timer messages, don't be concerned. Long story shortened: these Timer objects were originally used for long intervals and the warning was put in place to help identify bugs in computing the length of those intervals, but they ended up being used for short intervals, too, and there are some conditions where those intervals can randomly be so short that they trigger the warning. I think it's time for this warning to be relegated to debug level or removed.

            You clearly have something that's logging a lot, and that's causing frequent log rotations. This not only wastes time/cycles and bytes on the disk, but it also makes debugging anything on your system harder for the reason you stated: you can't find the errors, likely because (a) it's logging too much (you're sipping from a firehose), and (b) it's rotating so frequently that you're losing useful data quickly.

            What I'd suggest is that you identify the affected rules (i.e. those that are responding to the frequent entity attribute changes), and increase their specific log levels to reduce the log output. You can do that for an individual rule. You need to get the rule ID, which you can derive from the UI by opening the rule's state in the list. You can also see it logged. Let's pick on rule-ktmrcd6d... we modify config/logging.yaml by adding the following:

              # The line below is indented two spaces; the line after is indented four spaces.
  "Rule#rule-ktmrcd6d":
    level: 3

            This puts the logging minimum level at "NOTICE", so all of the INFO messages associated with rule evaluation will be suppressed for that rule only (other rules will not be affected). That should considerably reduce your log traffic.

            I saw your question about the frequent updates as it relates to InfluxDB, and that's a sticky business. I'll respond to that over there.

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

            tunnusT 2 Replies Last reply
            0
            • toggledbitsT toggledbits

              @tunnus If your specific concern is the Timer messages, don't be concerned. Long story shortened: these Timer objects were originally used for long intervals and the warning was put in place to help identify bugs in computing the length of those intervals, but they ended up being used for short intervals, too, and there are some conditions where those intervals can randomly be so short that they trigger the warning. I think it's time for this warning to be relegated to debug level or removed.

              You clearly have something that's logging a lot, and that's causing frequent log rotations. This not only wastes time/cycles and bytes on the disk, but it also makes debugging anything on your system harder for the reason you stated: you can't find the errors, likely because (a) it's logging too much (you're sipping from a firehose), and (b) it's rotating so frequently that you're losing useful data quickly.

              What I'd suggest is that you identify the affected rules (i.e. those that are responding to the frequent entity attribute changes), and increase their specific log levels to reduce the log output. You can do that for an individual rule. You need to get the rule ID, which you can derive from the UI by opening the rule's state in the list. You can also see it logged. Let's pick on rule-ktmrcd6d... we modify config/logging.yaml by adding the following:

                # The line below is indented two spaces; the line after is indented four spaces.
  "Rule#rule-ktmrcd6d":
    level: 3

              This puts the logging minimum level at "NOTICE", so all of the INFO messages associated with rule evaluation will be suppressed for that rule only (other rules will not be affected). That should considerably reduce your log traffic.

              I saw your question about the frequent updates as it relates to InfluxDB, and that's a sticky business. I'll respond to that over there.

              tunnusT Offline
              tunnusT Offline
              tunnus
              wrote on last edited by tunnus
              #50
              This post is deleted!
              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                @tunnus If your specific concern is the Timer messages, don't be concerned. Long story shortened: these Timer objects were originally used for long intervals and the warning was put in place to help identify bugs in computing the length of those intervals, but they ended up being used for short intervals, too, and there are some conditions where those intervals can randomly be so short that they trigger the warning. I think it's time for this warning to be relegated to debug level or removed.

                You clearly have something that's logging a lot, and that's causing frequent log rotations. This not only wastes time/cycles and bytes on the disk, but it also makes debugging anything on your system harder for the reason you stated: you can't find the errors, likely because (a) it's logging too much (you're sipping from a firehose), and (b) it's rotating so frequently that you're losing useful data quickly.

                What I'd suggest is that you identify the affected rules (i.e. those that are responding to the frequent entity attribute changes), and increase their specific log levels to reduce the log output. You can do that for an individual rule. You need to get the rule ID, which you can derive from the UI by opening the rule's state in the list. You can also see it logged. Let's pick on rule-ktmrcd6d... we modify config/logging.yaml by adding the following:

                  # The line below is indented two spaces; the line after is indented four spaces.
  "Rule#rule-ktmrcd6d":
    level: 3

                This puts the logging minimum level at "NOTICE", so all of the INFO messages associated with rule evaluation will be suppressed for that rule only (other rules will not be affected). That should considerably reduce your log traffic.

                I saw your question about the frequent updates as it relates to InfluxDB, and that's a sticky business. I'll respond to that over there.

                tunnusT Offline
                tunnusT Offline
                tunnus
                wrote on last edited by
                #51

                @toggledbits thanks for the tip, now logging traffic is considerably slower (log rotation ca. 10 minutes)

                1 Reply Last reply
                0
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #52

                  userauth build 24137

                  • Updated the documentation theme and its supporting plugins; improved the appearance of code snippets with syntax highlighting in most cases; add line highlighting in many code snippets to draw attention to certain elements or changes.
                  • Dashboard: added new Thermostat type (supported by Level.updown layout) for capabilities hvac_heating_unit/hvac_cooling_unit. Evolving; further improvements coming.
                  • VirtualEntityController: Support for time-series data collection and aggregation. See the docs). As of this build, not all aggregators have been tested.
                  • Remove spurious debug warning about short timers.
                  • Fix detection of local docs and handling of static HTML files in the local installation.
                  • HassController: Bless Hass to 2024.5.3

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

                  tunnusT 1 Reply Last reply
                  👍
                  0
                  • toggledbitsT toggledbits

                    userauth build 24137

                    • Updated the documentation theme and its supporting plugins; improved the appearance of code snippets with syntax highlighting in most cases; add line highlighting in many code snippets to draw attention to certain elements or changes.
                    • Dashboard: added new Thermostat type (supported by Level.updown layout) for capabilities hvac_heating_unit/hvac_cooling_unit. Evolving; further improvements coming.
                    • VirtualEntityController: Support for time-series data collection and aggregation. See the docs). As of this build, not all aggregators have been tested.
                    • Remove spurious debug warning about short timers.
                    • Fix detection of local docs and handling of static HTML files in the local installation.
                    • HassController: Bless Hass to 2024.5.3
                    tunnusT Offline
                    tunnusT Offline
                    tunnus
                    wrote on last edited by
                    #53

                    @toggledbits thanks, can confirm that (local) manual is fixed now, no more "initializing search"

                    1 Reply Last reply
                    1
                    • G Offline
                      G Offline
                      gwp1
                      wrote on last edited by
                      #54

                      @toggledbits I think the restart reactor button is down again. When I click it I'm pushed back to the user login screen and immediately login to see the Status screen loading normally... not showing Disconnected as it usually does as it restarts. Logs provided in Dropbox.

                      *Hubitat C-7 2.4.1.151
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HASS 2025.3.4
                      w/ ZST10-700 fw 7.18.3

                      *Prod MSR in docker/portainer
                      MSR: latest-25082-3c348de6
                      MQTTController: 24257
                      ZWave Controller: 25082

                      1 Reply Last reply
                      0
                      • toggledbitsT Offline
                        toggledbitsT Offline
                        toggledbits
                        wrote on last edited by
                        #55

                        Does it do that every time you use it?

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

                        G 1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          Does it do that every time you use it?

                          G Offline
                          G Offline
                          gwp1
                          wrote on last edited by
                          #56

                          @toggledbits Yessir.

                          *Hubitat C-7 2.4.1.151
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HASS 2025.3.4
                          w/ ZST10-700 fw 7.18.3

                          *Prod MSR in docker/portainer
                          MSR: latest-25082-3c348de6
                          MQTTController: 24257
                          ZWave Controller: 25082

                          1 Reply Last reply
                          0
                          • toggledbitsT Offline
                            toggledbitsT Offline
                            toggledbits
                            wrote on last edited by
                            #57

                            OK. That's normal behavior if the login/session cookie expires or is no longer valid. And it's all browser-side, so the logs aren't of any value there. And it's working for me, so we may have to dig a little. Next time you are tempted to use the Restart button, just do a plain refresh on your browser and see (report) what happens.

                            Also, what browser are you using? And, please upload your users.yaml file (redact any plaintext passwords)

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

                            G 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              OK. That's normal behavior if the login/session cookie expires or is no longer valid. And it's all browser-side, so the logs aren't of any value there. And it's working for me, so we may have to dig a little. Next time you are tempted to use the Restart button, just do a plain refresh on your browser and see (report) what happens.

                              Also, what browser are you using? And, please upload your users.yaml file (redact any plaintext passwords)

                              G Offline
                              G Offline
                              gwp1
                              wrote on last edited by
                              #58

                              @toggledbits Using Brave browser. Redacted users.yaml on it's way.

                              *Hubitat C-7 2.4.1.151
                              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                              *HASS 2025.3.4
                              w/ ZST10-700 fw 7.18.3

                              *Prod MSR in docker/portainer
                              MSR: latest-25082-3c348de6
                              MQTTController: 24257
                              ZWave Controller: 25082

                              1 Reply Last reply
                              0
                              • tunnusT Offline
                                tunnusT Offline
                                tunnus
                                wrote on last edited by
                                #59

                                Happens to me as well (Chrome + userauth-24137-57b41335 on Docker)

                                1 Reply Last reply
                                0
                                • toggledbitsT Offline
                                  toggledbitsT Offline
                                  toggledbits
                                  wrote on last edited by
                                  #60

                                  If you just refresh the page instead of hitting the button, does it refresh, or go to the login page?

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

                                  1 Reply Last reply
                                  0
                                  • tunnusT Offline
                                    tunnusT Offline
                                    tunnus
                                    wrote on last edited by
                                    #61

                                    If I refresh that Tools-page, it'll go to Status-page

                                    1 Reply Last reply
                                    0
                                    • toggledbitsT Offline
                                      toggledbitsT Offline
                                      toggledbits
                                      wrote on last edited by toggledbits
                                      #62

                                      userauth build 24143

                                      • Fixes something that might, perhaps, address the Restart button issue some people are having (and I cannot reproduce at all on any broser). Also adds some debug (browser side) that we might be able to access to figure it out if it persists.
                                      • Revamps the port determination. Some of you, particularly docker users, may find that your Reactor UI shifts to port 8554, and is actually the desired location for HTTPS service.
                                      • Updated a lot of docs, including developer docs for building controllers.

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

                                      tunnusT 1 Reply Last reply
                                      1
                                      • toggledbitsT toggledbits

                                        userauth build 24143

                                        • Fixes something that might, perhaps, address the Restart button issue some people are having (and I cannot reproduce at all on any broser). Also adds some debug (browser side) that we might be able to access to figure it out if it persists.
                                        • Revamps the port determination. Some of you, particularly docker users, may find that your Reactor UI shifts to port 8554, and is actually the desired location for HTTPS service.
                                        • Updated a lot of docs, including developer docs for building controllers.
                                        tunnusT Offline
                                        tunnusT Offline
                                        tunnus
                                        wrote on last edited by
                                        #63

                                        @toggledbits Restart-button still does not work. Chrome:

                                        Screenshot 2024-05-23 at 21.24.45.png

                                        1 Reply Last reply
                                        0
                                        • toggledbitsT Offline
                                          toggledbitsT Offline
                                          toggledbits
                                          wrote on last edited by
                                          #64

                                          That's ACL restriction. You probably need to give logged-in users permission to use the API, or at least, that particular API.

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

                                          tunnusT 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes

                                          Recent Topics

                                          • Set Reaction > Script Action
                                            therealdbT
                                            therealdb
                                            0
                                            6
                                            85
                                          • Wiring Samotech SM308-S into light fitting
                                            akbooerA
                                            akbooer
                                            0
                                            2
                                            44
                                          • Errors after updating to MQTTController build 25139
                                            toggledbitsT
                                            toggledbits
                                            0
                                            6
                                            74
                                          • 🎉 My very first MSR controller: OpenSprinkler
                                            therealdbT
                                            therealdb
                                            5
                                            13
                                            631
                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            96
                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            122
                                            37.3k
                                          • Z-Wave Future....
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            178
                                          • Can´t restart or upgrade/deploy MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            135
                                          • [Solved] Limit HA Entity in MSR
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            7
                                            264
                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            702
                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            429
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Unsolved