• Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
Upcoming Release -- Plan for the Future
toggledbitsT

Beginning with the next Reactor release, there will be some dependency changes and new deprecations.

These apply to users on bare-metal installs only. If you are running Reactor in a docker container, the following does not apply to you — the container supplies its own dependencies and will be up-to-date.

All versions of nodejs prior to 18 are now end-of-life (no maintenance), so starting with the next Reactor build, they are deprecated for use with Reactor; they will continue to work until March 1 2024 (about 3 months from now), so you need to upgrade before that date. The recommended version of nodejs is 20, which is the current long-term support (LTS) version (EOL in mid-2026). Version 18 is the prior LTS version and still supported (by OpenJS Foundation and Reactor) until mid-2025, so it's a good fallback if you have issues getting version 20 running. As of this writing, the current 20 is 20.10.0, and the current 18 is 18.18.2. Both have been tested with Reactor 23302.

Now, nodejs version 20.9.0 seems to have dependencies that are not easily resolved on Raspberry Pi OS (formerly Raspbian) Buster (Debian 10). If you are using an RPi running Buster, you should select nodejs 18. That gives you until mid-2025 to upgrade both nodejs and the RPi OS to a more modern version (the current RPi OS is bookworm, Debian 12, 64-bit). The tools/rpi-install.sh script will be enhanced for the next build to try to discern what is reasonable for your system and make the appropriate upgrades; it is safe to run even on a current Reactor install.

If you are running an OS other than Raspberry Pi OS, try for nodejs 20, but use 18 as a fallback if you can't get it installed and running.

Multi-System Reactor
Honeywell TH6320ZW2003_T6_Pro_ZWave shows hvac_control.state="heat" in zwaveJSController
SnowmanS

@togglebits I have another one for you.

HASS controller shows hvac_control.state="heating, cooling or idle".

ZWaveJSController controller shows hvac_control.state="heat, cool, or idle"

I believe hvac_control.state="heating, cooling or idle" should be what the ZWaveJSController should show.

"heat", "cool" or "off" are values assigned to the hvac_control.mode attribute.

Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the thermostat in hopes it can help.

Thanks in advance.

Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3

battery_power.level=0.95 battery_power.since=1700301347874 humidity_sensor.units="%" humidity_sensor.value=40 hvac_blower_unit.filter_change=null hvac_blower_unit.mode="low" hvac_blower_unit.state=true hvac_control.mode="heat" hvac_control.state="heat" hvac_cooling_unit.setpoint=23.5 hvac_cooling_unit.state=false hvac_cooling_unit.units="°C" hvac_heating_unit.setpoint=20.5 hvac_heating_unit.state=false hvac_heating_unit.units="°C" power_source.source=null temperature_sensor.units="°C" temperature_sensor.value=20.5 x_debug.dt={"entity_class":"Thermostat","match":"deviceClass.generic.key=8","capabilities":["hvac_control"],"primary_attribute":"hvac_control.state","description":"T6 Pro Z-Wave Programmable Thermostat","model":"TH6320ZW","default_name":"Honeywell T6 Pro Thermostat","values":[{"valueId":"113:Power Management:Mains status","capabilities":{"power_source":{"attributes":{"source":{"expr":"([ 'unknown', 'unknown', 'dc', 'ac' ])[value ?# 0] ?? 'unknown'","update_only":true}}}}}],"manufacturerId":57,"productType":17,"productId":8} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=95 x_zwave_values.Configuration_Adaptive_Intelligent_Recovery=1 x_zwave_values.Configuration_Air_Filter_1_Reminder=0 x_zwave_values.Configuration_Air_Filter_2_Reminder=0 x_zwave_values.Configuration_Air_Filters=1 x_zwave_values.Configuration_Auto_Changeover=0 x_zwave_values.Configuration_Auto_Differential=0 x_zwave_values.Configuration_Aux_Heat_Cycle_Rate=9 x_zwave_values.Configuration_Aux_Heat_Outdoor_Lockout=0 x_zwave_values.Configuration_Auxiliary_Emergency_Control=0 x_zwave_values.Configuration_Auxiliary_Heat_Droop=0 x_zwave_values.Configuration_Auxiliary_Heat_Type=0 x_zwave_values.Configuration_Balance_Point=0 x_zwave_values.Configuration_Clock_Format=1 x_zwave_values.Configuration_Compressor_Protection=5 x_zwave_values.Configuration_Cool_Stage_1_Cycle_Rate=3 x_zwave_values.Configuration_Cool_Stage_2_Cycle_Rate=3 x_zwave_values.Configuration_Cool_Stages=1 x_zwave_values.Configuration_Daylight_Saving=1 x_zwave_values.Configuration_Dehumidification_Filter_Reminder=0 x_zwave_values.Configuration_Emergency_Heat_Cycle_Rate=9 x_zwave_values.Configuration_Emergency_Heat_Type=0 x_zwave_values.Configuration_Equipment_Type=2 x_zwave_values.Configuration_Fossil_Kit_Control=0 x_zwave_values.Configuration_Heat_Stage_1_Cycle_Rate=3 x_zwave_values.Configuration_Heat_Stage_2_Cycle_Rate=3 x_zwave_values.Configuration_Heat_Stages=1 x_zwave_values.Configuration_High_Cool_Stage_Finish=0 x_zwave_values.Configuration_High_Heat_Stage_Finish=0 x_zwave_values.Configuration_Humidification_Pad_Reminder=0 x_zwave_values.Configuration_Idle_Brightness=0 x_zwave_values.Configuration_Maximum_Heat_Temperature=75 x_zwave_values.Configuration_Minimum_Cool_Temperature=66 x_zwave_values.Configuration_Outdoor_Temperature_Sensor=0 x_zwave_values.Configuration_Reversing_Valve=0 x_zwave_values.Configuration_Schedule_Type=2 x_zwave_values.Configuration_Temperature_Offset=0 x_zwave_values.Configuration_Temperature_Scale=1 x_zwave_values.Configuration_UV_Bulb_1_Reminder=0 x_zwave_values.Configuration_UV_Bulb_2_Reminder=0 x_zwave_values.Configuration_UV_Devices=0 x_zwave_values.Configuration_Up_Stage_Timer_Aux_Heat=0 x_zwave_values.Configuration_Ventilation_Filter_Reminder=0 x_zwave_values.Manufacturer_Specific_manufacturerId=57 x_zwave_values.Manufacturer_Specific_productId=8 x_zwave_values.Manufacturer_Specific_productType=17 x_zwave_values.Multilevel_Sensor_Air_temperature=20.5 x_zwave_values.Multilevel_Sensor_Humidity=40 x_zwave_values.Notification_Power_Management_Mains_status=3 x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Thermostat_Fan_Mode_mode=1 x_zwave_values.Thermostat_Fan_Mode_off=false x_zwave_values.Thermostat_Fan_State_state=1 x_zwave_values.Thermostat_Mode_manufacturerData=null x_zwave_values.Thermostat_Mode_mode=1 x_zwave_values.Thermostat_Operating_State_state=0 x_zwave_values.Thermostat_Setpoint_setpoint_1=20.5 x_zwave_values.Thermostat_Setpoint_setpoint_11=18 x_zwave_values.Thermostat_Setpoint_setpoint_12=26 x_zwave_values.Thermostat_Setpoint_setpoint_2=23.5 x_zwave_values.Version_firmwareVersions=["1.3","1.4"] x_zwave_values.Version_hardwareVersion=1 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.61" zwave_device.capabilities=[49,64,66,67,68,69,112,113,114,128,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Thermostat" zwave_device.impl_sig="23318:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=true zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.manufacturer_info=[57,17,8] zwave_device.max_data_rate=null zwave_device.node_id=16 zwave_device.specific_class="General Thermostat V2" zwave_device.status=4 zwave_device.status_text="alive" zwave_device.version_info=[null,"1.3"]
Multi-System Reactor
Dismiss -option for updates
tunnusT

Certain MSR updates are irrelevant for some users (e.g. only Hass related changes when you are not using one), so I was wondering if there could be a dismiss (firmware) feature similar to Hubitat?

Then when you'll use "dismiss", a blue checkmark would disappear until there's a new firmware.

Multi-System Reactor
case statement with a single when clause fails
tunnusT

Noticed that if I try to use a case statement, I'll have to have multiple when clauses, otherwise I'll get syntax error.

(I tried to include a screenshot, but got parse error from the forum...)

The following works:

case when condition == true: "This is true" when condition == false: "Now it is false" else "Something else" end

But this will end up with syntax error:

case when condition == true: "This is true" else "Something else" end

Using build 23242 on Docker

Multi-System Reactor
[Solved] HTTP API no response on perform action
CrilleC

When doing something like curl -o - 'http://localhost:8111/api/v1/entity/ezlo>device_61baf509129e0725bd9f80e1/attribute/dimming.level' I get a response with current dimming level for example "0.6"
but curl -o - 'http://localhost:8111/api/v1/entity/ezlo>device_61baf509129e0725bd9f80e1/perform/dimming.set?level=0.8' sets the dimming level to 0.8 but gives no response which causes the connection to eventually timeout.

Doing it in a browser performs the action but leaves the tab with a spinning wheel of a loading page.

Is this expected behavior?

Edit: Solved in build 22142

Multi-System Reactor
CallMeBot new interface?
wmarcolinW

Hi @toggledbits

Apparently, there have been some changes to the CallMeBot interface, as the service recently stopped working for me. I've tried several configurations, and none of the ones below are working.

# CallMeBot CallMeBot: profiles: default: # description - A friendly description of this profile (for menus) description: Default Profile New # # api_url - Access URL for CallMeBot API being used api_url: http://api.callmebot.com/start.php # # api_key - (if needed) API key (use for Facebook API, WhatsApp API, etc.). # If the API you are using does not require it, leave it # commented out or blank. api_key: "177xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTGk" # # source - (if needed) Source field for some APIs. If yours does not require # it, leave it commented out or blank. #source: "source-value" # # phone - (if needed) Phone field for some APIs. If yours does not require # it, leave it commented out or blank. phone: "+5xxxxxxxx33" # # user - (if needed) User field for some APIs. If yours does not require # it, leave it commented out or blank. #user: "@xxxxxxxxxxxxx" # # lang - (optional) Language/voice; default "en-US-Standard-C". # See CallMeBot docs for possible values. lang: "en-US-Standard-C" # # rpt - (optional) Number of times to repeat message; default: 1. rpt: 2

