@toggledbits Trigger OR was the problem and not identical internal condition/group ID as I suspected. AND is the fix. With the old OR setup, the problem was that the trigger had already fired, registering as "true" for a different reason (Lux), minutes earlier. So the photo captured by the trigger was outdated.
Thanks again for the push in the right direction!

Thanks for the reply. I tried again, the rules driving DLT have the same logical structure in every room and no one is working.
Tried the Reset Rule button specifically (not just re-editing conditions), plus a hard refresh (F5) beforehand, plus Reset Rule on every rule this one depends on (the Motion/PresenceMode rule, the Lux rule, the OccupancyMode rule, the Debounce rule) — not just the affected rule itself.
Clicked Reset Rule, got a fresh reset entry in Rule History, then a genuine motion event ~10s later. The condition tree updated correctly in the UI (Trigger OR-group and Constraints both show true, timestamped at the motion event). The rule's SET action turns lights on directly. That light did not physically turn on. Also if the UI can be out of sync with the display, a physical device action should be executed. Rule History still shows no SET after the reset entry.

I'm trying to put some logs

22:12:46.474 Rule:NOTICE  vH_DLT_20_Auto_ON (rule-mo5edh1o in H) stopping
22:12:46.475 Rule:NOTICE  vH_Motion_00_LastSeen (rule-mo5wsh4z in H) stopping
22:12:46.476 Rule:NOTICE  vH_PresenceMode_MotionSensor_ID (rule-mo5adtot in H) stopping
...
22:13:07.864 app:null     Shutdown complete, process ID 1
22:14:39.639 app:null     Reactor build latest-26221-b25bb3e3 starting
...
22:16:12.239 Rule:NOTICE  vH_DLT_20_Auto_ON (rule-mo5edh1o in H) starting
22:16:12.240 Rule:NOTICE  vH_Motion_00_LastSeen (rule-mo5wsh4z in H) starting
22:16:12.240 Rule:NOTICE  vH_PresenceMode_MotionSensor_ID (rule-mo5adtot in H) starting
22:16:13.214 Rule:INFO    vH_DLT_20_Auto_ON (rule-mo5edh1o in H) started
22:16:13.215 Rule:INFO    vH_Motion_00_LastSeen (rule-mo5wsh4z in H) started
22:16:13.215 Rule:INFO    vH_PresenceMode_MotionSensor_ID (rule-mo5adtot in H) started

22:18:29.766 Rule:INFO    vH_PresenceMode_MotionSensor_ID (rule-mo5adtot in H) starting rule state evaluation; because predicate-state-changed
22:18:29.766 Rule:INFO    vH_PresenceMode_MotionSensor_ID (rule-mo5adtot in H) evaluated; rule state transition from RESET to 'SET'
22:18:29.779 Rule:INFO    vH_Motion_00_LastSeen (rule-mo5wsh4z in H) starting rule state evaluation; because predicate-state-changed
22:18:29.779 Rule:INFO    vH_Motion_00_LastSeen (rule-mo5wsh4z in H) evaluated; rule state transition from RESET to 'SET'
   -- rule-mo5edh1o: NOTHING --

22:19:02.407 Rule:INFO    vH_PresenceMode_MotionSensor_ID (rule-mo5adtot in H) starting rule state evaluation; because predicate-state-changed
22:19:02.408 Rule:INFO    vH_PresenceMode_MotionSensor_ID (rule-mo5adtot in H) evaluated; rule state transition from SET to 'RESET'
22:19:02.419 Rule:INFO    vH_Motion_00_LastSeen (rule-mo5wsh4z in H) starting rule state evaluation; because predicate-state-changed
22:19:02.419 Rule:INFO    vH_Motion_00_LastSeen (rule-mo5wsh4z in H) evaluated; rule state transition from SET to 'RESET'
   -- rule-mo5edh1o: NOTHING --

Thanks in advance

@tunnus Hi, also constraints are true

Build: latest-26221-b25bb3e3, Docker on Synology.

Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing.
Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries.
Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart.
Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either.
Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart?
Thanks in advance

