I'll check out Telegram and Pushover. Thanks for the suggestions.
-
Post has been updated.
Need some guidance in determining what this error means.
Running Reactor latest-23078-d592d400; ZWaveJSController; Docker on Synology; Home Assistant 2023.3.6; Z-Wave JS UI 8.11.1
I have searched the site and could not find anything related to my question.
I know what the rule does. Yet, I cannot find the relationship with this error.
If someone could point me in the right direction, it would be appreciated.
Thanks in advance
Rule is as follow:
If the garage side door opens when the alarm is not armed and that both my spouse and I are at home:
Set Reaction: turn on the Siren_8 (basically a two seconds beep that was configured with the Aeotec Siren to warn us that the door is open)
Reset Reaction: turn off the Siren_8 in case it wants to keep beeping
Here's the updated error.
[latest-23078]2023-03-26T22:31:36.772Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:36.772Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:36.773Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.773Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.782Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.783Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.790Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.791Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.799Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:36.799Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:36.800Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:36.800Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:36.800Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:36.801Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.802Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (false), but rule state remains RESET [latest-23078]2023-03-26T22:31:36.804Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.804Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.812Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:36.812Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:36.814Z <Engine:INFO> Enqueueing "Door Sensors State<RESET>" (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:36.815Z <Engine:INFO> Enqueueing "Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET>" (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:36.817Z <Engine:INFO> Enqueueing "Toggle Vestibule scene 003 LED color state between green/blue<RESET>" (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:36.819Z <Engine:NOTICE> Starting reaction Door Sensors State<RESET> (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:36.820Z <Engine:NOTICE> Starting reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:36.822Z <Engine:NOTICE> Starting reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:36.823Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Switch#zwavejs>128-0 with [Object]{ "parameter": "9", "size": 1, "value": 2, "bitmask": 0 } [latest-23078]2023-03-26T22:31:36.830Z <HassController:INFO> HassController#hass action x_hass_input_text.set_value([Object]{ "value": "Closed" }) on Entity#hass>input_text_h_door_sensors_state succeeded [latest-23078]2023-03-26T22:31:36.831Z <Engine:INFO> Resuming reaction Door Sensors State<RESET> (rule-lerjv6if:R) from step 1 [latest-23078]2023-03-26T22:31:36.832Z <Engine:INFO> Door Sensors State<RESET> all actions completed. [latest-23078]2023-03-26T22:31:37.043Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) starting evaluation; because entity-changed ValueSensor#hass>sensor_garage_side_door_openclose_battery_level [latest-23078]2023-03-26T22:31:37.044Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_garage_side_door_openclose_battery_level [latest-23078]2023-03-26T22:31:37.045Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) trigger evaluation result is true (previously true) [latest-23078]2023-03-26T22:31:37.046Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) evaluated; trigger state unchanged (true); rule state remains SET [latest-23078]2023-03-26T22:31:37.060Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) trigger evaluation result is true (previously true) [latest-23078]2023-03-26T22:31:37.060Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluated; trigger state unchanged (true); rule state remains SET [latest-23078]2023-03-26T22:31:37.062Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:37.062Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:37.146Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) starting evaluation; because entity-changed Group#groups>low_battery [latest-23078]2023-03-26T22:31:37.156Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) trigger evaluation result is true (previously true) [latest-23078]2023-03-26T22:31:37.157Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluated; trigger state unchanged (true); rule state remains SET [latest-23078]2023-03-26T22:31:37.157Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:37.161Z <Engine:INFO> Resuming reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) from step 2 [latest-23078]2023-03-26T22:31:37.162Z <Engine:INFO> Toggle Vestibule scene 003 LED color state between green/blue<RESET> all actions completed. [latest-23078]2023-03-26T22:31:37.316Z <HassController:INFO> HassController#hass action x_hass_siren.turn_off([Object]{ }) on Entity#hass>siren_siren_8 succeeded [latest-23078]2023-03-26T22:31:37.317Z <Engine:INFO> Resuming reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> (rule-lbmoup28:R) from step 2 [latest-23078]2023-03-26T22:31:37.317Z <Engine:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> all actions completed. [latest-23078]2023-03-26T22:31:38.892Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:38.892Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:38.893Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:38.894Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.894Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.907Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.907Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.916Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.917Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.925Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:38.925Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:38.926Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:38.926Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:38.926Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:38.927Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.930Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) constraints not met! [latest-23078]2023-03-26T22:31:38.930Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (true), but rule state remains RESET [latest-23078]2023-03-26T22:31:38.931Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.932Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.939Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:38.939Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:38.941Z <Engine:INFO> Enqueueing "Door Sensors State<SET>" (rule-lerjv6if:S) [latest-23078]2023-03-26T22:31:38.942Z <Engine:INFO> Enqueueing "Notification: Home Security - Garage side door just opened (Disarmed Only)<SET>" (rule-lbmoup28:S) [latest-23078]2023-03-26T22:31:38.943Z <Engine:INFO> Enqueueing "Toggle Vestibule scene 003 LED color state between green/blue<SET>" (rule-lfn441bq:S) [latest-23078]2023-03-26T22:31:38.945Z <Engine:NOTICE> Starting reaction Door Sensors State<SET> (rule-lerjv6if:S) [latest-23078]2023-03-26T22:31:38.946Z <Engine:NOTICE> Starting reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<SET> (rule-lbmoup28:S) [latest-23078]2023-03-26T22:31:38.948Z <Engine:NOTICE> Starting reaction Toggle Vestibule scene 003 LED color state between green/blue<SET> (rule-lfn441bq:S) [latest-23078]2023-03-26T22:31:38.949Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Switch#zwavejs>128-0 with [Object]{ "parameter": "9", "size": 1, "value": 1, "bitmask": 0 } [latest-23078]2023-03-26T22:31:38.956Z <HassController:INFO> HassController#hass action x_hass_input_text.set_value([Object]{ "value": "Open" }) on Entity#hass>input_text_h_door_sensors_state succeeded [latest-23078]2023-03-26T22:31:38.957Z <Engine:INFO> Resuming reaction Door Sensors State<SET> (rule-lerjv6if:S) from step 1 [latest-23078]2023-03-26T22:31:38.958Z <Engine:INFO> Door Sensors State<SET> all actions completed. [latest-23078]2023-03-26T22:31:39.284Z <Engine:INFO> Resuming reaction Toggle Vestibule scene 003 LED color state between green/blue<SET> (rule-lfn441bq:S) from step 2 [latest-23078]2023-03-26T22:31:39.284Z <Engine:INFO> Toggle Vestibule scene 003 LED color state between green/blue<SET> all actions completed. [latest-23078]2023-03-26T22:31:39.530Z <HassController:INFO> HassController#hass action x_hass_siren.turn_on([Object]{ "tone": "30" }) on Entity#hass>siren_siren_8 succeeded [latest-23078]2023-03-26T22:31:39.531Z <Engine:INFO> Resuming reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<SET> (rule-lbmoup28:S) from step 2 [latest-23078]2023-03-26T22:31:39.531Z <Engine:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only)<SET> all actions completed. [latest-23078]2023-03-26T22:31:40.341Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_siren_siren_active_8 [latest-23078]2023-03-26T22:31:40.351Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:40.352Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:40.353Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:40.645Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) starting evaluation; because entity-changed Group#groups>water_leak_detected [latest-23078]2023-03-26T22:31:40.654Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:40.654Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:40.655Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.311Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:41.312Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:41.313Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:41.315Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.315Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.327Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.327Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.335Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.336Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.343Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:41.343Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:41.344Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:41.344Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:41.344Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.345Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.346Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (false), but rule state remains RESET [latest-23078]2023-03-26T22:31:41.347Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.348Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.354Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:41.355Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:41.356Z <Engine:INFO> Enqueueing "Door Sensors State<RESET>" (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:41.357Z <Engine:INFO> Enqueueing "Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET>" (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:41.360Z <Engine:INFO> Enqueueing "Toggle Vestibule scene 003 LED color state between green/blue<RESET>" (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:41.361Z <Engine:NOTICE> Starting reaction Door Sensors State<RESET> (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:41.363Z <Engine:NOTICE> Starting reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:41.365Z <Engine:NOTICE> Starting reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:41.366Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Switch#zwavejs>128-0 with [Object]{ "parameter": "9", "size": 1, "value": 2, "bitmask": 0 } [latest-23078]2023-03-26T22:31:41.374Z <HassController:INFO> HassController#hass action x_hass_input_text.set_value([Object]{ "value": "Closed" }) on Entity#hass>input_text_h_door_sensors_state succeeded [latest-23078]2023-03-26T22:31:41.375Z <Engine:INFO> Resuming reaction Door Sensors State<RESET> (rule-lerjv6if:R) from step 1 [latest-23078]2023-03-26T22:31:41.375Z <Engine:INFO> Door Sensors State<RESET> all actions completed. [latest-23078]2023-03-26T22:31:41.497Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_docker_hub [latest-23078]2023-03-26T22:31:41.498Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:41.498Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:41.499Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.501Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_docker_hub_update_available [latest-23078]2023-03-26T22:31:41.502Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:41.502Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:41.503Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.709Z <Engine:INFO> Resuming reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) from step 2 [latest-23078]2023-03-26T22:31:41.709Z <Engine:INFO> Toggle Vestibule scene 003 LED color state between green/blue<RESET> all actions completed. [latest-23078]2023-03-26T22:31:49.669Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.670Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.670Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.670Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:49.675Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.675Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.676Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.676Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:49.678Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.679Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.679Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.680Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:49.682Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.683Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.683Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.683Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:52.484Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_siren_siren_active_8 [latest-23078]2023-03-26T22:31:52.485Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:52.485Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:52.486Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:52.502Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:52.502Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:52.505Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.505Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.515Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.515Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.524Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.525Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.537Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:52.539Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:52.540Z <HassController:INFO> HassController#hass action x_hass_siren.turn_off([Object]{ }) on Entity#hass>siren_siren_8 succeeded [latest-23078]2023-03-26T22:31:52.541Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.542Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) constraints not met! [latest-23078]2023-03-26T22:31:52.542Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (true), but rule state remains RESET [latest-23078]2023-03-26T22:31:52.544Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.544Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.551Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:52.552Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:52.565Z <Engine:NOTICE> [Engine]Engine#1 entry 171 reaction rule-lbmoup28:R: [Error] terminated [-] [latest-23078]2023-03-26T22:31:52.565Z <Engine:CRIT> Error: terminated [-] Error: terminated at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:1555:47) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) -
I know this Forum has never focused much on SmartThings or Hubitat, thus not surprisingly I find virtually nothing here concerning the Groovy programming language or creating drivers/apps for those platforms.
I'm curious: Is there any interest at all for co-authoring a "Definitive Guide to Coding Drivers & Apps for Hubitat" among our motley crew?
-
Hello guys. I'm currently building my own home and i want it to be kind of high tech and cool but i have actually never owned a smart device other than a smartphone and an old smart TV so i don't even know what exactly am i looking for. I will explain my idea and i am looking forward to somebody shining some light.
Sooo - i was thinking about getting a WiFi controlled AC, TV, Washing machine, Dryer and smart switches for the lights. I suppose i need some kind of a assistant that connects to the wifi and can control all of these. Also i want an audio system - for the TV in the living room aaaand i also want to have 2 speakers in the bathroom which i have no idea where i would connect. I guees i need some kind of a receiver and amplifier for them to work correctly. But i also want that reciever to be hidden somewhere so it ahould be small and it also should be able to connect to the wifi i guess.
So wgat exactly do i need so far. Would any wifi device connect to any assistant? Or am i lookng for particullar stuff... Will i be able for example to turn on my AC from outside the household for example when im at work? And can i also connect an alarm system of some type? -
ChatGPT samples:
Me:
Tell me about an iot program called openLuup.
It:
OpenLuup is an open source home automation system that is built on the VeraLuup platform. It is designed to be easy to install and configure, and provides users with a powerful and versatile way to control their home automation devices. OpenLuup offers a wide range of features, including support for many popular home automation devices, scheduling, scripting, and integration with other services. OpenLuup is designed to be customizable, allowing users to create their own home automation systems. It is an excellent choice for those looking to create their own home automation system without spending a lot of money.
Me:
Write an iot program using openLuup.
It:
--openLuup IoT Program-- -- Initialize Variables -- local device_id = "MyHomeDevice" local temperature_sensor_id = "MyTemperatureSensor" local temperature_threshold = 75 -- Create Devices -- luup.create_device("OpenLuup Temperature Sensor", 0, device_id, "D_GenericSensor1.xml", "I_GenericSensor1.xml", "S_TemperatureSensor1.xml", "") luup.variable_set("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 0, device_id) -- Start Timer -- luup.call_delay("check_temperature", 10, "", false) --Function to Check Temperature-- function check_temperature() local current_temperature = luup.variable_get(temperature_sensor_id, "CurrentTemperature", 0) --Check Temperature Threshold-- if current_temperature >= temperature_threshold then --Send Alert-- luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "SendTextMessage", {PhoneNumber="1234567890", Message="ALERT! Temperature exceeded threshold!"}, 0) end --Reset Timer-- luup.call_delay("check_temperature", 10, "", false) endMe:
Write an iot program using openLuup.
It:
Write an iot program using openLuup. -- openLuup IOT Program -- -- Variables local lampState = false local lampTime = 0 -- Functions function lampTimer() if lampTime > 0 then lampTime = lampTime - 1 if lampTime == 0 then luup.variable_set('urn:upnp-org:serviceId:SwitchPower1', 'Status', 0, lampDeviceID) lampState = false end end end -- Setup luup.call_delay('lampTimer', 60, 0) -- Main Loop while true do -- Check for motion if luup.variable_get('urn:micasaverde-com:serviceId:MotionSensor1', 'Tripped', motionSensorDeviceID) == '1' then if not lampState then luup.variable_set('urn:upnp-org:serviceId:SwitchPower1', 'Status', 1, lampDeviceID) lampState = true -- Set lamp timer to 5 minutes lampTime = 300 end end luup.sleep(1) endWhat??
luup.sleep(1)Not good - looks like I still have some semblance of a job to fulfill.
Me:
An iot program called openLuup was written by akbooer. Who is akbooer?
It: (note: answer redacted and as I understand it, also incorrect re: AltUI):
akbooer is the pseudonym of the software developer and home automation enthusiast. He is the creator of the openLuup home automation software, which is an open-source version of the Vera home automation system. He is also the creator of the AltUI graphical user interface for openLuup.
Me:
Who created of the AltUI graphical user interface for openLuup.
and
Me:
Who created of the AltUI graphical user interface for the home automation system Vera.
Names two different people - mmmm.
Regardless very impressive - give it a few more years.
-
Some background
I have MQTTController based entities that I want to use in time calculations in my rules. These entities represent two separate time ranges, one for the weekdays and the other for the weekends. In this particular example they are used to control my doorbell activity (whether it's enabled or disabled).
MQTT message which is used to update the entities. NOTE: time is in 24h format
{ "data": { "weekdays": { "enable": "09:28", "disable": "20:00" }, "weekends": { "enable": "09:00", "disable": "21:00" } } }Entity definitions (here's only the definition for the weekdays for brevity)
doorbell-weekdays-enable: name: 'Ovikello päälle (arkisin)' topic: 'doorbell/settings' capabilities: - string_sensor primary_attribute: string_sensor.value events: "%topic%": "string_sensor.value": json_payload: true expr: "payload.data.weekdays.enable" doorbell-weekdays-disable: name: 'Ovikello pois päältä (arkisin)' topic: 'doorbell/settings' capabilities: - string_sensor primary_attribute: string_sensor.value events: "%topic%": "string_sensor.value": json_payload: true expr: "payload.data.weekdays.disable"I have verified that the entities are populated correctly and the values are working in local expressions.
The entity (only the range start for brevity):
Screenshot from 2023-03-22 09-27-54.pngThe rule:
Screenshot from 2023-03-22 09-28-28.pngAnd the local expression within the rule:
weekdays_enabled = (time() >= time(getEntity( "mqtt>doorbell-weekdays-enable" ).attributes.string_sensor.value )) && (time() <= time(getEntity( "mqtt>doorbell-weekdays-disable" ).attributes.string_sensor.value ))The problem
Local expression doesn't seem to evaluate to true even if the current time gets within the range. But if the related entities are updated, then the expression is evaluated and the rule is triggered.As seen from the screenshots, the current time is 09:28:12 and the start time in corresponding entity is set to 09:28. But still the rule is not triggered. However, if I update the entity e.g. to 09:27, the local expression will get evaluated and the rule is triggered.
My understanding is that the local expression is working correctly but since it's not evaluated, it will not trigger the rule.
Is this a bug or have I misunderstood something? If so, how should I implement this kind of functionality?
br,
mgvraReactor (Multi-hub) latest-23078-d592d400 + MQTTController [0.1.23010]
-
Hi,
I am a student and recently i am working on smart home project and writing a seminar paper about the way users handle and manage IoT devices. I you have 3 min, please fill below survey. Its really short.
Thank you in advance, I really appreciate everyone's help. -
For what it's worth, I've been putting the finishing touches on a much-updated version of my DP Apps spreadsheet -- specifically intended for HE users, at least for now -- and invite you all to take a gander http://bit.ly/hedb23 at the PDF one-page version.
Corrections and edits welcome (esp. for the HOMEKIT column, just added yesterday)! Thanks in advance, especially because I'm not a big dashboard user myself, but somehow accepted this role as "keeper of the list" as it were.
-
Converting from Vera Plus to Hubitat at two different locations. The two sites are interconnected via a router-to-router VPN. I currently have a Hubitat C7 running at Site One and a Vera Plus at Site Two. The MSR Raspberry Pi is co-located with the Vera Plus at Site Two. I "activated" a Hubitat C8 (ethernet connected) at Site Two including the installation of Hub Information Driver and its associated device. I also installed a single zwave outlet module (GE ZW4202). I restarted MSR. The C8 and its associated devices appear on both the Entities page and the MSR Dashboard, but the C8 reports as down on the MSR Status page and the GE outlet does not respond when "clicked". I am not sure where to look to try to find the source of the problem and will greatly appreciate any suggestions.
-
I have a use case where I need to have a boolean variable that will be set to true/false by reactions.
I see that i can define a local variable by giving it a name and leaving the definition empty. This leaves it at state "null" until a reaction tells it that its a boolean.
Is there a way to tell it that it should start out as "false" (i.e when reactor has restarted), and not null?
Am i going about this the wrong way?
-- The use case is that I have a sensor on my fireplace, and the following logic is for notifying when its time to get up en refill with firewood.. I also want to reset the MaxInInterval to CurrentTemp when notification is sent..
1fd2951f-cb6b-4a2f-b957-1e0698171f4d-image.png dd99634e-f0ad-4878-bb87-0284c2df5535-image.png
Edit: better screenhots. Reactor version 23010-7dd2c9e9
-
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. -
Hi guys,
I want to import my reactor sensors in the MSR addon for Home Assistant, but I can't find the app.js file anywhere. So now I don't know where to put the backup file.
I have not tried to put it in the main directory (config/reactor) yet. Wanted to know if I'm the only one with the problem.
Reactor addon: v0.0.8
MSR: 23063-c464b685
Home Assistant 2023.3.3
Supervisor 2023.03.1
Operating System 9.5
Frontend 20230202.0 - latestI started with v0.0.7, have just updated everything. Still no file.
-
Home Automation means you have to have a way of describing the logical steps you want your home to implement automatically.
Whilst I've always been a fan of the Lua language, as used in Vera (and openLuup) for scenes and plugins, it's perhaps not ideal. For this reason, there has been a long development history of plugins with their own "language" to help define the automation logic: PLEG (for those with a long memory), AltUI workflows, Rules Engine, Reactor, MSR, ...
It's always seemed to me that the 'best' way of describing logic would be a language designed for that purpose – a "logic programming language". Perhaps one of the most famous, and venerable, is Prolog, which had its fiftieth birthday last year in 2022.
Thanks to some relatively recent research A Hitchhiker’s Guide to Reinventing a Prolog Machine, Paul Tarau (2017) it's become possible to implement a very efficient Prolog engine in a reasonably concise way. So, just for fun, I'm developing a CGI plugin for describing openLuup actions in Prolog.
I have an early prototype running (written in Lua, of course). It presents a web page which looks like a fairly typical Interactive Development Environment (IDE) and contains some primitives which allow basic access to the Luup engine.
Screenshot 2023-03-10 at 18.27.33.png
In a subsequent post, I'll give a glimpse of its capabilities...
-
I'm a little bit confused how to configure extended capabilities for the entities in the MQTTController.
mqtt_cababilities.yaml states that: "...You can add your own capabilities by adding a "capabilities" section to your own local_mqtt_capabilities.yaml file in your config directory."
So I did this in my local_mqtt_capabilities.yaml in the config directory:
version: 22353 revision: 1 format: 1 capabilities: x_my_config: attributes: partyMode: type: bool actions: some_action: topic: '%topic/write' payload: "some value"And in my reactor.yaml I have following configuration entry:
my-config: name: 'My custom configuration' topic: 'my-config' query: "%topic%/read" init: "%topic%/read" capabilities: - x_my_config primary_attribute: x_my_config.partyMode events: "%topic%/status": "x_my_config.partyMode": json_payload: true expr: "payload.partyMode"This sort of works but not quite. The partyMode attribute gets updated when messages arrive for that specific topic, so that's fine. But I don't see x_my_config capability in the Capabilities list in the UI and also the some_action is missing.
Screenshot from 2023-03-09 19-42-49.png
Addition to that the primary value is not set and I'm getting the following error:
Screenshot from 2023-03-09 19-30-42.pngHave I completely misunderstood the idea behind the capability extension and the attributes? If so, could someone point me to the right direction with few explanatory example configs.
What I'm trying to achieve is a set of configuration options that could be updated thru the MQTT, and also provide some actions that the rules could invoke.
Reactor (Multi-hub) latest-23063-c464b685 + MQTTController [0.1.23010]
br,
mgvra -
-
Hello guys,
I would like to achieve two different things with lights, but I am not sure it could be done. I am starting with smart things, and I am far from any electrician knowledge, wo any help is really appreciated.
I have dumb switches in my hall, controlled from 3 places. I understood that installing one smart module before first switch will make them "hybrid", both smart controlled and dumb controlled.
I would like to buy ceiling light with two bulb sockets. What I would like to achieve is I would like to have one bulb for normal daily usage (lets say cold white full brightness), and second for night time (aprox from 10pm till morning) with some red/orange - minimum brightness.
So question are:
Is there a way to keep both bulbs turning-on separated? So only one will be on during day, and then only second during night?
And could that be done with pressing dumb switch? What would I need to achieve it? (maybe another module into the ceiling lights)
Thank you in advance
-
Installing MQTTController on Home Assistant Core when Reactor is installed as an Add-In (VirtualBox)
Running Home Assistant Core under VirtualBox (on Windows) and Reactor is installed and working fine as an add-in. What I can't figure out is how to install MQTTController in this situation. I can upload the files and unzip them, but I can't run install.sh in a terminal window because npm is not a part of the Core installation.
It does appear that somewhere in the stack there is a version of docker there between VirtualBox and HA, (I see some references go by in the VirtualBox startup log) but it appears minimal and will not execute the install via the docker technique in your documentation from the VB console.
Is there a way to do this?
Thanks.
-
I've done a bit of repackaging of MSR to make it work as an add-on under Home Assistant mostly for my own purposes but hopefully it makes it a bit easier to install and get going.
GitHub - mrw298/hassio-reactor-addon GitHub - mrw298/hassio-reactor-addon
Contribute to mrw298/hassio-reactor-addon development by creating an account on GitHub.
-
I have the following issue: In my Vera, I have created a dimmer using the Switchboard plugin. I want this light always turn on at 100% brightness when turn the light on. By default, the dimmer remembers its last used setting. I have created the following scene: when the light is turned off, the LoadLevelLast should be 100.
9937e326-2453-43bd-bd32-917803b38e90-image.png
Manually, this works through the test Luup code (Lua), but not through the scene's action by execute the following Luup code.
I also tried in MSR, but no result
Does anyone know the solution to this?
-
Hi @akbooer
Just bringing this over as suggested..
I’ve started to use the console view a lot more, mainly for it’s look and simplicity , but I noticed it does not do any live updates compared to ALTUI, you have to do a full browser reload. Is that by design, or is mine not working?
Also if I want to go strait to the console view, rather than into ALTUI, I recall seeing something abut altering that in the guide by for the life of me I can’t find it. Is it possible to do, if so how would I do that..
You suggested this was something you were looking at ? Also you said You don't need a "full browser reload", just click on the display menu item to refresh the screen. - what do you mean by `display menu?
Best posts made by droy
-
RE: Messaging after VERA decoupling
-
RE: Anybody Installed MSR on unRaid Docker
If anyone else is running Dockers on unRaid and wants instructions for Installing Reactor, see below.
Installing Multi-system Reactor in a unRaid Docker Notes. 01/22/22
unRaid Version 6.9.2
Preparation:
Based on Generic Notes from:
Typically for Generic (modify with username below):
docker run --name reactor -d --restart on-failure -p 8111:8111
-v /home/username/reactor:/var/reactor
--mount type=bind,src=/etc/localtime,target=/etc/localtime
toggledbits/reactor:latest-generic-amd64Create a Share called "reactor" and use "Prefer Cache" if cache drive is available.
Under SMB settings - Export = Yes so that you can edit config files. Set security per your needs.Go to the Docker tab click Add Container and click Advanced View for additional settings.
Enter:
Name = reactorOverview = Reactor (Multi-system, aka MSR) is an automation engine for multiple home automation systems. It allows you to develop automations that respond to and control devices across platforms. For example, you could have a motion sensor on a Hubitat controller used as a trigger for set of lights, some of which are connected through a VeraPlus and some through HomeAssistant.
Please see https://reactor.toggledbits.com/docs for more information.
Repository = toggledbits/reactor:latest-generic-amd64
For Latest otherwise choose a specific versionDocker Hub URL = https://hub.docker.com/r/toggledbits/reactor
No icon path has been found
WebUI = http://[IP]:[PORT:8111]/
CPU Pinning as you see fit.
Network Type = Bridge
Console shell command = ShellWebGUI = http://[IP]:[PORT:8111]/
Extra Parameters = --restart=on-failure
Click Add another Path, Port, Variable, Label or Device.
Choose Path -
Name = data
Container Path = /var/reactor
Host Path = /mnt/user/reactor (previous share path)
Access = Read/Write
Display = Always
Required = No
Password Mask = NoClick Add another Path, Port, Variable, Label or Device.
Choose Port -
Name = Host Port 1
Container Port = 8111
Host Port = 8111
Default Value = 8111
Type = TCP
Description will auto populate with "Container Port: 8111" once Saved
Display = Yes
Required = Yes
Password Mask = No
SaveClick Add another Path, Port, Variable, Label or Device.
Choose Variable -
Name Key 1
Key = UMASK
Val and Default = 100
Description will auto populate
Display = Yes
Required = No
Password Mask = No
Save and repeat adding Variables for below:
Key 2: Container Variable: PUID = 99
Key 3: Container Variable: PGID = 100Click Apply
Script should look similar to:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='reactor' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8111:8111/tcp' -v '/mnt/user/reactor/':'/var/reactor':'rw' --restart=on-failure 'toggledbits/reactor:latest-generic-amd64'
The command finished successfully!
Notes:
- The docker manager script will add the Time Zone based on unRaid's config.
- If variables (uid/gid <> 99/100) then you must run the "New Permissions" script under Tools
and select the User Share reactor otherwise the Reactor files will be R/O except for the Docker container. - WebUI Access = "http://[your NAS IP]:8111"
- Follow the reactor configuration documentation for your Hub(s).
Regards
-
Is Hubitat to HA Bridge possible?
Greetings,
I’m researching a migration from Vera+ to Hubitat C7 and want to know if anyone has successfully connected the Hubitat to the “HA Bridge” for local Alexia calls.
The HA Bridge does not callout Hubitat natively from what I see.Thanks for your assistance.
-
RE: Why is VERA+ making calls to facebook.com?
Thanks for the quick reply.
I have facebook blocked (not a fan) and I see google.com so that must be the back up.
I don't see any option to change under the main reactor variables tab but I can live with google getting pinged. -
RE: Why is VERA+ making calls to facebook.com?
Yes, decoupled and loving it. I'm running Syslog now and have the VERA logs and backups ftp'd locally now so many thanks. I had no idea how busy the VERA device was until you look at the logs. Actually its sad to see it checking to rotate logs every minute and scanning for network devices... but I digress.
I'll go back to the docs. I do recall you writing about it, thanks again.
Latest posts made by droy
-
RE: [SOLVED] Hubitat mapped capability has no implementation error
Wild guess but I wonder of MSR is looking for the "Hub Information" app that is tied to a virtual device in Hubitat. MSR uses that to check the connection heath of the Hubitat Controller.
-
RE: Anybody Installed MSR on unRaid Docker
@3rdstng Thanks for the feedback and link to an icon. I'll save that off and put it local.
One note - I try to avoid “privileged” mode for containers. It allows it to run containers with (almost) all the capabilities of their host machine, regarding kernel features and device access.Regards
-
RE: Anybody Installed MSR on unRaid Docker
It was the latest version (22021). It was running fine but doing "npm audit fix --force" and the command you requested broke it.
To get it running again I reinstalled node.js and ran the Reactor setup scripts but I didn't like having the audit issues so I'm off of Windows now, deleted the Service and moved to a Docker.Thanks for your quick replies but you can pass on my Windows install issue.
-
RE: Anybody Installed MSR on unRaid Docker
If anyone else is running Dockers on unRaid and wants instructions for Installing Reactor, see below.
Installing Multi-system Reactor in a unRaid Docker Notes. 01/22/22
unRaid Version 6.9.2
Preparation:
Based on Generic Notes from:
Typically for Generic (modify with username below):
docker run --name reactor -d --restart on-failure -p 8111:8111
-v /home/username/reactor:/var/reactor
--mount type=bind,src=/etc/localtime,target=/etc/localtime
toggledbits/reactor:latest-generic-amd64Create a Share called "reactor" and use "Prefer Cache" if cache drive is available.
Under SMB settings - Export = Yes so that you can edit config files. Set security per your needs.Go to the Docker tab click Add Container and click Advanced View for additional settings.
Enter:
Name = reactorOverview = Reactor (Multi-system, aka MSR) is an automation engine for multiple home automation systems. It allows you to develop automations that respond to and control devices across platforms. For example, you could have a motion sensor on a Hubitat controller used as a trigger for set of lights, some of which are connected through a VeraPlus and some through HomeAssistant.
Please see https://reactor.toggledbits.com/docs for more information.
Repository = toggledbits/reactor:latest-generic-amd64
For Latest otherwise choose a specific versionDocker Hub URL = https://hub.docker.com/r/toggledbits/reactor
No icon path has been found
WebUI = http://[IP]:[PORT:8111]/
CPU Pinning as you see fit.
Network Type = Bridge
Console shell command = ShellWebGUI = http://[IP]:[PORT:8111]/
Extra Parameters = --restart=on-failure
Click Add another Path, Port, Variable, Label or Device.
Choose Path -
Name = data
Container Path = /var/reactor
Host Path = /mnt/user/reactor (previous share path)
Access = Read/Write
Display = Always
Required = No
Password Mask = NoClick Add another Path, Port, Variable, Label or Device.
Choose Port -
Name = Host Port 1
Container Port = 8111
Host Port = 8111
Default Value = 8111
Type = TCP
Description will auto populate with "Container Port: 8111" once Saved
Display = Yes
Required = Yes
Password Mask = No
SaveClick Add another Path, Port, Variable, Label or Device.
Choose Variable -
Name Key 1
Key = UMASK
Val and Default = 100
Description will auto populate
Display = Yes
Required = No
Password Mask = No
Save and repeat adding Variables for below:
Key 2: Container Variable: PUID = 99
Key 3: Container Variable: PGID = 100Click Apply
Script should look similar to:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='reactor' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8111:8111/tcp' -v '/mnt/user/reactor/':'/var/reactor':'rw' --restart=on-failure 'toggledbits/reactor:latest-generic-amd64'
The command finished successfully!
Notes:
- The docker manager script will add the Time Zone based on unRaid's config.
- If variables (uid/gid <> 99/100) then you must run the "New Permissions" script under Tools
and select the User Share reactor otherwise the Reactor files will be R/O except for the Docker container. - WebUI Access = "http://[your NAS IP]:8111"
- Follow the reactor configuration documentation for your Hub(s).
Regards
-
RE: Anybody Installed MSR on unRaid Docker
I ran that and now the Reactor Windows Service Terminates unexpectedly.
*** I was able to install MSR in a Docker on unRaid so the details below are for your reference only as I plan on uninstalling Reactor in Windows. ***
Event Log Shows - ''Child process [7664 - C:\Program Files\nodejs\node.exe C:\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined] finished with 1''
''C:\reactor>npm i --no-save --omit dev
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'jsdoc@0.0.0',
npm WARN EBADENGINE required: { node: '~v0.4.10' },
npm WARN EBADENGINE current: { node: 'v16.13.1', npm: '8.1.2' }
npm WARN EBADENGINE }removed 5 packages, and audited 90 packages in 1s
12 packages are looking for funding
runnpm fund
for details1 high severity vulnerability
To address all issues (including breaking changes), run:
npm audit fix --forceRun
npm audit
for details.'' -
Anybody Installed MSR on unRaid Docker
Greetings,
I'm not a Docker expert hence the choice of using unRaid but I would like to install MSR in a Docker and I'm looking for details on the settings used as I have not installed one manually yet.
I have installed MSR on Windows Server 2019 but I'm receiving (3 vulnerabilities (1 low, 2 high)) error messages with 'npm' and the audit fix breaks it ('npm').
Thanks for any help you can provide.
David
-
RE: Is Hubitat to HA Bridge possible?
@therealdb Good point, I'll look into Hubitat's interfacing option more closely. I know that MSR is using a Hubitat "Maker" API to call device changes.
-
RE: Is Hubitat to HA Bridge possible?
Thanks for the responses but I was hoping to keep the system local (not Amazon cloud) by using the HA Bridge like I have connected to Vera (https://www.bwssystems.com/#/habridge).
The developers of the HA-Bridge added Hubs such as Vera and Home Assistant + others but left out Hubitat.
I have it running on a Pi 3B and it acts as a bridge between to Alexia exposing the devices on Vera and making calls to the Hub based on voice commands. -
Is Hubitat to HA Bridge possible?
Greetings,
I’m researching a migration from Vera+ to Hubitat C7 and want to know if anyone has successfully connected the Hubitat to the “HA Bridge” for local Alexia calls.
The HA Bridge does not callout Hubitat natively from what I see.Thanks for your assistance.
-
RE: Why is VERA+ making calls to facebook.com?
Yes, decoupled and loving it. I'm running Syslog now and have the VERA logs and backups ftp'd locally now so many thanks. I had no idea how busy the VERA device was until you look at the logs. Actually its sad to see it checking to rotate logs every minute and scanning for network devices... but I digress.
I'll go back to the docs. I do recall you writing about it, thanks again.