I have already tested using the phone or the user.

Looking at the action log, I see that it starts, runs and finishes without any problems.

[latest-23302]2023-11-05T14:35:54.106Z <Engine:INFO> Enqueueing "teste<SET>" (rule-lolk0nlj:S) [latest-23302]2023-11-05T14:35:54.108Z <Engine:NOTICE> Starting reaction teste<SET> (rule-lolk0nlj:S) [latest-23302]2023-11-05T14:35:54.111Z <Engine:INFO> teste<SET> all actions completed.

When testing directly on the site, I see that it no longer uses API, and I haven't even found where to generate the API KEY.

http://api.callmebot.com/start.php?source=web&user=+5xxxxxxxx33&text=Teste callmebot pelo numero novo&lang=en-US-Standard-C

Please, can you advise me on what I should do to solve the problem?

Thanks.

Multi-System Reactor
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
SnowmanS

@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.

Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.

Thanks in advance.

Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3

battery_power.level=0.99 battery_power.since=1699401727360 binary_sensor.state=false tamper.state=true tilt_sensor.state=null x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=99 x_zwave_values.Binary_Sensor_Any=false x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0 x_zwave_values.Configuration_Send_Reports=0 x_zwave_values.Manufacturer_Specific_manufacturerId=330 x_zwave_values.Manufacturer_Specific_productId=3 x_zwave_values.Manufacturer_Specific_productType=4 x_zwave_values.Notification_Access_Control_Door_state=23 x_zwave_values.Notification_Access_Control_Door_state_simple=23 x_zwave_values.Notification_Home_Security_Cover_status=3 x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0 x_zwave_values.Notification_UNKNOWN_0x46=23 x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=["10.1"] x_zwave_values.Version_hardwareVersion=2 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=14400 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="23305:1:22057:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1699563172708 zwave_device.manufacturer_info=[330,4,3] zwave_device.max_data_rate=null zwave_device.node_id=24 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,"10.1"] zwave_device.wakeup_interval=14400
Multi-System Reactor
Inovelli LZW31 / Aeotec ZWA037 switches always displaying power_switch.state = false in zwaveJSController
SnowmanS

I have just noticed that two of my z-wave switches, Inovelli LZW31 and Aeotec ZWA037, although responding correctly to commands such as (turning on the switch, changing LED color, etc.), are not displaying the right power_switch.state when turned ON. All other attributes are showing proper values.

Example when I turn on either switches,
In Home Assistant (hass), the power_switch.state = true while in ZWaveJSController (zwavejs), the power_switch.state = false.

Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3

Here's what the log shows.

[latest-23302]2023-11-01T21:14:00.303Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.308Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.311Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.312Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.312Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.313Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.315Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:03.258Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:03.259Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is true (previously false) [latest-23302]2023-11-01T21:14:03.260Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; rule state transition from RESET to SET! [latest-23302]2023-11-01T21:14:03.271Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:03.273Z <Engine:INFO> Enqueueing "Toggle office light LED color state between green/blue Copy<SET>" (rule-lof5hpwe:S) [latest-23302]2023-11-01T21:14:03.285Z <Engine:NOTICE> Starting reaction Toggle office light LED color state between green/blue Copy<SET> (rule-lof5hpwe:S) [latest-23302]2023-11-01T21:14:03.287Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Light#zwavejs>138-0 with [Object]{ "parameter": "84", "size": 1, "value": 3, "bitmask": 0 } [latest-23302]2023-11-01T21:14:03.345Z <Engine:INFO> Resuming reaction Toggle office light LED color state between green/blue Copy<SET> (rule-lof5hpwe:S) from step 2 [latest-23302]2023-11-01T21:14:03.346Z <Engine:INFO> Toggle office light LED color state between green/blue Copy<SET> all actions completed. [latest-23302]2023-11-01T21:14:05.191Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state [latest-23302]2023-11-01T21:14:05.205Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:05.205Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is true (previously true) [latest-23302]2023-11-01T21:14:05.206Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; trigger state unchanged (true); rule state remains SET [latest-23302]2023-11-01T21:14:05.206Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:10.503Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state [latest-23302]2023-11-01T21:14:10.518Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:10.519Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is false (previously true) [latest-23302]2023-11-01T21:14:10.520Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; rule state transition from SET to RESET! [latest-23302]2023-11-01T21:14:10.529Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:10.530Z <Engine:INFO> Enqueueing "Toggle office light LED color state between green/blue Copy<RESET>" (rule-lof5hpwe:R) [latest-23302]2023-11-01T21:14:10.542Z <Engine:NOTICE> Starting reaction Toggle office light LED color state between green/blue Copy<RESET> (rule-lof5hpwe:R) [latest-23302]2023-11-01T21:14:10.543Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Light#zwavejs>138-0 with [Object]{ "parameter": "84", "size": 1, "value": 2, "bitmask": 0 } [latest-23302]2023-11-01T21:14:10.596Z <Engine:INFO> Resuming reaction Toggle office light LED color state between green/blue Copy<RESET> (rule-lof5hpwe:R) from step 2 [latest-23302]2023-11-01T21:14:10.597Z <Engine:INFO> Toggle office light LED color state between green/blue Copy<RESET> all actions completed. [latest-23302]2023-11-01T21:14:12.441Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state

PS I am trying to attach an image but getting "Something went wrong while parsing server response". Also, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version.

Hopefully I have provided the necessary information.

Thanks in advance.

Multi-System Reactor
Rule's sustain / delay reset etc. value parameterization thru entities
M

Some background
I have two simple rules that will toggle my carport's down lights depending on outdoor brightness when I open the motorized sliding gate. I.e. if the brightness is 1500 lux or less and the gate is opened, the down lights will be switched on, and when the gate is closed, the lights will switch off after 3 minutes. Pretty simple 'coming home' functionality so to speak.

Here's the switch off rule showing the 'hard coded' thresholds

Screenshot from 2023-10-31 18-44-46.png

The problem
I would like to parameterize the lux and switch off delay using entities. I bet the lux threshold can be done with local expressions the same way I do my WC background music scheduling:

weekdays_enabled = (time() >= time(getEntity( "mqtt>wc-music-weekdays-enable" ).attributes.string_sensor.value )) && (time() <= time(getEntity( "mqtt>wc-music-weekdays-disable" ).attributes.string_sensor.value ))

But the since I'm using the Condition must be sustained for functionality for the switch off rule, I have no idea how to parameterize that with some entity value.

So my question is that is it even possible to do this using entities or could there some other way to accomplish the same functionality? In this example it's the sustain -value but I might need same kind of parameterization for the delay reset also.

I have to go with entities, since my own HA system will provide the threshold values for the MSR through the MQTTController.

Help would be appreciated @toggledbits
br,
mgvra

MSR latest-23302-b7def56a and MQTTController [0.1.23254]

Multi-System Reactor
Have reactor shut off a light with no motion unless I turned it on manually
S

So I have a strange one here and I don't know if there is a way to do this or not. I have blue iris triggering a vera virtual switch when AI detects motion on my front porch. Reactor then triggers the light, this works perfect. I want to shut the light off when there is no motion, this also works perfect. What I am having am issue with is when someone turns on the light manually I don't want it to turn off after motion is detected. Example: we are expecting a pizza so we turn on the porch light. 5 min later amazon delivers a package, trips motion. 10 min later Reactor is going to turn off the light. If I manually turn on the light before motion is detected I do not want reactor to turn it off. For the life of me I cannot figure the logic out. Does anyone have any ideas?

Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT

Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Variable Value select array part
wmarcolinW

Hi @toggledbits

Is there any way that in the trigger the Varable Value could select the desired part of the array?

For example, I could have a global variable VarTEST$[Part1, Part2, Part3] like this: ${{ [TestText, 5, 3] }}. Use the Variable Value to validate a VarTEST[Part2] == 5 trigger.

What am I doing today? I've defined 3 global variables:

3ae76d20-ffce-4f66-9002-1b4d6cc7c3c3-image.png

And I validate each variable.

3bcc1d62-2ce1-41ca-9f00-f98578c0d597-image.png

In short, I would like to have a global variable of the array type, and be able to select which element of the array I would use for validation in a trigger.

Thanks

Multi-System Reactor
Need Some Help Using browser_mod (HA integration)
PablaP

Hello all I am trying to run the service call browser_mod.popup from MSR to HA. If I enter the service data in YAML like this:

dismissable: true autoclose: false timeout: 120000 content: type: custom:mushroom-alarm-control-panel-card entity: alarm_control_panel.home_partition states: - armed_home - armed_away layout: vertical show_keypad: true target: device_id: e684ad00b76e330e57a8c915dc367bc4

For some reason the target portion of the data isn't sent and therefor the popup shows up on all my browser mod devices not the only one I had specified in the device_id. Here is a snippet of the reactor log, no errors that I see just looks like the target info isn't being passed on.