Hi,
I'm on Docker/NAs (latest-26011-c621bbc7) with Zwave js ui (last version).
I have set the 'Location' for each device in the Z-Wave JS UI dashboard, I cannot find this information among the Entity Attributes in the Reactor. I tried and the result is an empty array []. It seems the 'Location' metadata from Z-Wave JS is not being mapped to a standard attribute in Reactor. Location is equale to Rooms for me. When comparing this to the Vera or Ezlo Controller, Reactor automatically creates Room Icons also in the Reactor Dashboard and places the various devices under those room categories.
This is a very convenient way to keep the dashboard organized and quickly find lights to turn off with a click (especially when something isn't switched off as expected for me:) ).
Is there a way to map the Z-Wave JS UI 'Location' attribute and a dashboard organization, just like it does with Vera/Ezlo?

Thanks in advance for all the great tips you've shared

Hi, thank you for the new update and I'm testing it under:

Reactor build 25082
ZWaveJSController build 25082
-Docker on Synology NAS
-ZWaveJSUI 10.1.3

Trying with these values but nothing happens (in zwavejs events and in reactor logs). Am I doing something wrong with JSON string value fields?

in zwavejsui

040 = L Bulb Ball 1 Z-RGBW2
036 = R3 Bulb Roof 1 HKZW-RGB01
033 = R3 Bulb Wall 1 A-ZWA002

Correct! Without this function, I don't know how to make the bulb RGBWW work properly.
Thanks to you!

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.

@therealdb said in TTS in MSR?:

[
"Bentornato a casa",
"Casa, dolce casa!",
"Ciao!",
]

Grazie! and thanks to @toggledbits for the new dark theme, also my eyes are happy!

Hi, just playing around this topic with Alexa and I share it:
Example that works:

Still no lucky to play with "random" announce.
This example not work:

@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

@tunnus yes, some problem here too from the reactor log in container manager. Hope this may help too:

2024/05/08 21:20:46	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 21:20:46	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:20:46	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 21:20:46	stdout	/var/reactor/logs/reactor.log size hit rotation limit, rotating
2024/05/08 21:20:46	stdout	[userauth-24120]2024-05-08T19:20:46.401Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 7ms (from 1715196046401<5/8/2024, 9:20:46 PM> to 1715196046408<5/8/2024, 9:20:46 PM>)
2024/05/08 21:20:45	stdout	[userauth-24120]2024-05-08T19:20:45.347Z <Timer:null> Timer#rule-lq1iq5i3 just a note: I'm setting a delay of only 8ms (from 1715196045347<5/8/2024, 9:20:45 PM> to 1715196045355<5/8/2024, 9:20:45 PM>)
2024/05/08 21:20:42	stdout	[userauth-24120]2024-05-08T19:20:42.093Z <Timer:null> Timer#rule-lq5ri09p just a note: I'm setting a delay of only 8ms (from 1715196042093<5/8/2024, 9:20:42 PM> to 1715196042101<5/8/2024, 9:20:42 PM>)
2024/05/08 21:19:04	stdout	[userauth-24120]2024-05-08T19:19:04.547Z <Timer:null> Timer#rule-lq5rgx5t just a note: I'm setting a delay of only 8ms (from 1715195944547<5/8/2024, 9:19:04 PM> to 1715195944555<5/8/2024, 9:19:04 PM>)
2024/05/08 21:19:02	stdout	[userauth-24120]2024-05-08T19:19:02.765Z <Timer:null> Timer#rule-lq5rhvua just a note: I'm setting a delay of only 8ms (from 1715195942765<5/8/2024, 9:19:02 PM> to 1715195942773<5/8/2024, 9:19:02 PM>)
2024/05/08 21:19:02	stdout	[userauth-24120]2024-05-08T19:19:02.153Z <EzloController:null> remapped item action to [Object]{ "item": "switch", "value": true, "method": "hub.item.value.set", "parameters": { "value": { "value": true } } }
2024/05/08 21:19:01	stdout	[userauth-24120]2024-05-08T19:19:01.110Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715195941110<5/8/2024, 9:19:01 PM> to 1715195941118<5/8/2024, 9:19:01 PM>)
2024/05/08 21:18:59	stdout	[userauth-24120]2024-05-08T19:18:59.226Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195939226<5/8/2024, 9:18:59 PM> to 1715195939234<5/8/2024, 9:18:59 PM>)
2024/05/08 21:17:10	stdout	[userauth-24120]2024-05-08T19:17:10.678Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715195830678<5/8/2024, 9:17:10 PM> to 1715195830686<5/8/2024, 9:17:10 PM>)
2024/05/08 21:14:44	stdout	[userauth-24120]2024-05-08T19:14:44.540Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195684540<5/8/2024, 9:14:44 PM> to 1715195684548<5/8/2024, 9:14:44 PM>)
2024/05/08 21:09:18	stdout	[userauth-24120]2024-05-08T19:09:18.150Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715195358150<5/8/2024, 9:09:18 PM> to 1715195358158<5/8/2024, 9:09:18 PM>)
2024/05/08 21:05:44	stdout	[userauth-24120]2024-05-08T19:05:44.738Z <Timer:null> Timer#rule-ks56ms0b just a note: I'm setting a delay of only 8ms (from 1715195144738<5/8/2024, 9:05:44 PM> to 1715195144746<5/8/2024, 9:05:44 PM>)
2024/05/08 21:05:44	stdout	[userauth-24120]2024-05-08T19:05:44.719Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195144719<5/8/2024, 9:05:44 PM> to 1715195144727<5/8/2024, 9:05:44 PM>)
2024/05/08 21:00:16	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 21:00:14	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log size hit rotation limit, rotating
2024/05/08 20:59:52	stdout	[userauth-24120]2024-05-08T18:59:52.886Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715194792886<5/8/2024, 8:59:52 PM> to 1715194792894<5/8/2024, 8:59:52 PM>)
2024/05/08 20:58:22	stdout	[userauth-24120]2024-05-08T18:58:22.585Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715194702585<5/8/2024, 8:58:22 PM> to 1715194702593<5/8/2024, 8:58:22 PM>)
2024/05/08 20:56:26	stdout	[userauth-24120]2024-05-08T18:56:26.917Z <Timer:null> Timer#rule-lq5rh1ns just a note: I'm setting a delay of only 8ms (from 1715194586917<5/8/2024, 8:56:26 PM> to 1715194586925<5/8/2024, 8:56:26 PM>)
2024/05/08 20:56:06	stdout	[userauth-24120]2024-05-08T18:56:06.581Z <Timer:null> Timer#rule-lq1iq5i3 just a note: I'm setting a delay of only 8ms (from 1715194566581<5/8/2024, 8:56:06 PM> to 1715194566589<5/8/2024, 8:56:06 PM>)
2024/05/08 20:54:49	stdout	[userauth-24120]2024-05-08T18:54:49.514Z <Timer:null> Timer#rule-lq5rgx5t just a note: I'm setting a delay of only 8ms (from 1715194489514<5/8/2024, 8:54:49 PM> to 1715194489522<5/8/2024, 8:54:49 PM>)
2024/05/08 20:54:49	stdout	[userauth-24120]2024-05-08T18:54:49.058Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715194489058<5/8/2024, 8:54:49 PM> to 1715194489066<5/8/2024, 8:54:49 PM>)
2024/05/08 20:54:43	stdout	[userauth-24120]2024-05-08T18:54:43.027Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715194483027<5/8/2024, 8:54:43 PM> to 1715194483035<5/8/2024, 8:54:43 PM>)
2024/05/08 20:50:44	stdout	[userauth-24120]2024-05-08T18:50:44.225Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715194244225<5/8/2024, 8:50:44 PM> to 1715194244233<5/8/2024, 8:50:44 PM>)
2024/05/08 20:50:43	stdout	[userauth-24120]2024-05-08T18:50:43.256Z <EzloController:null> remapped item action to [Object]{ "item": "dimmer", "value_expr": "min(100,max(0,floor(parameters.level*100+0.5)))", "method": "hub.item.value.set", "parameters": { "value": { "value_expr": "min(100,max(0,floor(parameters.level*100+0.5)))" } } }
2024/05/08 20:47:23	stdout	[userauth-24120]2024-05-08T18:47:23.713Z <Timer:null> Timer#rule-ks56ms0b just a note: I'm setting a delay of only 8ms (from 1715194043713<5/8/2024, 8:47:23 PM> to 1715194043721<5/8/2024, 8:47:23 PM>)
2024/05/08 20:47:23	stdout	[userauth-24120]2024-05-08T18:47:23.693Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715194043693<5/8/2024, 8:47:23 PM> to 1715194043701<5/8/2024, 8:47:23 PM>)
2024/05/08 20:47:22	stdout	[userauth-24120]2024-05-08T18:47:22.392Z <EzloController:null> remapped item action to [Object]{ "item": "switch", "value": false, "method": "hub.item.value.set", "parameters": { "value": { "value": false } } }
2024/05/08 20:46:10	stdout	[userauth-24120]2024-05-08T18:46:09.716Z <default:null> Module NotifyAlert v21092
2024/05/08 20:46:10	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 20:46:10	stdout	[userauth-24120]2024-05-08T18:46:09.704Z <default:null> Module NotifyPushover v21195
2024/05/08 20:46:10	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 20:46:10	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 20:46:10	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 20:46:10	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log size hit rotation limit, rotating
2024/05/08 20:46:09	stdout	[userauth-24120]2024-05-08T18:46:09.014Z <Notifier:null> Module Notifier v22283
2024/05/08 20:46:06	stdout	    at /opt/reactor/server/lib/VirtualEntityController.js:357:319
2024/05/08 20:46:06	stdout	    at VirtualEntityController._load_devices (/opt/reactor/server/lib/VirtualEntityController.js:644:114)
2024/05/08 20:46:06	stdout	    at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:563:19)
2024/05/08 20:46:06	stdout	Error: Invalid primary attribute assignment; capability not assigned (state_sensor.value)
2024/05/08 20:46:06	stdout	[userauth-24120]2024-05-08T18:46:06.542Z <VirtualEntityController:CRIT> Error: Invalid primary attribute assignment; capability not assigned (state_sensor.value) [-]
2024/05/08 20:46:06	stdout	    at /opt/reactor/server/lib/VirtualEntityController.js:357:319
2024/05/08 20:46:06	stdout	    at VirtualEntityController._load_devices (/opt/reactor/server/lib/VirtualEntityController.js:644:114)
2024/05/08 20:46:06	stdout	    at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:563:19)
2024/05/08 20:46:06	stdout	Error: Invalid primary attribute assignment; capability not assigned (string_sensor.value)
2024/05/08 20:46:06	stdout	[userauth-24120]2024-05-08T18:46:06.541Z <VirtualEntityController:CRIT> Error: Invalid primary attribute assignment; capability not assigned (string_sensor.value) [-]
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.410Z <VirtualEntityController:null> Module VirtualEntityController v24117
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.391Z <SystemController:null> Module SystemController v24076
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.382Z <OWMWeatherController:null> Module OWMWeatherController v22294
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.161Z <EzloController:null> Module EzloController v23345
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.090Z <VeraController:null> Module VeraController v24050
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.089Z <TaskQueue:null> Module TaskQueue 24113
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.993Z <HassController:null> Module HassController v24115
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.726Z <InfluxFeed:null> Module InfluxFeed v23341
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.682Z <wsapi:null> Module wsapi v24115
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.439Z <httpapi:null> Module httpapi v24119
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.231Z <Engine:null> Module Engine v24113
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.229Z <GlobalReaction:null> Module GlobalReaction v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.197Z <Rule:null> Module Rule v24115
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.176Z <AlertManager:null> Module AlertManager v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.107Z <Predicate:null> Module Predicate v23093
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.045Z <GlobalExpression:null> Module GlobalExpression v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.023Z <default:null> Module Rulesets v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.022Z <default:null> Module Ruleset v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.952Z <Controller:null> Module Controller v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.929Z <Entity:null> Module Entity v24108
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.925Z <TimerBroker:null> Module TimerBroker v22283
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.460Z <Plugin:null> Module Plugin v22300
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.311Z <Capabilities:null> Module Capabilities v23331
2024/05/08 20:46:03	stdout	[userauth-24120]2024-05-08T18:46:03.269Z <Structure:null> Module Structure v24110
2024/05/08 20:46:03	stdout	[userauth-24120]2024-05-08T18:46:03.059Z <app:null> Local date/time using configured timezone and locale formatting is "5/8/2024, 8:46:03 PM"
2024/05/08 20:46:03	stdout	[userauth-24120]2024-05-08T18:46:03.058Z <app:null> Loaded locale en-US for en-US
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.890Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.750Z <app:null> Resolved timezone=Europe/Rome, environment TZ=Europe/Rome; offset minutes from UTC=120
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.656Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.656Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.656Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined)
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.584Z <app:null> Reactor build userauth-24120-7745fb8d starting on v20.10.0 /usr/local/bin/node
2024/05/08 20:46:02	stdout	NODE_PATH /opt/reactor:/opt/reactor/node_modules
2024/05/08 20:46:02	stdout	Reactor userauth-24120-7745fb8d app 24120 configuration from /var/reactor/config

