MSR UI on a mobile browser

[toggledbits]

It looks like you may have a misconfiguration in your VirtualEntityController config. Can you post the config section for that?

[noelab]

@toggledbits
some devices are created for test purpose so maybe there are errors

code_text

• id: virtual
  name: VEC
  implementation: VirtualEntityController
  enabled: true
  config:
  entities:

  HomeMode

   -
     id: v00_Automation
     template: Binary Sensor
     name: v00 Automation Mode
  

  Indici Temperatura Umidità

   -
     id: v00_InsideHOT
     template: Binary Sensor
     name: v00 Temp Inside HOT                
   -
     id: v00_OutsideHOT
     template: Value Sensor
     name: v00 Temp Outside HOT
   -
     id: v00_TempOutsideInside
     template: Binary Sensor
     name: v00 Temp Outside>Inside
   -
     id: v00_umidita_assoluta_interna
     name: v00 Umidita Assoluta Interna      
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xWeather_Umidita_Assoluta_Interna
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: v00_umidita_assoluta_esterna
     name: v00 Umidita Assoluta Esterna
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xWeather_Umidita_Assoluta_Esterna
     primary_attribute: value_sensor.value
     type: ValueSensor
  

  IndiceThom

   -
     id: vB1_IndiceThom
     template: Value Sensor
     name: vB1 IndiceThom    
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xB1_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vB2_IndiceThom
     name: vB2 IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xB2_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vCS_IndiceThom
     name: vCS IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xCS_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vH_IndiceThom
     name: vH IndiceThom    
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xH_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vK_IndiceThom
     name: vK IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xK_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vL_IndiceThom
     name: vL IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xL_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR1_IndiceThom
     name: vR1 IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR1_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR2_IndiceThom
     name: vR2 IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR2_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR3_IndiceThom
     name: vR3 IndiceThom    
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR3_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR4_IndiceThom
     name: vR4 IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR4_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vT_IndiceThom
     name: vT IndiceThom
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xT_IndiceThom_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
  

  LUX Funzionale

   -
     id: vB1_LuxFunzionale
     name: vB1 LuxFunzionale  
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xB1_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vB2_LuxFunzionale
     name: vB2 LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xB2_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vCS_LuxFunzionale
     name: vCS LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xCS_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vH_LuxFunzionale
     name: vH LuxFunzionale    
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xH_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vK_LuxFunzionale
     name: vK LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xK_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vL_LuxFunzionale
     name: vL LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xL_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR1_LuxFunzionale
     name: vR1 LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR1_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR2_LuxFunzionale
     name: vR2 LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR2_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR3_LuxFunzionale
     name: vR3 LuxFunzionale  
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR3_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR4_LuxFunzionale
     name: vR4 LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR4_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vT_LuxFunzionale
     name: vT LuxFunzionale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xT_Lux_Funzionale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
  

  LUX AMBIENTALE

   -
     id: vB1_LuxAmbientale
     name: vB1 LuxAmbientale  
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xB1_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vB2_LuxAmbientale
     name: vB2 LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xB2_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vCS_LuxAmbientale
     name: vCS LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xCS_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vH_LuxAmbientale
     name: vH LuxAmbientale    
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xH_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vK_LuxAmbientale
     name: vK LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xK_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vL_LuxAmbientale
     name: vL LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xL_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR1_LuxAmbientale
     name: vR1 LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR1_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR2_LuxAmbientale
     name: vR2 LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR2_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR3_LuxAmbientale
     name: vR3 LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR3_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vR4_LuxAmbientale
     name: vR4 LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xR4_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
   -
     id: vT_LuxAmbientale
     name: vT LuxAmbientale
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: xT_Lux_Ambientale_ID
     primary_attribute: value_sensor.value
     type: ValueSensor
  

  State

  EnergyMode10

   -
     id: v00_EnergyMode_Biorario
     template: Binary Sensor
     name: v00 EnergyMode Biorario
   -
     id: v00_EnergyMode_Sovraccarico_Locale
     template: Binary Sensor
     name: v00 EnergyMode Sovraccarico Locale
   -
     id: v00_EnergyMode_Lavatrice_State
     name: v00 EnergyMode Lavatrice State
     template: String Sensor
     capabilities:
       string_sensor:
         attributes:
           value: 
             expr: xB1_Lavatrice_State
   -
     id: v00_EnergyMode_Oven_State
     name: v00 EnergyMode Oven State
     template: String Sensor
     capabilities:
       string_sensor:
         attributes:
           value: 
             expr: xK_Oven_State
   -
     id: v00_EnergyMode_Fridge_State
     name: v00 EnergyMode Fridge State
     template: String Sensor
     capabilities:
       string_sensor:
         attributes:
           value: 
             expr: xK_Fridge_State
   -
     id: v00_EnergyMode_Dishwasher_State
     name: v00 EnergyMode Dishwasher State
     template: String Sensor
     capabilities:
       string_sensor:
         attributes:
           value: 
             expr: xK_Dishwasher_State
  

  HVACMode20

  TEST100

   -
     id: testA
     template: Binary Switch
     name: TestA Binary         
   -
     id: testB
     template: Binary Switch
     name: TestB Binary        
   -
     id: testC
     template: Binary Switch
     name: TestC Binary
   -
     id: testD
     template: Binary Switch
     name: TestD Binary        
   -
     id: testE
     template: Binary Switch
     name: TestE Binary
   -
     id: testF
     template: Value Sensor
     name: TestF ValueSensor       
   -
     id: testG
     template: Value Sensor
     name: TestG ValueSensor
   -
     id: testH
     template: String Sensor
     name: TestH StringSensor
   -
     id: testI
     template: String Sensor
     name: TestI StringSensor   
   -
     id: testJ
     template: String Sensor
     name: TestJ StringSensor
   -
     id: virtual_therm
     name: Test Virtual Heating Thermostat
     capabilities:
       - hvac_control
       - hvac_heating_unit
       - temperature_sensor
     primary_attribute: hvac_control.state
   -
     id: color_dimmerA
     template: Dimmer
     name: Test Virtual Color DimmerA
     capabilities:
       - color_temperature
   -
     id: color_dimmerB
     template: Dimmer
     name: Test Virtual Color DimmerB
   -
     id: testK
     template: Binary Sensor
     name: TestK Binary
   -
     id: mode
     name: Test ModeHouse StringSensor
     template: String Sensor
     capabilities:
       string_sensor:
         attributes:
           value: 
             expr: x00_HouseMode_StartState
   -
     id: testA_dynamic_vec
     name: TestA Dynamic Vec Binary
     capabilities:
       value_sensor:
         attributes:
           value:
             expr: x00_HouseMode_StartState
     primary_attribute: string_sensor.value
     type: StringSensor
     
   -
     id: testB_dynamic_vec
     name: TestB Dynamic Vec Binary
     capabilities:
       binary_sensor:
         attributes:
           state:
             expr: 
     primary_attribute: state_sensor.value
     type: BinarySensor
   -
     id: testC_dynamic_vec
     name: TestC Dynamic Vec Binary
     capabilities:
       value_sensor:
         attributes:
           value:
             if_expr: test
   -
     id: testD_dynamic_vec
     name: TEST D Dynamic VEC
     capabilities:
       binary_sensor:
         attributes:
           state:
             expr: 
  

  END VIRTUAL DEVICE