[latest-23242]2023-10-12T23:51:50.795Z <Engine:INFO> Enqueueing "Main Floor Tablet Alarm Arming Popup<SET>" (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:51:50.800Z <Engine:NOTICE> Starting reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:51:50.813Z <HassController:INFO> HassController#hass action x_hass_system.call_service([Object]{ "service": "browser_mod.popup", "data": "data:\n dismissable: true\n autoclose: false\n timeout: 120000\n content:\n type: custom:mushroom-alarm-control-panel-card\n entity: alarm_control_panel.home_partition\n states:\n - armed_home\n - armed_away\n layout: vertical\n show_keypad: true\ntarget:\n device_id: e684ad00b76e330e57a8c915dc367bc4" }) on System#hass>system succeeded [latest-23242]2023-10-12T23:51:50.816Z <Engine:INFO> Resuming reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) from step 1 [latest-23242]2023-10-12T23:51:50.817Z <Engine:INFO> Main Floor Tablet Alarm Arming Popup<SET> all actions completed.

So I used an online YAML to JSON converter since I am not the good with JSON and it converted the YAML to this:

{ "data": { "dismissable": true, "autoclose": false, "timeout": 120000, "content": { "type": "custom:mushroom-alarm-control-panel-card", "entity": "alarm_control_panel.bar_partition", "states": [ "armed_home", "armed_away" ], "layout": "vertical", "show_keypad": true } }, "target": { "device_id": "34ae76561192c4bb0b64fb07ad0f01c1" } }

When I use this in my reaction the popup doesn't show up properly. Something pops up but it's just a grey bar. Interestingly the JSON version actually does target only the device_id I had specified. Here is the reactor log output:

[latest-23242]2023-10-12T23:52:39.875Z <Engine:INFO> Enqueueing "Main Floor Tablet Alarm Arming Popup<SET>" (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:52:39.880Z <Engine:NOTICE> Starting reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:52:40.291Z <HassController:INFO> HassController#hass action x_hass_system.call_service([Object]{ "service": "browser_mod.popup", "data": "{\n \"data\": {\n \"dismissable\": true,\n \"autoclose\": false,\n \"timeout\": 120000,\n \"content\": {\n \"type\": \"custom:mushroom-alarm-control-panel-card\",\n \"entity\": \"alarm_control_panel.home_partition\",\n \"states\": [\n \"armed_home\",\n \"armed_away\"\n ],\n \"layout\": \"vertical\",\n \"show_keypad\": true\n }\n },\n \"target\": {\n \"device_id\": \"e684ad00b76e330e57a8c915dc367bc4\"\n }\n}" }) on System#hass>system succeeded [latest-23242]2023-10-12T23:52:40.293Z <Engine:INFO> Resuming reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) from step 1 [latest-23242]2023-10-12T23:52:40.294Z <Engine:INFO> Main Floor Tablet Alarm Arming Popup<SET> all actions completed.

My limited skill with JSON has kind of backed me into a corner here, so if anyone could help me format it correctly that would be great!

MSR latest 23242
HA 2023.10.1

Multi-System Reactor
reactor-lgtv: LG TV Controller for Reactor
therealdbT

Here's my second attempt at a Reactor Controller, this time to integrate LG TVs:

GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos) GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos)

Reactor controller for LG TV (webos). Contribute to dbochicchio/reactor-lgtv development by creating an account on GitHub.

Standard capabilities are provided and TV volume, mute and switch status are controllable.
There's also an action to send toast notifications on your TV.

webos 5+ is required.

Multi-System Reactor
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
G

I installed a new iblind this evening and it is appearing in ZWaveJS. It is operational thru Home Assistant just fine. It is operational thru the HA ZwaveJS plugin just fine.

Where it is non-responsive is in MSR for some reason. The entities are there. Adding the node to a Reaction and then attempting to run said Reaction nets me this:

[latest-23242]2023-09-08T05:33:08.454Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value motion_sensor.state=false [latest-23242]2023-09-08T05:33:08.455Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Binary Sensor#zwavejs>11-0.x_zwave_values.Binary_Sensor_Motion to false [latest-23242]2023-09-08T05:33:08.692Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Binary Sensor#zwavejs>11-0 [latest-23242]2023-09-08T05:40:23.960Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>20-0 with [Object]{ } [latest-23242]2023-09-08T05:40:23.962Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default [latest-23242]2023-09-08T05:40:25.062Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.refresh on Cover#zwavejs>20-0 with [Object]{ } **[latest-23242]2023-09-08T05:40:25.063Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default** [latest-23242]2023-09-08T05:40:25.065Z <ZWaveJSController:5:ZWaveJSController.js:294> ZWaveJSController#zwavejs sending #1694151625064<9/8/2023, 1:40:25 AM>: [Object]{ "command": "node.refresh_values", "nodeId": 20, "messageId": 1694151625064 } [latest-23242]2023-09-08T05:40:26.307Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.317Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.318Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:level:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "level", "endpoint": 0, "newValue": 100, "prevValue": 100, "propertyName": "level" } } [latest-23242]2023-09-08T05:40:26.319Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:level:"=100: [Array][ "battery_power.level", "battery_power.since" ] [latest-23242]2023-09-08T05:40:26.320Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.level with [Object]{ "entity": "20-0", "impl": { "expr": "float( value ) / 100", "valueId": "128:level:" } } [latest-23242]2023-09-08T05:40:26.321Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.level [latest-23242]2023-09-08T05:40:26.322Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.level=1 [latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.since with [Object]{ "entity": "20-0", "impl": { "expr": "time()", "valueId": "128:level:" } } [latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.since [latest-23242]2023-09-08T05:40:26.324Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.since=1694151626324<9/8/2023, 1:40:26 AM> [latest-23242]2023-09-08T05:40:26.325Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_level to 100 [latest-23242]2023-09-08T05:40:26.333Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.334Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:isLow:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "isLow", "endpoint": 0, "newValue": false, "prevValue": false, "propertyName": "isLow" } } [latest-23242]2023-09-08T05:40:26.336Z <ZWaveJSController:5:ZWaveJSController.js:324> ZWaveJSController#zwavejs request 1694151625064<9/8/2023, 1:40:25 AM> (node.refresh_values) success notification [latest-23242]2023-09-08T05:40:26.337Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:isLow:"=false: [Array][ ] [latest-23242]2023-09-08T05:40:26.338Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_isLow to false [latest-23242]2023-09-08T05:40:26.558Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0

Please note the highlighted logpart - no other iblind has this. In addition, in MSR>Entities several show as null rather than having a value as the others do.

69631fbc-db4e-4e8d-aa98-10565811cd93-image.png

I tried deleting all Entities associated with this device from MSR and then refreshing ZWaveJS in Home Assistant and restarting MSR - the Entities return but in the same state/s.

Admittedly, it's been a very long three weeks at work - I could have missed something obvious during setup but I sure can't figure what it is.

Multi-System Reactor
[Solved] OWM error
wmarcolinW

Hi @toggledbits

I'm trying to use OWM, apparently, I receive the correct information, but after a while, the MSR disconnects.

My configuration is as follows.

- id: weather enabled: true implementation: OWMWeatherController name: OWM Weather config: # Place your OWM API key here (remember to enable the controller after adding your appid) appid: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" # How often weather is allowed to be refreshed. This helps limit OWN API use, # to keep you in their good graces (and on their free tier). This value is # in minutes. interval: 30 locations: - id: home name: Home Weather # Set the location by specifying ONE OF: latitude+longitude, OWN city # ID, or location (as postal,country). If none is set, the system # location will be used. latitude: 8.9936 longitude: -79.5197 city_id: 3703443 #location: "30269,us" # Enable "save_full_response" to save the full response (you may have # need to use parts of the response that are not part of the wx # capability in your dashboard widgets). #save_full_response: false

When I request a systemctl status reactor I get this message:

root@main:/home/wilson/reactor/logs# systemctl status reactor ● reactor.service - Multi System Reactor Loaded: loaded (/etc/systemd/system/reactor.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-09-08 21:03:13 EST; 5s ago Main PID: 194711 (node) Tasks: 11 (limit: 9390) Memory: 82.5M CPU: 2.508s CGroup: /system.slice/reactor.service └─194711 /usr/bin/node app -p Sep 08 21:03:13 main node[194711]: Error: Incompatible serialization data; can't unserialize Sep 08 21:03:13 main node[194711]: at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) Sep 08 21:03:13 main node[194711]: at /home/wilson/reactor/server/lib/Controller.js:458:70 Sep 08 21:03:13 main node[194711]: at Array.forEach (<anonymous>) Sep 08 21:03:13 main node[194711]: at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) Sep 08 21:03:13 main node[194711]: at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) Sep 08 21:03:13 main node[194711]: at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) Sep 08 21:03:13 main node[194711]: at /home/wilson/reactor/server/lib/Controller.js:93:37 Sep 08 21:03:13 main node[194711]: [latest-23242]2023-09-09T02:03:13.855Z <NUTController:null> Module NUTController v22305 Sep 08 21:03:13 main node[194711]: [latest-23242]2023-09-09T02:03:13.859Z <SystemController:null> Module SystemController v23214 root@main:/home/wilson/reactor/logs# root@main:/home/wilson/reactor# systemctl status reactor ● reactor.service - Multi System Reactor Loaded: loaded (/etc/systemd/system/reactor.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-09-08 20:48:36 EST; 2min 58s ago Main PID: 194353 (node) Tasks: 11 (limit: 9390) Memory: 66.0M CPU: 9.493s CGroup: /system.slice/reactor.service └─194353 /usr/bin/node app -p Sep 08 20:48:37 main node[194353]: at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) Sep 08 20:48:37 main node[194353]: at /home/wilson/reactor/server/lib/Controller.js:458:70 Sep 08 20:48:37 main node[194353]: at Array.forEach (<anonymous>) Sep 08 20:48:37 main node[194353]: at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) Sep 08 20:48:37 main node[194353]: at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) Sep 08 20:48:37 main node[194353]: at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) Sep 08 20:48:37 main node[194353]: at /home/wilson/reactor/server/lib/Controller.js:93:37 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.017Z <NUTController:null> Module NUTController v22305 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.024Z <SystemController:null> Module SystemController v23214 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.475Z <Timer:null> Timer#rule-l7ujwva5 just a note: I'm setting a delay of > lines 1-20/20 (END)

I can see this information in the log, but I don't understand what I should do to fix it.