Hi, I used Portainer to change the image from latest to userauth and it was easy and thanks for this update!

current configuration:
Synology NAS/Docker/Reactor (Multi-hub) userauth-24120-7745fb8d

unexpected:
when I try to log in on http://10.0.0.1:8111/dashboard/ as admin:admin, I'm redirect to reactor http://10.0.0.1:8111/reactor/en-US/ and not to dashboard
This happens on Chrome and Edge

Features/suggestion that I image:

Guest user has access to:
all dashboard set to public (homescreen - all public group tile - all public single tile)

where group tile are rooms/hubs/virtual/weather on homescreen dashboard
and single tile are all the entities: devices/virtual devices/etc

Admin can use option on tile VISIBLE/HIDDEN icon by clicking on it.

If a tile is set to HIDDEN, all entities associated with it will also be hidden. Setting VISIBLE on specific entities will not be respected. Setting hidden on specific entities it will be not visible to guests.
So Public means VISIBLE.

imaging it:

@toggledbits happy to help!

I'm running Reactor>Docker>Synology NAS

ops, soorry! now it is in signature too.

Reactor (Multi-hub) latest-23338-170ea0c7
Docker - Synology NAS

Thanks to you!!!
Lines are added

another idea for the future:
a gauge range applied to ValueSensor or Weather in simple text color:
RED text for value out of range min/max

or

glabal expression

xB1_IndiceThom_ID = round( float( xB1_Temp_01_ID ) - (0.55-0.0055 *  float( xB1_Humidity_01_ID )) * ( float( xB1_Temp_01_ID ) - 14.5) , 1)

reactor.yaml

        -
          id: testA_dynamic_vec
          name: TestA Dynamic Vec Value
          capabilities:
            value_sensor:
              attributes:
                value:
                  expr: xB1_IndiceThom_ID

dashboard

@toggledbits

Reactor (Multi-hub) latest-23338-170ea0c7
Docker - Synology NAS

Global expression

xB1_Temp_01_ID = getEntity( "ezlo>device_626d5f9f129e2912444634a4" ).attributes.temperature_sensor.value

xB1_Humidity_01_ID = getEntity( "ezlo>device_626d5f9f129e2912444634a0" ).attributes.humidity_sensor.value

in reactor.yaml

-
          id: testA_dynamic_vec
          name: TestA Dynamic Vec Value
          capabilities:
            value_sensor:
              attributes:
                value:
                  expr: round( float( xB1_Temp_01_ID ) - (0.55-0.0055 *  float( xB1_Humidity_01_ID )) * ( float( xB1_Temp_01_ID ) - 14.5) , 1)

in dashboard