[toggledbits]

@noelab said in Need Testers:

• id: testB_dynamic_vec
  name: TestB Dynamic Vec Binary
  capabilities:
  binary_sensor:
  attributes:
  state:
  expr:
  primary_attribute: state_sensor.value
  type: BinarySensor

In this config, you are declaring binary_sensor as a capability, but then trying to set the primary attribute to state_sensor.value -- the capability state_sensor is not a Reactor-defined capability. That should be corrected.

I have other changes coming today to help examine the timer complaints. The logging issue seems like it should be more rare -- it's a race condition in the asynchronous writing of streams. I expect to see this messages occasionally, rarely (as I said), but in runs like you are getting is not cool, but I think it's induced by the timer complaint. Stay tuned.

Also, @noelab and @tunnus the log snippets you posted look heavily filtered. That removes important context, so please don't do that. I'd rather see one error message with full context than 20 with none.

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

[tamorgen]

I'm not seeing 24133 userauth on your download portal....

[therealdb]

@toggledbits I think you also forgot to push userauth-amd64. thanks.

[Pabla]

@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

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

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

[tunnus]

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

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

[tunnus]

This post is deleted!

[tunnus]

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

[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

[tunnus]

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

[gwp1]

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

[toggledbits]

Does it do that every time you use it?

[gwp1]

@toggledbits Yessir.

[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)

[gwp1]

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