[latest-23242]2023-09-09T02:03:13.838Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23242]2023-09-09T02:03:13.845Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-23242]2023-09-09T02:03:13.847Z <OWMWeatherController:null> Module OWMWeatherController v22294 [latest-23242]2023-09-09T02:03:13.850Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity controller_all: [Error] Inco> [latest-23242]2023-09-09T02:03:13.850Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Group.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.851Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity default: [Error] Incompatibl> [latest-23242]2023-09-09T02:03:13.851Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.852Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity system: [Error] Incompatible> [latest-23242]2023-09-09T02:03:13.852Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.853Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController) [latest-23242]2023-09-09T02:03:13.855Z <NUTController:null> Module NUTController v22305 [latest-23242]2023-09-09T02:03:13.855Z <Controller:INFO> Loaded NUTController version "0.1.22305"; Patrick Rigney/Kedron Holdings LLC <patrick@> [latest-23242]2023-09-09T02:03:13.857Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [

And finally, I have a second house, with the same OWM configuration I made today, and it doesn't show any errors.

Please, your traditional help.

Thanks.

Multi-System Reactor
Host time is wrong
wmarcolinW

@toggledbits

After a prolonged power cut, the UPS was unable to cope with the weather and shut down the entire system.

When I returned, I had the problem that the host time displayed in the browser and automatically used in the rules was not correct.

I searched for a topic here on this forum that talked about it, but it referred to a container installation. There was a recommendation to go into the storage/states directory and delete the files and restart MSR, I did it and it didn't solve the problem.

There was also a recommendation to go directly to the browser to check the time, and I did so and I see that the time is correct.

8ad429c8-ea5f-45b4-8670-7d0353a50a0e-image.png

As you can see on the screen above:

MSR browser shows the correct browser time 21:23, but host time 13:02; In the browser below the direct query and the host time is correct 9:22:54 PM; Setting the VM date command on the third screen, the time is 9:23:00 PM.

I've opened the entire reactor.log file and searched for any errors, and there aren't any.

^L [latest-23242]2023-09-15T02:11:12.928Z <app:null> Reactor build latest-23242-5ee8e1d4 starting on v18.12.0 [latest-23242]2023-09-15T02:11:12.929Z <app:null> Process ID 1807 user/group 1000/1000; bare-metal; platform linux/x64 #179-Ubuntu SMP Mo> [latest-23242]2023-09-15T02:11:12.929Z <app:null> Basedir /home/leonardo/reactor; data in /home/leonardo/reactor/storage [latest-23242]2023-09-15T02:11:12.929Z <app:null> NODE_PATH=/home/leonardo/reactor [latest-23242]2023-09-15T02:11:12.933Z <app:INFO> Configured locale (undefined); selected locale(s) en_US.UTF-8 [latest-23242]2023-09-15T02:11:12.955Z <app:INFO> Loaded locale en-US for en-US [latest-23242]2023-09-15T02:11:12.958Z <Structure:null> Module Structure v23172 [latest-23242]2023-09-15T02:11:12.959Z <Capabilities:null> Module Capabilities v22356 [latest-23242]2023-09-15T02:11:12.969Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 23914 revisi> [latest-23242]2023-09-15T02:11:12.978Z <Plugin:null> Module Plugin v22300 [latest-23242]2023-09-15T02:11:12.981Z <TimerBroker:null> Module TimerBroker v22283 [latest-23242]2023-09-15T02:11:12.983Z <Entity:null> Module Entity v22353 [latest-23242]2023-09-15T02:11:12.986Z <Controller:null> Module Controller v23069 [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Ruleset v22293 [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Rulesets v22146 [latest-23242]2023-09-15T02:11:12.996Z <GlobalExpression:null> Module GlobalExpression v23211 [latest-23242]2023-09-15T02:11:13.003Z <Predicate:null> Module Predicate v23093 [latest-23242]2023-09-15T02:11:13.005Z <AlertManager:null> Module AlertManager v22283 [latest-23242]2023-09-15T02:11:13.007Z <Rule:null> Module Rule v23107 [latest-23242]2023-09-15T02:11:13.009Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23242]2023-09-15T02:11:13.010Z <Engine:null> Module Engine v23231 [latest-23242]2023-09-15T02:11:13.012Z <httpapi:null> Module httpapi v23058 [latest-23242]2023-09-15T02:11:13.019Z <wsapi:null> Module wsapi v23172 [latest-23242]2023-09-15T02:11:13.019Z <app:NOTICE> Starting Structure...

As you can see, the time in the log is 02:11, which is correct, because I'm in time zone -5, which means it's 09:11PM for me.

I've restarted the VM, the computer hosting the VM, and the MSR a few times and the same difference remains. What do you recommend for the next step in understanding and solving the problem?

Thanks.

Multi-System Reactor
Migration question
T

Good afternoon,
I'm running my MSR instance on an old NAS server running Fedora 37 Server. This is an older Core i5-4690K server that has served me well overall, but it's showing it's age, and will often reboot into maint mode if it applies updates overnight. I've been trying to troubleshoot, but it's also in my office (makes my office hot), and I'm looking at getting either a QNAP or Syslogy rack mount NAS to replace it.

What I'm wondering is what the process would be to migrate my current MSR config and move it to a different platform. I have quite a large ruleset that I don't want to have to recreate. I know I can run it in a container on either platform, but I'm not sure how I would migrate all my rules over. Is there one config file that has all of the rules, or could I simply copy my /reactor directory over to a enw platform?

I am also considering moving the MSR instance to a stand alone RPI 4 with a SSD. This way, while I'm migrating all of my files off of my NAS, I'm not loosing Reactor's functionality until I have whichever rack mount NAS I go with up and running, with all of the data migrated.

Thoughts?

Multi-System Reactor

Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

Latest version is installed, we are still working on some visual changes.

Need Some Help Using browser_mod (HA integration)

Scheduled Pinned Locked Moved Multi-System Reactor
26 Posts 2 Posters 589 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #17

    Can you confirm that after restart of Reactor, you find a log message containing the text ZIP data update found, and another shortly after ZIP update file device configuration version 23240.2 overrides package version xxx.yyy?

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

    1 Reply Last reply
    0
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #18

    Here are the startup logs, looks like there is a error saying the ZIP file has no hass_capabilities.json. Also ignore the dynamic group errors its still a work in progress lol .

    

[latest-23242]2023-10-18T18:58:22.258Z <app:NOTICE> Closing Structure...
[latest-23242]2023-10-18T18:58:22.258Z <Structure:NOTICE> Structure#1 Stopping controllers...
[latest-23242]2023-10-18T18:58:22.259Z <Structure:INFO> Structure#1 stopping HassController#hass
[latest-23242]2023-10-18T18:58:22.259Z <HassController:NOTICE> HassController#hass stopping
[latest-23242]2023-10-18T18:58:22.263Z <wsapi:WARN> client close from unknown connection? "192.168.8.185#3"
[latest-23242]2023-10-18T18:58:22.271Z <HassController:NOTICE> HassController#hass websocket closing, 1000 
[latest-23242]2023-10-18T18:58:22.272Z <Controller:NOTICE> HassController#hass stopping
[latest-23242]2023-10-18T18:58:22.285Z <Controller:ERR> Controller HassController#hass is off-line!
[latest-23242]2023-10-18T18:58:25.508Z <Structure:INFO> Structure#1 stopping ZWaveJSController#zwavejs
[latest-23242]2023-10-18T18:58:25.508Z <Controller:NOTICE> ZWaveJSController#zwavejs stopping
[latest-23242]2023-10-18T18:58:25.514Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group open_zones: [TypeError] Cannot read properties of undefined (reading 'binary_sensor_babay_papa_windows') [-]
[latest-23242]2023-10-18T18:58:25.515Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'binary_sensor_babay_papa_windows') [-]
TypeError: Cannot read properties of undefined (reading 'binary_sensor_babay_papa_windows')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.517Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group phones: [TypeError] Cannot read properties of undefined (reading 'sensor_bar_tablet_battery_level') [-]
[latest-23242]2023-10-18T18:58:25.518Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'sensor_bar_tablet_battery_level') [-]
TypeError: Cannot read properties of undefined (reading 'sensor_bar_tablet_battery_level')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.519Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group low_battery_35: [TypeError] Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level') [-]
[latest-23242]2023-10-18T18:58:25.520Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level') [-]
TypeError: Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.521Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group low_battery_10: [TypeError] Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level') [-]
[latest-23242]2023-10-18T18:58:25.522Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level') [-]
TypeError: Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.524Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group dead_battery: [TypeError] Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level') [-]
[latest-23242]2023-10-18T18:58:25.524Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level') [-]
TypeError: Cannot read properties of undefined (reading 'sensor_backyard_gate_battery_level')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.527Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group offline_devices: [TypeError] Cannot read properties of undefined (reading 'controller_all') [-]
[latest-23242]2023-10-18T18:58:25.527Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'controller_all') [-]
TypeError: Cannot read properties of undefined (reading 'controller_all')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.529Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group add_on_update_available: [TypeError] Cannot read properties of undefined (reading 'update_address_sign_light_firmware') [-]
[latest-23242]2023-10-18T18:58:25.529Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'update_address_sign_light_firmware') [-]
TypeError: Cannot read properties of undefined (reading 'update_address_sign_light_firmware')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.603Z <DynamicGroupController:ERR> DynamicGroupController#groups error updating dynamic group jammed_door_locks: [TypeError] Cannot read properties of undefined (reading 'binary_sensor_touchscreen_deadbolt_access_control_lock_jammed') [-]
[latest-23242]2023-10-18T18:58:25.603Z <DynamicGroupController:CRIT> TypeError: Cannot read properties of undefined (reading 'binary_sensor_touchscreen_deadbolt_access_control_lock_jammed') [-]
TypeError: Cannot read properties of undefined (reading 'binary_sensor_touchscreen_deadbolt_access_control_lock_jammed')
    at HassController.getNamedEntity (/home/arman/Documents/reactor/server/lib/Controller.js:380:35)
    at Structure.findEntity (/home/arman/Documents/reactor/server/lib/Structure.js:460:151)
    at DynamicGroupController._update_group (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:318:60)
    at /home/arman/Documents/reactor/server/lib/DynamicGroupController.js:375:67
    at Array.forEach (<anonymous>)
    at DynamicGroupController._update (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:367:274)
    at DynamicGroupController.notify (/home/arman/Documents/reactor/server/lib/DynamicGroupController.js:255:91)
    at /home/arman/Documents/reactor/server/lib/MessageBus.js:106:223
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (/home/arman/Documents/reactor/server/lib/MessageBus.js:103:47)
[latest-23242]2023-10-18T18:58:25.622Z <Controller:ERR> Controller ZWaveJSController#zwavejs is off-line!
[latest-23242]2023-10-18T18:58:26.470Z <Structure:INFO> Structure#1 stopping DynamicGroupController#groups
[latest-23242]2023-10-18T18:58:26.471Z <DynamicGroupController:null> DynamicGroupController#groups stopping
[latest-23242]2023-10-18T18:58:26.481Z <Controller:NOTICE> DynamicGroupController#groups stopping
[latest-23242]2023-10-18T18:58:26.488Z <Controller:ERR> Controller DynamicGroupController#groups is off-line!
[latest-23242]2023-10-18T18:58:26.503Z <Structure:INFO> Structure#1 stopping SystemController#reactor_system
[latest-23242]2023-10-18T18:58:26.504Z <Controller:NOTICE> SystemController#reactor_system stopping
[latest-23242]2023-10-18T18:58:26.512Z <Controller:ERR> Controller SystemController#reactor_system is off-line!
[latest-23242]2023-10-18T18:58:26.520Z <Structure:INFO> Structure#1 Final data sync...
[latest-23242]2023-10-18T18:58:26.521Z <default:INFO> Closing container Container#rulesets
[latest-23242]2023-10-18T18:58:26.521Z <default:INFO> Closing container Container#rules
[latest-23242]2023-10-18T18:58:26.521Z <default:INFO> Closing container Container#reactions
[latest-23242]2023-10-18T18:58:26.521Z <default:INFO> Closing container Container#states
[latest-23242]2023-10-18T18:58:26.583Z <default:INFO> Closing container Container#default
[latest-23242]2023-10-18T18:58:27.013Z <default:INFO> Closing container Container#expressions
[latest-23242]2023-10-18T18:58:27.019Z <Structure:NOTICE> Structure Structure#1 stopped
[latest-23242]2023-10-18T18:58:27.019Z <app:NOTICE> Stopping timers...
[latest-23242]2023-10-18T18:58:27.025Z <app:null> Shutdown complete, process ID 19741

