@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.
I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
I see these errors on the following browsers:
Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big SurHere are the errors
Safari while creating/updating an expression
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040DuckDuckGo while clicking on status
http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44Firefox while updating a rule
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58Chrome while creating/updating an expression
TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi
Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.
I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.
I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?
I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.
But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?
So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.
This is how I installed nodejs as whilst logged in as root
ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png
Thanks in advance.
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.As the title says, here's my OpenAI Controller for Reactor:
OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.
It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.
It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).
9013ae50-fd68-42a2-87c3-97479132e465-image.png
80a88eec-7c89-464a-8196-690b4b72d044-image.png
Have fun with LLM into your scenes!
In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.
Screenshot 2024-11-28 at 22.20.41.png
And the expression is
Screenshot 2024-11-28 at 22.38.19.png
Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.
Hello
I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:
-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.
Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.
Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.
Thank you !
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
@toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.
The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?
Reactor version 24302
ZWaveJSController version 24293
Z-Wave JS UI version 9.27.4
zwave-js version 14.3.4
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0Need Testers
-
@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_sensoras a capability, but then trying to set the primary attribute tostate_sensor.value-- the capabilitystate_sensoris 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.stateattribute to a group to show true when any light in the group is on. Refer to the docs for DynamicGroupController. - The
dist-configdirectory 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-configversion ofusers.yamlinto line with current reality. - Fix the
rpi-status.shtool to work better with HTTPS enabled. - HassController: Bless Hass to 2024.5.2
Note that this build incorporates all changes for
userauthas well aslatestbranch changes not yet deployed for everyone else.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@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/configAlso 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.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@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.
-
@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 modifyconfig/logging.yamlby adding the following:# The line below is indented two spaces; the line after is indented four spaces. "Rule#rule-ktmrcd6d": level: 3This 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.
-
This post is deleted!
-
@toggledbits thanks for the tip, now logging traffic is considerably slower (log rotation ca. 10 minutes)
-
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.
-
@toggledbits thanks, can confirm that (local) manual is fixed now, no more "initializing search"
-
@toggledbits I think the
restart reactorbutton 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 showingDisconnectedas it usually does as it restarts. Logs provided in Dropbox. -
Does it do that every time you use it?
-
@toggledbits Yessir.
-
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)
-
@toggledbits Using Brave browser. Redacted
users.yamlon it's way. -
If you just refresh the page instead of hitting the button, does it refresh, or go to the login page?