[latest-23242]2023-10-18T18:58:35.498Z <app:null> Reactor build latest-23242-5ee8e1d4 starting on v16.15.1
[latest-23242]2023-10-18T18:58:35.501Z <app:null> Process ID 20525 user/group 1000/1000; bare-metal; platform linux/arm #1642 SMP Mon Apr  3 17:20:52 BST 2023; locale en_CA.UTF-8
[latest-23242]2023-10-18T18:58:35.502Z <app:null> Basedir /home/arman/Documents/reactor; data in /home/arman/Documents/reactor/storage
[latest-23242]2023-10-18T18:58:35.503Z <app:null> NODE_PATH=/home/arman/Documents/reactor
[latest-23242]2023-10-18T18:58:35.514Z <app:INFO> Configured locale (undefined); selected locale(s) en_CA.UTF-8
[latest-23242]2023-10-18T18:58:35.712Z <app:INFO> Loaded locale en-US for en-CA
[latest-23242]2023-10-18T18:58:35.729Z <Structure:null> Module Structure v23172
[latest-23242]2023-10-18T18:58:35.740Z <Capabilities:null> Module Capabilities v22356
[latest-23242]2023-10-18T18:58:35.840Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 23914 revision 1
[latest-23242]2023-10-18T18:58:35.901Z <Plugin:null> Module Plugin v22300
[latest-23242]2023-10-18T18:58:35.926Z <TimerBroker:null> Module TimerBroker v22283
[latest-23242]2023-10-18T18:58:35.937Z <Entity:null> Module Entity v22353
[latest-23242]2023-10-18T18:58:35.950Z <Controller:null> Module Controller v23069
[latest-23242]2023-10-18T18:58:36.003Z <default:null> Module Ruleset v22293
[latest-23242]2023-10-18T18:58:36.005Z <default:null> Module Rulesets v22146
[latest-23242]2023-10-18T18:58:36.054Z <GlobalExpression:null> Module GlobalExpression v23211
[latest-23242]2023-10-18T18:58:36.112Z <Predicate:null> Module Predicate v23093
[latest-23242]2023-10-18T18:58:36.126Z <AlertManager:null> Module AlertManager v22283
[latest-23242]2023-10-18T18:58:36.137Z <Rule:null> Module Rule v23107
[latest-23242]2023-10-18T18:58:36.150Z <GlobalReaction:null> Module GlobalReaction v22324
[latest-23242]2023-10-18T18:58:36.156Z <Engine:null> Module Engine v23231
[latest-23242]2023-10-18T18:58:36.174Z <httpapi:null> Module httpapi v23058
[latest-23242]2023-10-18T18:58:36.229Z <wsapi:null> Module wsapi v23172
[latest-23242]2023-10-18T18:58:36.232Z <app:NOTICE> Starting Structure...
[latest-23242]2023-10-18T18:58:36.251Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping
[latest-23242]2023-10-18T18:58:36.258Z <Structure:INFO> Structure#1 loading controller interface hass (HassController)
[latest-23242]2023-10-18T18:58:36.347Z <HassController:null> Module HassController v23240
[latest-23242]2023-10-18T18:58:36.380Z <Controller:WARN> HassController#hass failed (1) to restore entity binary_sensor_front_water_fountain_sensor_water_alarm_water_leak_detected: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23242]2023-10-18T18:58:36.381Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/home/arman/Documents/reactor/server/lib/Entity.js:624:19)
    at /home/arman/Documents/reactor/server/lib/Controller.js:458:70
    at Array.forEach (<anonymous>)
    at HassController._restoreEntities (/home/arman/Documents/reactor/server/lib/Controller.js:446:36)
    at new Controller (/home/arman/Documents/reactor/server/lib/Controller.js:37:45)
    at new HassController (/home/arman/Documents/reactor/server/lib/HassController.js:36:9)
    at /home/arman/Documents/reactor/server/lib/Controller.js:93:37
[latest-23242]2023-10-18T18:58:36.384Z <Controller:WARN> HassController#hass failed (1) to restore entity binary_sensor_z_wave_wireless_flood_freeze_sensor_sensor_state_water: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23242]2023-10-18T18:58:36.385Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/home/arman/Documents/reactor/server/lib/Entity.js:624:19)
    at /home/arman/Documents/reactor/server/lib/Controller.js:458:70
    at Array.forEach (<anonymous>)
    at HassController._restoreEntities (/home/arman/Documents/reactor/server/lib/Controller.js:446:36)
    at new Controller (/home/arman/Documents/reactor/server/lib/Controller.js:37:45)
    at new HassController (/home/arman/Documents/reactor/server/lib/HassController.js:36:9)
    at /home/arman/Documents/reactor/server/lib/Controller.js:93:37
[latest-23242]2023-10-18T18:58:38.603Z <Structure:INFO> Structure#1 loading controller interface zwavejs (ZWaveJSController)
[latest-23242]2023-10-18T18:58:38.648Z <ZWaveJSController:null> Module ZWaveJSController v23194
[latest-23242]2023-10-18T18:58:38.651Z <Controller:INFO> Loaded ZWaveJSController version "0.1.23194"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/ZWaveJSController/
[latest-23242]2023-10-18T18:58:38.970Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs added file logger to zwavejs.log
[latest-23242]2023-10-18T18:58:38.971Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController)
[latest-23242]2023-10-18T18:58:38.993Z <DynamicGroupController:null> Module DynamicGroupController v22313
[latest-23242]2023-10-18T18:58:39.021Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController)
[latest-23242]2023-10-18T18:58:39.035Z <SystemController:null> Module SystemController v23214
[latest-23242]2023-10-18T18:58:39.048Z <Structure:INFO> Starting controller HassController#hass
[latest-23242]2023-10-18T18:58:39.049Z <HassController:NOTICE> HassController#hass starting...
[latest-23242]2023-10-18T18:58:39.063Z <Controller:INFO> HassController#hass ZIP data update found (/home/arman/Documents/reactor/config/hass_data.zip)
[latest-23242]2023-10-18T18:58:39.066Z <Structure:INFO> Starting controller ZWaveJSController#zwavejs
[latest-23242]2023-10-18T18:58:39.069Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_device_cfg, which is not consistent with the recommended naming
[latest-23242]2023-10-18T18:58:39.070Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_mfg_spec, which is not consistent with the recommended naming
[latest-23242]2023-10-18T18:58:39.070Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_device_ver, which is not consistent with the recommended naming
[latest-23242]2023-10-18T18:58:39.070Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_values, which is not consistent with the recommended naming
[latest-23242]2023-10-18T18:58:39.071Z <Controller:INFO> ZWaveJSController#zwavejs loaded zwavejs capabilities ver 23194 rev 1 format 1 
[latest-23242]2023-10-18T18:58:39.123Z <Controller:INFO> ZWaveJSController#zwavejs loaded implementation data ver 23194 rev 1 format 1 
[latest-23242]2023-10-18T18:58:39.123Z <Structure:INFO> Starting controller DynamicGroupController#groups
[latest-23242]2023-10-18T18:58:39.138Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online.
[latest-23242]2023-10-18T18:58:39.139Z <Structure:INFO> Starting controller SystemController#reactor_system
[latest-23242]2023-10-18T18:58:39.146Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
[latest-23242]2023-10-18T18:58:39.344Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs connecting to ws://192.168.8.85:3000
[latest-23242]2023-10-18T18:58:39.413Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs greeting from server: [Object]{ "type": "version", "driverVersion": "12.2.0", "serverVersion": "1.32.1", "homeId": 3775115912, "minSchemaVersion": 0, "maxSchemaVersion": 32 }
[latest-23242]2023-10-18T18:58:39.416Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs connected
[latest-23242]2023-10-18T18:58:39.417Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs sending connection initialization
[latest-23242]2023-10-18T18:58:39.431Z <Controller:WARN> /home/arman/Documents/reactor/config/hass_data.zip: no hass_capabilities.json: hass
[latest-23242]2023-10-18T18:58:39.432Z <Controller:INFO> HassController#hass loaded hass capabilities ver 23109 rev 1 format 1 
[latest-23242]2023-10-18T18:58:39.468Z <Controller:WARN> /home/arman/Documents/reactor/config/hass_data.zip: no hass_devices.json: [Error] Entry not found [-]
[latest-23242]2023-10-18T18:58:39.468Z <Controller:INFO> HassController#hass loaded implementation data ver 23240 rev 1 format 1 
[latest-23242]2023-10-18T18:58:39.473Z <HassController:INFO> HassController#hass device mapping data loaded; checking...
[latest-23242]2023-10-18T18:58:39.475Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability power_switch
[latest-23242]2023-10-18T18:58:39.477Z <HassController:5:HassController.js:258> HassController#hass capability power_switch attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.477Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability toggle
[latest-23242]2023-10-18T18:58:39.479Z <HassController:5:HassController.js:258> HassController#hass capability toggle attributes [Array][  ]
[latest-23242]2023-10-18T18:58:39.480Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability dimming
[latest-23242]2023-10-18T18:58:39.480Z <HassController:5:HassController.js:258> HassController#hass capability dimming attributes [Array][ "level", "step" ]
[latest-23242]2023-10-18T18:58:39.481Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability rgb_color
[latest-23242]2023-10-18T18:58:39.481Z <HassController:5:HassController.js:258> HassController#hass capability rgb_color attributes [Array][ "red", "green", "blue" ]
[latest-23242]2023-10-18T18:58:39.482Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability hs_color
[latest-23242]2023-10-18T18:58:39.482Z <HassController:5:HassController.js:258> HassController#hass capability hs_color attributes [Array][ "hue", "saturation" ]
[latest-23242]2023-10-18T18:58:39.483Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability xy_color
[latest-23242]2023-10-18T18:58:39.484Z <HassController:5:HassController.js:258> HassController#hass capability xy_color attributes [Array][ "x", "y" ]
[latest-23242]2023-10-18T18:58:39.484Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability color_temperature
[latest-23242]2023-10-18T18:58:39.485Z <HassController:5:HassController.js:258> HassController#hass capability color_temperature attributes [Array][ "value" ]
[latest-23242]2023-10-18T18:58:39.486Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability light_effect
[latest-23242]2023-10-18T18:58:39.486Z <HassController:5:HassController.js:258> HassController#hass capability light_effect attributes [Array][ "current" ]
[latest-23242]2023-10-18T18:58:39.487Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability binary_sensor
[latest-23242]2023-10-18T18:58:39.487Z <HassController:5:HassController.js:258> HassController#hass capability binary_sensor attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.488Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability person.binary_sensor
[latest-23242]2023-10-18T18:58:39.488Z <HassController:5:HassController.js:258> HassController#hass capability person.binary_sensor attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.489Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability motion_sensor
[latest-23242]2023-10-18T18:58:39.490Z <HassController:5:HassController.js:258> HassController#hass capability motion_sensor attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.490Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability tamper
[latest-23242]2023-10-18T18:58:39.491Z <HassController:5:HassController.js:258> HassController#hass capability tamper attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.491Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability co_detector
[latest-23242]2023-10-18T18:58:39.492Z <HassController:5:HassController.js:258> HassController#hass capability co_detector attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.492Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability door_sensor
[latest-23242]2023-10-18T18:58:39.493Z <HassController:5:HassController.js:258> HassController#hass capability door_sensor attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.493Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability freeze_detector
[latest-23242]2023-10-18T18:58:39.494Z <HassController:5:HassController.js:258> HassController#hass capability freeze_detector attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.494Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability gas_detector
[latest-23242]2023-10-18T18:58:39.495Z <HassController:5:HassController.js:258> HassController#hass capability gas_detector attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.495Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability heat_detector
[latest-23242]2023-10-18T18:58:39.496Z <HassController:5:HassController.js:258> HassController#hass capability heat_detector attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.496Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability presence_sensor
[latest-23242]2023-10-18T18:58:39.497Z <HassController:5:HassController.js:258> HassController#hass capability presence_sensor attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.497Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability smoke_detector
[latest-23242]2023-10-18T18:58:39.498Z <HassController:5:HassController.js:258> HassController#hass capability smoke_detector attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.498Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability window_sensor
[latest-23242]2023-10-18T18:58:39.499Z <HassController:5:HassController.js:258> HassController#hass capability window_sensor attributes [Array][ "state" ]
[latest-23242]2023-10-18T18:58:39.499Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability battery_maintenance
[latest-23242]2023-10-18T18:58:39.500Z <HassController:5:HassController.js:258> HassController#hass capability battery_maintenance attributes [Array][ "rechargeable", "replace", "charging" ]
[latest-23242]2023-10-18T18:58:39.500Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability value_sensor
[latest-23242]2023-10-18T18:58:39.501Z <HassController:5:HassController.js:258> HassController#hass capability value_sensor attributes [Array][ "value", "units" ]
[latest-23242]2023-10-18T18:58:39.501Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability temperature_sensor
[latest-23242]2023-10-18T18:58:39.502Z <HassController:5:HassController.js:258> HassController#hass capability temperature_sensor attributes [Array][ "value", "units" ]
[latest-23242]2023-10-18T18:58:39.502Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability humidity_sensor
[latest-23242]2023-10-18T18:58:39.503Z <HassController:5:HassController.js:258> HassController#hass capability humidity_sensor attributes [Array][ "value", "units" ]
[latest-23242]2023-10-18T18:58:39.503Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability pressure_sensor
[latest-23242]2023-10-18T18:58:39.504Z <HassController:5:HassController.js:258> HassController#hass capability pressure_sensor attributes [Array][ "value", "units" ]
[latest-23242]2023-10-18T18:58:39.504Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability voltage_sensor
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #19

    OK. Sorry. Try a fresh download of the ZIP file and install the updated version. Same routine... install (to config), restart Reactor, run test, post logs.

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

    1 Reply Last reply
    0
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #20

    So it looks like the ZIP file worked this time

    [latest-23242]2023-10-18T23:13:13.781Z <Structure:INFO> Structure#1 loading controller interface zwavejs (ZWaveJSController)
[latest-23242]2023-10-18T23:13:13.825Z <ZWaveJSController:null> Module ZWaveJSController v23194
[latest-23242]2023-10-18T23:13:13.827Z <Controller:INFO> Loaded ZWaveJSController version "0.1.23194"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/ZWaveJSController/
[latest-23242]2023-10-18T23:13:14.159Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs added file logger to zwavejs.log
[latest-23242]2023-10-18T23:13:14.160Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController)
[latest-23242]2023-10-18T23:13:14.182Z <DynamicGroupController:null> Module DynamicGroupController v22313
[latest-23242]2023-10-18T23:13:14.214Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController)
[latest-23242]2023-10-18T23:13:14.228Z <SystemController:null> Module SystemController v23214
[latest-23242]2023-10-18T23:13:14.242Z <Structure:INFO> Starting controller HassController#hass
[latest-23242]2023-10-18T23:13:14.243Z <HassController:NOTICE> HassController#hass starting...
[latest-23242]2023-10-18T23:13:14.256Z <Controller:INFO> HassController#hass ZIP data update found (/home/arman/Documents/reactor/config/hass_data.zip)
[latest-23242]2023-10-18T23:13:14.259Z <Structure:INFO> Starting controller ZWaveJSController#zwavejs
[latest-23242]2023-10-18T23:13:14.262Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_device_cfg, which is not consistent with the recommended naming
[latest-23242]2023-10-18T23:13:14.263Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_mfg_spec, which is not consistent with the recommended naming
[latest-23242]2023-10-18T23:13:14.263Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_device_ver, which is not consistent with the recommended naming
[latest-23242]2023-10-18T23:13:14.264Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_values, which is not consistent with the recommended naming
[latest-23242]2023-10-18T23:13:14.264Z <Controller:INFO> ZWaveJSController#zwavejs loaded zwavejs capabilities ver 23194 rev 1 format 1 
[latest-23242]2023-10-18T23:13:14.317Z <Controller:INFO> ZWaveJSController#zwavejs loaded implementation data ver 23194 rev 1 format 1 
[latest-23242]2023-10-18T23:13:14.317Z <Structure:INFO> Starting controller DynamicGroupController#groups
[latest-23242]2023-10-18T23:13:14.336Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online.
[latest-23242]2023-10-18T23:13:14.336Z <Structure:INFO> Starting controller SystemController#reactor_system
[latest-23242]2023-10-18T23:13:14.347Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
[latest-23242]2023-10-18T23:13:14.553Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs connecting to ws://192.168.8.85:3000
[latest-23242]2023-10-18T23:13:14.626Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs greeting from server: [Object]{ "type": "version", "driverVersion": "12.2.0", "serverVersion": "1.32.1", "homeId": 3775115912, "minSchemaVersion": 0, "maxSchemaVersion": 32 }
[latest-23242]2023-10-18T23:13:14.629Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs connected
[latest-23242]2023-10-18T23:13:14.630Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs sending connection initialization
[latest-23242]2023-10-18T23:13:14.644Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing initial inventory
[latest-23242]2023-10-18T23:13:14.666Z <Controller:INFO> HassController#hass ZIP update file capabilities ignored; ZIP version 23109.1 <= package version 23109.1
[latest-23242]2023-10-18T23:13:14.668Z <Controller:INFO> HassController#hass loaded hass capabilities ver 23109 rev 1 format 1 
[latest-23242]2023-10-18T23:13:14.758Z <Controller:INFO> HassController#hass ZIP update file device configuration version 23240.2 overrides package version 23240.1
[latest-23242]2023-10-18T23:13:14.759Z <Controller:INFO> HassController#hass loaded implementation data ver 23240 rev 2 format 1 
[latest-23242]2023-10-18T23:13:14.763Z <HassController:INFO> HassController#hass device mapping data loaded; checking...
[latest-23242]2023-10-18T23:13:14.765Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability power_switch
[latest-23242]2023-10-18T23:13:14.766Z <HassController:5:HassController.js:258> HassController#hass capability power_switch attributes [Array][ "state" ]
[latest-23242]2023-10-18T23:13:14.767Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability toggle
[latest-23242]2023-10-18T23:13:14.768Z <HassController:5:HassController.js:258> HassController#hass capability toggle attributes [Array][  ]
[latest-23242]2023-10-18T23:13:14.768Z <HassController:5:HassController.js:247> HassController#hass checking implementation for capability dimming

    However testing the rule the popup still showed on all browser mod devices. I know you had mentioned using x_hass.call_service on the device entity, but my question is how would MSR know what the browser_id would be for said entity? The browser_id is unique to this integration so I would think that MSR/HA would not have this info stored in the entity. Just a thought though. Is there any way we can get the call_service command for the HA system entity to work since it just seems like the target info isn't being passed through correctly?

    [latest-23242]2023-10-18T23:15:24.707Z <Rule:INFO> Fountain (rule-grpsdlp33d in Backyard Reactor) evaluated; trigger state unchanged (true); rule state remains SET
[latest-23242]2023-10-18T23:15:24.710Z <Rule:INFO> Backyard Fountain (rule-grptitus9c in Backyard Reactor) starting evaluation; because data-changed Data#states:cs-rule-grpsdlp33d
[latest-23242]2023-10-18T23:15:24.710Z <Rule:INFO> Fountain (rule-grpsdlp33d in Backyard Reactor) evaluation complete
[latest-23242]2023-10-18T23:15:24.711Z <Rule:INFO> Backyard Fountain (rule-grptitus9c in Backyard Reactor) trigger evaluation result is true (previously true)
[latest-23242]2023-10-18T23:15:24.711Z <Rule:INFO> Backyard Fountain (rule-grptitus9c in Backyard Reactor) evaluated; trigger state unchanged (true); rule state remains SET
[latest-23242]2023-10-18T23:15:24.712Z <Rule:INFO> Backyard Fountain (rule-grptitus9c in Backyard Reactor) evaluation complete
[latest-23242]2023-10-18T23:15:26.304Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.front_door1
[latest-23242]2023-10-18T23:15:26.315Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.front_east
[latest-23242]2023-10-18T23:15:26.324Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.back_garden
[latest-23242]2023-10-18T23:15:26.333Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.back_landing
[latest-23242]2023-10-18T23:15:26.342Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.front_entrance_east
[latest-23242]2023-10-18T23:15:26.349Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.front_entrance_west
[latest-23242]2023-10-18T23:15:26.355Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.backyard
[latest-23242]2023-10-18T23:15:26.362Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.east_side_house
[latest-23242]2023-10-18T23:15:26.369Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.deck_stairs
[latest-23242]2023-10-18T23:15:26.375Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.bar_landing
[latest-23242]2023-10-18T23:15:26.382Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.deck_door
[latest-23242]2023-10-18T23:15:26.389Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.west_side_back
[latest-23242]2023-10-18T23:15:26.395Z <HassController:5:HassController.js:352> HassController#hass updating hass entity camera.front_door_main
[latest-23242]2023-10-18T23:15:27.253Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-18T23:15:29.264Z <Engine:INFO> Enqueueing "Bar Tablet Alarm Arming Popup Copy<SET>" (rule-lnoyj3ub:S)
[latest-23242]2023-10-18T23:15:29.271Z <Engine:NOTICE> Starting reaction Bar Tablet Alarm Arming Popup Copy<SET> (rule-lnoyj3ub:S)
[latest-23242]2023-10-18T23:15:29.281Z <HassController:5:HassController.js:100> HassController#hass MediaPlayer#hass>media_player_bar_tablet_2 performOnEntity x_hass.call_service no domain-specific cap, trying generic
[latest-23242]2023-10-18T23:15:29.287Z <HassController:5:HassController.js:222> HassController#hass: sending payload for x_hass.call_service on MediaPlayer#hass>media_player_bar_tablet_2 action: [Object]{ "type": "call_service", "service_data": { "dismissable": true, "autoclose": false, "timeout": 120000, "content": { "type": "custom:mushroom-alarm-control-panel-card", "entity": "alarm_control_panel.bar_partition", "states": [ "armed_home", "armed_away" ], "layout": "vertical", "show_keypad": true } }, "domain": "browser_mod", "service": "popup", "target": { "entity_id": "media_player.bar_tablet_2" } }
[latest-23242]2023-10-18T23:15:29.298Z <HassController:INFO> HassController#hass action x_hass.call_service([Object]{ "service": "browser_mod.popup", "data": "dismissable: true\nautoclose: false\ntimeout: 120000\ncontent:\n  type: custom:mushroom-alarm-control-panel-card\n  entity: alarm_control_panel.bar_partition\n  states:\n    - armed_home\n    - armed_away\n  layout: vertical\n  show_keypad: true" }) on MediaPlayer#hass>media_player_bar_tablet_2 succeeded
[latest-23242]2023-10-18T23:15:29.303Z <Engine:INFO> Resuming reaction Bar Tablet Alarm Arming Popup Copy<SET> (rule-lnoyj3ub:S) from step 1
[latest-23242]2023-10-18T23:15:29.304Z <Engine:INFO> Bar Tablet Alarm Arming Popup Copy<SET> all actions completed.
[latest-23242]2023-10-18T23:15:30.576Z <HassController:5:HassController.js:352> HassController#hass updating hass entity binary_sensor.pabla_windows
[latest-23242]2023-10-18T23:15:33.070Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.pabla_windows_browser_path
[latest-23242]2023-10-18T23:15:33.119Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.pabla_windows_browser_path
[latest-23242]2023-10-18T23:15:33.243Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-18T23:15:34.425Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.pabla_windows_browser_path
[latest-23242]2023-10-18T23:15:34.443Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.pabla_windows_browser_path
[latest-23242]2023-10-18T23:15:35.627Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_wan_download_speed
[latest-23242]2023-10-18T23:15:35.640Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_wan_upload_speed
[latest-23242]2023-10-18T23:15:35.650Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_wired_download_speed
[latest-23242]2023-10-18T23:15:35.660Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_wired_upload_speed
[latest-23242]2023-10-18T23:15:35.670Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_bridge_download_speed
[latest-23242]2023-10-18T23:15:35.679Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_bridge_upload_speed
[latest-23242]2023-10-18T23:15:35.700Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.pabla_windows_browser_path
[latest-23242]2023-10-18T23:15:36.247Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-18T23:15:36.678Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_ram
[latest-23242]2023-10-18T23:15:36.684Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_cpu
[latest-23242]2023-10-18T23:15:37.062Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.pabla_windows_browser_path
[latest-23242]2023-10-18T23:15:38.841Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.processor_use
[latest-23242]2023-10-18T23:15:38.851Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.memory_free
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #21

    First, I can see that target is being passed correctly.

    According to their documentation, the browser_id is something you have to add to the service data. It even says this in their documentation:

    If no target or browser_id is specified, the service will target all registerd [sic] Browsers.

    That's not something Reactor would or could know to add automatically, it's an integration-specific implementation detail; it's not part of target (which is HA-defined structure and only supports HA's native entity_id, device_id and area_id).

    I didn't notice before, but you don't seem to be passing browser_id. That might help. It looks like you can set the browser ID on each client, which seems like a good idea (make them human-readable/friendly).

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

    1 Reply Last reply
    0
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #22

    Yes this is what my original YAML was trying to do.

    dismissable: true
autoclose: false
timeout: 120000
content:
  type: custom:mushroom-alarm-control-panel-card
  entity: alarm_control_panel.bar_partition
  states:
    - armed_home
    - armed_away
  layout: vertical
  show_keypad: true
target:
  device_id: 34ae76561192c4bb0b64fb07ad0f01c1

    But the target: device_id: 34ae76561192c4bb0b64fb07ad0f01c1 is not being passed through correctly and the popup shows up on all devices. I also have set the browser_id for each device but thats only UI facing the number is what the HA service uses. See HA service call:

    service: browser_mod.popup
data:
  dismissable: true
  autoclose: false
  content:
    type: custom:mushroom-alarm-control-panel-card
    entity: alarm_control_panel.bar_partition
    states:
      - armed_home
      - armed_away
    layout: vertical
    show_keypad: true
  timeout_action: 120000
target:
  device_id: 34ae76561192c4bb0b64fb07ad0f01c1

    Here is the Reactor log for when I call a service using the first YAML code.

    [latest-23242]2023-10-19T17:23:48.911Z <HassController:5:HassController.js:352> HassController#hass updating hass entity device_tracker.ec_71_db_69_bf_c4
[latest-23242]2023-10-19T17:23:49.589Z <HassController:5:HassController.js:352> HassController#hass updating hass entity binary_sensor.pabla_windows
[latest-23242]2023-10-19T17:23:50.546Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T17:23:53.537Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T17:23:56.365Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) configuration changed; reloading
[latest-23242]2023-10-19T17:23:56.370Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) stopping
[latest-23242]2023-10-19T17:23:56.385Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) stopped
[latest-23242]2023-10-19T17:23:56.386Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) starting
[latest-23242]2023-10-19T17:23:56.387Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) can't start -- rule is disabled
[latest-23242]2023-10-19T17:23:56.536Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T17:23:57.425Z <HassController:5:HassController.js:100> HassController#hass MediaPlayer#hass>media_player_bar_tablet_2 performOnEntity x_hass.call_service no domain-specific cap, trying generic
[latest-23242]2023-10-19T17:23:57.427Z <HassController:5:HassController.js:222> HassController#hass: sending payload for x_hass.call_service on MediaPlayer#hass>media_player_bar_tablet_2 action: [Object]{ "type": "call_service", "service_data": { "dismissable": true, "autoclose": false, "timeout": 120000, "content": { "type": "custom:mushroom-alarm-control-panel-card", "entity": "alarm_control_panel.bar_partition", "states": [ "armed_home", "armed_away" ], "layout": "vertical", "show_keypad": true } }, "domain": "browser_mod", "service": "popup", "target": { "entity_id": "media_player.bar_tablet_2" } }
[latest-23242]2023-10-19T17:23:57.432Z <HassController:INFO> HassController#hass action x_hass.call_service([Object]{ "service": "browser_mod.popup", "data": "data:\n  dismissable: true\n  autoclose: false\n  timeout: 120000\n  content:\n    type: custom:mushroom-alarm-control-panel-card\n    entity: alarm_control_panel.bar_partition\n    states:\n      - armed_home\n      - armed_away\n    layout: vertical\n    show_keypad: true\ntarget:\n  device_id: 34ae76561192c4bb0b64fb07ad0f01c1" }) on MediaPlayer#hass>media_player_bar_tablet_2 succeeded
[latest-23242]2023-10-19T17:23:58.667Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.memory_free
[latest-23242]2023-10-19T17:23:59.545Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T17:24:02.560Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_electricity_consumption
[latest-23242]2023-10-19T17:24:02.570Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_electricity_consumption_cost
[latest-23242]2023-10-19T17:24:02.579Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_electricity_consumption_cost
[latest-23242]2023-10-19T17:24:02.587Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.2_month_hydro_usage
[latest-23242]2023-10-19T17:24:02.597Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T17:24:02.617Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.2_month_hydro_cost
[latest-23242]2023-10-19T17:24:02.626Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.2_month_hydro_cost
[latest-23242]2023-10-19T17:24:04.337Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.main_floor_tablet_internal_storage_free_space
[latest-23242]2023-10-19T17:24:04.347Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.main_floor_tablet_free_memory
[latest-23242]2023-10-19T17:24:05.211Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bar_tablet_internal_storage_free_space
[latest-23242]2023-10-19T17:24:05.216Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bar_tablet_free_memory
[latest-23242]2023-10-19T17:24:05.619Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T17:24:08.555Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T17:24:10.096Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_wan_download_speed
[latest-23242]2023-10-19T17:24:10.106Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_wan_upload_speed
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #23

    You need to send browser_id in data

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

    1 Reply Last reply
    0
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #24

    Tried browser_id no popup on any devices, used device_id and popup came up on all devices again. Logs for both attempts below

    [latest-23242]2023-10-19T21:30:44.024Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:44.544Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.processor_use
[latest-23242]2023-10-19T21:30:44.549Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.memory_free
[latest-23242]2023-10-19T21:30:44.553Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.memory_use_percent
[latest-23242]2023-10-19T21:30:47.353Z <HassController:5:HassController.js:352> HassController#hass updating hass entity climate.shed_climate
[latest-23242]2023-10-19T21:30:48.374Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T21:30:48.387Z <HassController:5:HassController.js:352> HassController#hass updating hass entity climate.shed_climate
[latest-23242]2023-10-19T21:30:49.377Z <HassController:5:HassController.js:352> HassController#hass updating hass entity device_tracker.ec_71_db_69_bf_c4
[latest-23242]2023-10-19T21:30:49.386Z <HassController:5:HassController.js:352> HassController#hass updating hass entity device_tracker.80_64_6f_85_fe_37
[latest-23242]2023-10-19T21:30:49.396Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.asus_router_connected_devices
[latest-23242]2023-10-19T21:30:49.499Z <HassController:5:HassController.js:100> HassController#hass MediaPlayer#hass>media_player_bar_tablet_2 performOnEntity x_hass.call_service no domain-specific cap, trying generic
[latest-23242]2023-10-19T21:30:49.502Z <HassController:5:HassController.js:222> HassController#hass: sending payload for x_hass.call_service on MediaPlayer#hass>media_player_bar_tablet_2 action: [Object]{ "type": "call_service", "service_data": { "dismissable": true, "autoclose": false, "timeout": 120000, "content": { "type": "custom:mushroom-alarm-control-panel-card", "entity": "alarm_control_panel.bar_partition", "states": [ "armed_home", "armed_away" ], "layout": "vertical", "show_keypad": true }, "browser_id": "05c0cb75141aeb8d38a86999e07e6a7d" }, "domain": "browser_mod", "service": "popup", "target": { "entity_id": "media_player.bar_tablet_2" } }
[latest-23242]2023-10-19T21:30:49.508Z <HassController:INFO> HassController#hass action x_hass.call_service([Object]{ "service": "browser_mod.popup", "data": "dismissable: true\nautoclose: false\ntimeout: 120000\ncontent:\n  type: custom:mushroom-alarm-control-panel-card\n  entity: alarm_control_panel.bar_partition\n  states:\n    - armed_home\n    - armed_away\n  layout: vertical\n  show_keypad: true\nbrowser_id: 05c0cb75141aeb8d38a86999e07e6a7d" }) on MediaPlayer#hass>media_player_bar_tablet_2 succeeded
[latest-23242]2023-10-19T21:30:51.381Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T21:30:54.387Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T21:30:54.943Z <HassController:5:HassController.js:352> HassController#hass updating hass entity binary_sensor.main_floor_motion
[latest-23242]2023-10-19T21:30:55.321Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.home_partition_keypad
[latest-23242]2023-10-19T21:30:55.326Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:30:55.326Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:30:55.326Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:30:55.328Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:55.328Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:55.331Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:55.332Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:55.335Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:55.336Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:55.337Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:55.338Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:55.338Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) starting evaluation; because data-changed Data#states:cs-rule-grpri779hy
[latest-23242]2023-10-19T21:30:55.338Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:55.377Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:55.377Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:55.378Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:56.801Z <HassController:5:HassController.js:352> HassController#hass updating hass entity binary_sensor.main_floor_motion
[latest-23242]2023-10-19T21:30:56.963Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.home_partition_keypad
[latest-23242]2023-10-19T21:30:56.973Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:30:56.973Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:30:56.974Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:30:56.977Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:56.978Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:56.983Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:56.983Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:56.992Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:56.993Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:56.996Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:56.997Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:56.997Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) starting evaluation; because data-changed Data#states:cs-rule-grpri779hy
[latest-23242]2023-10-19T21:30:56.998Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:57.057Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:57.057Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:57.058Z <Rule:INFO> Zone Opened (rule-ljwaswws in Notifications) evaluation complete
[latest-23242]2023-10-19T21:30:57.361Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_instantaneous_demand
[latest-23242]2023-10-19T21:30:58.892Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) configuration changed; reloading
[latest-23242]2023-10-19T21:30:58.896Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) stopping
[latest-23242]2023-10-19T21:30:58.912Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) stopped
[latest-23242]2023-10-19T21:30:58.912Z <Rule:NOTICE> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) starting
[latest-23242]2023-10-19T21:30:58.913Z <Rule:INFO> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) starting evaluation; because startup
[latest-23242]2023-10-19T21:30:58.916Z <Rule:INFO> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:30:58.917Z <Rule:INFO> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:30:58.918Z <Rule:INFO> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) evaluation complete
[latest-23242]2023-10-19T21:30:58.918Z <Rule:INFO> Bar Tablet Alarm Arming Popup Copy (rule-lnoyj3ub in Home Reactor ) started
[latest-23242]2023-10-19T21:30:59.546Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.processor_use
[latest-23242]2023-10-19T21:30:59.556Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.memory_free
[latest-23242]2023-10-19T21:30:59.564Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.memory_use_percent
[latest-23242]2023-10-19T21:31:00.052Z <HassController:5:HassController.js:100> HassController#hass MediaPlayer#hass>media_player_bar_tablet_2 performOnEntity x_hass.call_service no domain-specific cap, trying generic
[latest-23242]2023-10-19T21:31:00.055Z <HassController:5:HassController.js:222> HassController#hass: sending payload for x_hass.call_service on MediaPlayer#hass>media_player_bar_tablet_2 action: [Object]{ "type": "call_service", "service_data": { "dismissable": true, "autoclose": false, "timeout": 120000, "content": { "type": "custom:mushroom-alarm-control-panel-card", "entity": "alarm_control_panel.bar_partition", "states": [ "armed_home", "armed_away" ], "layout": "vertical", "show_keypad": true }, "device_id": "05c0cb75141aeb8d38a86999e07e6a7d" }, "domain": "browser_mod", "service": "popup", "target": { "entity_id": "media_player.bar_tablet_2" } }
[latest-23242]2023-10-19T21:31:00.064Z <HassController:INFO> HassController#hass action x_hass.call_service([Object]{ "service": "browser_mod.popup", "data": "dismissable: true\nautoclose: false\ntimeout: 120000\ncontent:\n  type: custom:mushroom-alarm-control-panel-card\n  entity: alarm_control_panel.bar_partition\n  states:\n    - armed_home\n    - armed_away\n  layout: vertical\n  show_keypad: true\ndevice_id: 05c0cb75141aeb8d38a86999e07e6a7d" }) on MediaPlayer#hass>media_player_bar_tablet_2 succeeded
[latest-23242]2023-10-19T21:31:00.382Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_electricity_consumption
[latest-23242]2023-10-19T21:31:00.392Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_electricity_consumption_cost
[latest-23242]2023-10-19T21:31:00.396Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.bchydro_electricity_consumption_cost
[latest-23242]2023-10-19T21:31:00.401Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.2_month_hydro_usage
[latest-23242]2023-10-19T21:31:00.406Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.2_month_hydro_cost
[latest-23242]2023-10-19T21:31:00.410Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.2_month_hydro_cost
[latest-23242]2023-10-19T21:31:02.049Z <HassController:5:HassController.js:352> HassController#hass updating hass entity binary_sensor.pabla_windows
[latest-23242]2023-10-19T21:31:02.255Z <HassController:5:HassController.js:352> HassController#hass updating hass entity binary_sensor.main_floor_motion
[latest-23242]2023-10-19T21:31:02.614Z <HassController:5:HassController.js:352> HassController#hass updating hass entity sensor.home_partition_keypad
[latest-23242]2023-10-19T21:31:02.620Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:31:02.620Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:31:02.620Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_home_partition_keypad
[latest-23242]2023-10-19T21:31:02.622Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:31:02.623Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:31:02.625Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:31:02.626Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:31:02.629Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) trigger evaluation result is false (previously false)
[latest-23242]2023-10-19T21:31:02.630Z <Rule:INFO> Night or Away or Vacation or Armed (rule-grpri779hy in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23242]2023-10-19T21:31:02.632Z <Rule:INFO> Alexa No Zones Open (rule-grpozng7j0 in Notifications) evaluation complete
[latest-23242]2023-10-19T21:31:02.632Z <Rule:INFO> Alexa Which Zones Open (rule-grpozjdlfa in Notifications) evaluation complete
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #25

    OK, you can't put device_id in data; it goes in target. And you can't do that, because you can't modify target, Reactor controls it. And Reactor has no way to get the device ID for a HA entity (it's not exposed in their documented APIs), so it's not possible for me to make a service call with anything other than the HA entity_id. That's neither here nor there, because (a) the docs for browser_mod are very specific that browser_id is to be used, and (b) both the service data from the API and my testing confirm that entity_id is supported and works fine to reach the browser_mod integration.

    In your attempt that used browser_id, you have used the HA device_id, and that's wrong. The browser ID comes from browser_mod's configuration (left margin panel), visible in the same place you would/could set/change it). The browser_id is much shorter than a HA device_id by default. Again, suggest you study the integration's docs carefully.

    In addition, I've now installed this integration myself, and in my own testing:

    1. entity_id as a target works fine every time, and
    2. if you don't include browser_id in the data, the pop-up comes up on all browsers, which is word for word what they say in their documentation (as I quoted in my previous message above). And this is true whether I use the HA Developer Tools interface or x_hass.call_service in Reactor.

    So you need to use browser_id in the data, and use the correct string for that ID.

    231b67dc-742f-4d76-867d-f21a7a7afb63-image.png

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

    1 Reply Last reply
    0
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #26

    That looks like it did the trick! Was getting a bit confused between browser_id and device_id but your explanation cleared things up. Thanks again Patrick!

    1 Reply Last reply
    0

Recent Topics

  • toggledbitsT
    Upcoming Release -- Plan for the Future
  • G
    floor heating automation
  • T
    Need help. Looking people
  • SnowmanS
    Honeywell TH6320ZW2003_T6_Pro_ZWave shows hvac_control.state="heat" in zwaveJSController
  • toggledbitsT
    Dismiss -option for updates
  • toggledbitsT
    case statement with a single when clause fails
  • D
    [Solved] HTTP API no response on perform action
  • wmarcolinW
    CallMeBot new interface?
  • SnowmanS
    TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
Powered by NodeBB | Contributors
Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
  • Login
  • Don't have an account? Register
  • Login or register to search.