Good morning,
I'm trying to figure out if there is a way to evaluate if a command was completed and retry if it did not complete.
I have 14 iBlinds 3.1 z-wave controllers in my home. 95% of the time, they work just fine. Occasionally, I'll get a blind that does not open on the first attempt. When I go into Home Assistant, and manually open or close the blind, it works.
I have 3 reactions set up for each room. One to open, one to close, and one partial open for sun glare. Each of them is set up as below.
5afc9924-4300-4718-9e23-8855c4a3a9fd-image.png
The reactions are set up to wait for 5 seconds before going onto the next blind, so the z-wave network doesn't get overwhelmed.
In addition, the set command to run the reactions has "Wait for completion" checked.
3919fc06-c1f1-4c49-bf95-716028d18a27-image.png
I also have a routine set up whenever a z-wave device reports as non-functional (dead), it'll get pinged to wake it up. This usually works to wake them up.
16df4bff-c733-4ec2-a55c-c964238ada3b-image.png
Appreciate any ideas to make this more reliable.
I'm running:
Reactor latest-24190-bd310acc, Bare-metal on Fedora WaveJSController [0.1.23326] Home Assistant: 2024.7.0I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.
For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.
Good morning,
I'm going through my ruleset this morning, trying to get away from haas>blahblablah entries and completely migrate them all to zwavejs>xx-0 entries where possible.
I have 3 Aeon MultiSensor 6 devices in my home, all USB powered.
When using Haas entries, I see an entry for hass>binary_sensor_guest_bedroom_multisensor_home_security_motion_detection, and motion_sensor.state (primary)
Screenshot 2024-07-25 at 8.25.53 AM.png
Under ZwaveJS, this entry appears to be missing.
Screenshot 2024-07-25 at 8.26.51 AM.png
From the Entities page:
battery_power.level=1
battery_power.since=1721910337433
binary_sensor.state=false
humidity_sensor.units="%"
humidity_sensor.value=46
light_sensor.units="Lux"
light_sensor.value=5
tamper.state=false
temperature_sensor.units="°F"
temperature_sensor.value=73.8
x_debug.dt={}
x_zwave_values.Basic_currentValue=0
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Binary_Sensor_Any=false
x_zwave_values.Configuration_Automatic_Report_Group_1_Battery_1=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Humidity_64=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Luminance_128=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Temperature_32=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Ultraviolet_16=1
x_zwave_values.Configuration_Automatic_Report_Group_2_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_1=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_2=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_3=3600
x_zwave_values.Configuration_Automatic_Temperature_Reporting_Unit=2
x_zwave_values.Configuration_Battery_Level_Threshold=10
x_zwave_values.Configuration_Current_Power_Mode_65280=0
x_zwave_values.Configuration_Humidity_Above_Lower_Limit_32=0
x_zwave_values.Configuration_Humidity_Below_Lower_Limit_2=0
x_zwave_values.Configuration_Humidity_Change_Threshold=10
x_zwave_values.Configuration_Humidity_Recover_Limit=5
x_zwave_values.Configuration_Humidity_Sensor_Calibration=0
x_zwave_values.Configuration_LED_Blinking=0
x_zwave_values.Configuration_Lighting_Recover_Limit=10
x_zwave_values.Configuration_Lock_Configuration=0
x_zwave_values.Configuration_Low_Battery_Threshold=20
x_zwave_values.Configuration_Low_Temperature_Alarm_15_C=0
x_zwave_values.Configuration_Lower_Humidity_Limit=50
x_zwave_values.Configuration_Lower_Lighting_Limit=100
x_zwave_values.Configuration_Lower_Temperature_Limit_4294901760=320
x_zwave_values.Configuration_Lower_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Lower_Ultraviolet_Limit=4
x_zwave_values.Configuration_Luminance_Above_Lower_Limit_64=0
x_zwave_values.Configuration_Luminance_Below_Lower_Limit_4=0
x_zwave_values.Configuration_Luminance_Change_Threshold=100
x_zwave_values.Configuration_Luminance_Sensor_Calibration=0
x_zwave_values.Configuration_Motion_Sensor_Report_Type_to_Send=2
x_zwave_values.Configuration_PIR_Sensitivity=3
x_zwave_values.Configuration_PIR_Sensor_Timeout=20
x_zwave_values.Configuration_Recover_Limit_Temperature_Unit_255=2
x_zwave_values.Configuration_Report_Above_Humidity_Threshold_32=0
x_zwave_values.Configuration_Report_Above_Luminance_Threshold_64=0
x_zwave_values.Configuration_Report_Above_Temperature_Threshold_16=0
x_zwave_values.Configuration_Report_Above_Ultraviolet_Threshold_128=0
x_zwave_values.Configuration_Report_Below_Humidity_Threshold_2=0
x_zwave_values.Configuration_Report_Below_Luminance_Threshold_4=0
x_zwave_values.Configuration_Report_Below_Temperature_Threshold_1=0
x_zwave_values.Configuration_Report_Below_Ultraviolet_Threshold_8=0
x_zwave_values.Configuration_Reset_Parameters_101_103_to_Default_Values=null
x_zwave_values.Configuration_Reset_Parameters_111_113_to_Default_Values=null
x_zwave_values.Configuration_Reset_to_Factory_Default_Setting=null
x_zwave_values.Configuration_Selective_Reporting=0
x_zwave_values.Configuration_Sleep_State_255=2
x_zwave_values.Configuration_Temperature_Above_Lower_Limit_16=0
x_zwave_values.Configuration_Temperature_Below_Lower_Limit_1=0
x_zwave_values.Configuration_Temperature_Calibration_Offset_65280=0
x_zwave_values.Configuration_Temperature_Calibration_Unit_255=2
x_zwave_values.Configuration_Temperature_Change_Threshold_4294901760=20
x_zwave_values.Configuration_Temperature_Recover_Limit_65280=20
x_zwave_values.Configuration_Temperature_Threshold_Unit_3840=2
x_zwave_values.Configuration_Ultraviolet_Above_Lower_Limit_128=0
x_zwave_values.Configuration_Ultraviolet_Below_Lower_Limit_8=0
x_zwave_values.Configuration_Ultraviolet_Change_Threshold=2
x_zwave_values.Configuration_Ultraviolet_Recover_Limit=2
x_zwave_values.Configuration_Ultraviolet_Sensor_Calibration=0
x_zwave_values.Configuration_Upper_Humidity_Limit=60
x_zwave_values.Configuration_Upper_Lighting_Limit=1000
x_zwave_values.Configuration_Upper_Temperature_Limit_4294901760=824
x_zwave_values.Configuration_Upper_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Upper_Ultraviolet_Limit=8
x_zwave_values.Configuration_Wake_Device_for_10_minutes_After_Power_On=1
x_zwave_values.Configuration_Wake_Up_Timeout=15
x_zwave_values.Manufacturer_Specific_manufacturerId=134
x_zwave_values.Manufacturer_Specific_productId=100
x_zwave_values.Manufacturer_Specific_productType=258
x_zwave_values.Multilevel_Sensor_Air_temperature=73.8
x_zwave_values.Multilevel_Sensor_Humidity=46
x_zwave_values.Multilevel_Sensor_Illuminance=5
x_zwave_values.Multilevel_Sensor_Ultraviolet=0
x_zwave_values.Notification_Home_Security_Cover_status=0
x_zwave_values.Notification_Home_Security_Motion_sensor_status=0
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Version_firmwareVersions=["1.17"]
x_zwave_values.Version_hardwareVersion=100
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="4.54"
x_zwave_values.Wake_Up_controllerNodeId=1
x_zwave_values.Wake_Up_wakeUpInterval=3600
zwave_device.capabilities=[32,48,49,112,113,114,128,132,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Sensor"
zwave_device.impl_sig="23326: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=[134,258,100]
zwave_device.max_data_rate=null
zwave_device.node_id=53
zwave_device.specific_class="Routing Multilevel Sensor"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"1.17"]
zwave_device.wakeup_interval=3600
I'm running:
Reactor latest-24190-bd310acc, Bare-metal on Fedora
WaveJSController [0.1.23326]
Home Assistant: 2024.7.0
I'm fetching certain data five past every hour, but I would like to do it closer to the hour, e.g. 1 or 2 past (but not at the hour).
I experimented with the following rule that almost works (triggers also at the hour which is not the intention). Any advice for a solution?
It would be nice to have an ability to bookmark a direct link to a dashboard item. In my case I would use this feature to access a virtual switch directly.
Hi @toggledbits
Would you please consider adding an extra sublevel in the rulesets?
I have grouped my rules in rooms/ areas. This works great for me, but I would also like to group rules for the same functionality (in a room). This would make the rules easier to find and name.
Please let me know if this is an option. Thanks!
@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
@toggledbits,
I have this device attached to my system, but use a DSC panel. If you need testers to move forward, I'm happy to help.
I'm curious what your thinking the use case is for this. I currently have it integrated into HomeAssistant, and it works fine for the most part. The one thing I can't do is bypass zones, which I would like to have the ability to do.
Are you looking at more direct control for the panel, as opposed to having to jump through HA (or another system) first?
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.I have the following ruleset which I though had been working well until this morning when I noticed it's not.
I've put four weather conditions in an in array and one of them is the current weather condition - but the rule is not true. Now the cloud cover percentage is not yet met but this is an or rule so as long as the "Current Conditions" are met then it should go true.
What's the obvious thing I'm missing here? (I've tried spaces/no spaces in the in and no difference.)
Hi,
Running the latest MSR latest-24152-3455578a with the latest HA 2024.6.1. When trying to call a service I get the following in the MSR logs. Is this a version mismatch? I am not seeing anything in the HA logs.
[latest-24152]2024-06-11T10:29:56.162Z <Rule:INFO> rule-Monitor-DHW (rule-lsvq5k3x in Central Heating) started [latest-24152]2024-06-11T10:29:58.625Z <HassController:WARN> HassController#hass unknown service opentherm_gw.set_hot_water_setpoint in x_hass.call_service action on Thermostat#hass>climate_living_room_otgw [latest-24152]2024-06-11T10:29:58.626Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Thermostat#hass>climate_living_room_otgw action: [Object]{ "type": "call_service", "service_data": { "gateway_id": "living_room_otgw", "temperature": 65 }, "domain": "opentherm_gw", "service": "set_hot_water_setpoint", "target": { "entity_id": "climate.living_room_otgw" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:ERR> HassController#hass request 1718101798626<6/11/2024, 12:29:58 PM> (call_service) failed: [Object]{ "id": 1718101798626, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "extra keys not allowed @ data['entity_id']" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:WARN> HassController#hass action x_hass.call_service([Object]{ "service": "opentherm_gw.set_hot_water_setpoint", "data": "{ \"gateway_id\": \"living_room_otgw\", \"temperature\": 65 }" }) on Thermostat#hass>climate_living_room_otgw failed!Cheers Rene
Some background
I'm trying to integrate a Zigbee device into the MSR using zigbee2mqtt bridge and MQTTController. The device in question is a cheap mood light that has following properties that I'd like to control:
I'v already managed to get the switch part working and can toggle the light on/off. Also the brightness value is mapped back to MSR. In zigbee2mqtt it has a value range from 0 to 254, so this the reason for the expression:
expr: 'payload.brightness / 254'Here's the entity definition (don't know whether the type should be something else than the Switch)
zigbee-lidl-mood-light: name: 'Lidl Mood Light' friendly_name: 'Mood Light' type: Switch uses_template: lidl-moodlightAnd the corresponding template (NOTE: rgb_color has not been defined in this example):
lidl-moodlight: init: "zigbee2mqtt/%friendly_name%/get/state" query: "zigbee2mqtt/%friendly_name%/get/state" capabilities: - power_switch - toggle - dimming primary_attribute: power_switch.state events: "zigbee2mqtt/%friendly_name%": "power_switch.state": json_payload: true expr: 'upper(payload.state) == "ON"' "dimming.level": json_payload: true expr: 'payload.brightness / 254' actions: power_switch: "on": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'ON' "off": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'OFF' set: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: expr: "parameters.state ? 'ON' : 'OFF'" type: raw toggle: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'TOGGLE'The problem
In order to control the brightness or the RGB color values, I would have send a JSON payload in corresponding actions. But I have no idea how to define it in the template. The reason why the switch part is working is that the zigbee2mqtt accepts also plain ON / OFF / TOGGLE string payloads in that case.
But the brightness should be controlled with the following payload:
{"brightness": 196}And the RGB color like:
{"color":{"rgb":"46,102,150"}}Here's the link for the documentation (the Exposes part defines the messages).
So how should I define the JSON payload for example for the dimming action? It definitely should be some sort of expressions since I have to map the MSR real value (0...1) to (0...254) for the zigbee2mqtt.
actions: dimming: set: topic: "zigbee2mqtt/%friendly_name%/set" payload: expr: ????? type: jsonAnother problem is the RGB value. I could use the rgb_color capability for the setting but the problem is that the zigbee2mqtt only reports the current color in hue/saturation or xy coordinates.
Here's an example of published message after setting the color:
Topic: zigbee2mqtt/Mood Light QoS: 0 { "brightness":254, "color":{ "hue":240, "saturation":100, "x":0.1355, "y":0.0399 }, "color_mode":"xy", "color_temp":574, "linkquality":96, "state":"ON" }I would have to map those values back to RGB, but is it even possible with existing constructs in MQTTController's templates?
Help would be appreciated @toggledbits
br,
mgvra
That's probably more appropriate to post on Mantis for @toggledbits, but since I know there's at least @Crille publishing templates, my intent with this post is to open a broader discussion.
Long story short: I'm starting to slowly add new template for Shelly Plus and I noticed I'll end up with a dozen more templates, all similar but simply different in trivial details, all sharing a large amount of code and all needing special cares when fixing bugs/adding features (as the latest wifi_status addition).
So, I'm wondering if it's time to start thinking of some sort of inheritance in templates, where I could just create a generic shelly_gen1 and use it as a base for shelly_relay, and this be used as the base for shelly_relay_power and so on.
I could probably achieve this with some sort of scripting on my side to generate templates via code, but maybe there's a better way of doing this, or it's already on the radar.
I need a handful of victims volunteers to help test previews of the next build of Reactor. A long-standing request was for "a simple login mechanism," but in practice, adding user authentication and competent access control turned out to be a pretty big project with a lot of big changes on both server and client sides. It's a bit more than I'm comfortable testing myself and springing out to everyone at once, so I'd like to work with a small group to put it through "sea trials."
Major changes/features include:
User authentication with hashed password storage; User group configuration with application restriction (admin, dashboard, API); Detailed control over API access, with user- and token-based authentication/authorization; Improvements to the HTTPS service; Improvements to UI coordination with the core for Rules and Reactions.If this sounds like something you'd like to help with, drop me a reply here in this thread or privately.
[Solution: Reactor 24115 is not compatible with MQTTController > 24120]
Reactor latest-24115 bare metal.
All MQTT entities stop working after updating MQTTController to 24142, downgrade to 24120 and they are back. Templates and configured entities has not been changed between versions.
I'm not sure if uses_template should be replaced by ìnclude in entity configuration in reactor.yaml but I guess not, I've tried it and it did not do any difference.
I have not tried to update Reactor to userauth version.
Example entity in reactor.yaml that uses MQTTController included template:
entities: "takflakt_kallare": name: "Takfläkt källare" topic: "Källartemp" unit: "" uses_template: tasmota_generic_relay init: "cmnd/%topic%/POWER%unit%"Any hints? Do you need more info, please let me know.
Log from startup:
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
![](https://github.com/fluidicon.png)
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Is the following config correct?
- id: time_series name: "Out temp" capabilities: temperature_sensor: attributes: value: model: time series entity: "hass>sensor_outdoor_temperature" attribute: "temperature_sensor.value" interval: 5 # minutes retention: 20 # minutes aggregate: wma primary_attribute: temperature_sensor.value type: ValueSensorSpecifically, is "depth" directive needed/mandatory here? Reason I'm asking is that I'm not getting a "final" value in MSR, only debug values are shown:
temperature_sensor.units=null temperature_sensor.value=null x_virtualentity.last_request_time=null x_virtualentity.request_failures=null x_virtualentity.template=null x_virtualentity.timeseries_debug=[{"time":1716537360000,"value":22.1},{"time":1716537660000,"value":22},{"time":1716537960000,"value":22},{"time":1716538260000,"value":21.9},{"time":1716538560000,"value":22}]Good morning,
I apologize if this subject has been covered. I did try the search, but I'm not coming up with any topics on my issue.
I'm running userauth-24137-57b41335, bare metal installation on Fedora 39 Server.
I have a rule set up to turn the Eco mode off on my Nest Thermostat when the thermostat is set to Away (Rule State: Away Mode), the user (Driver) presence in my car changes to true, and the destination is set to home.
93804f7c-62d6-42c0-ae04-ff602011a6fd-image.png
This works fine for most days, where I'm headed home from work (commute is about 45 minutes). What I don't want it to do is set change it to Eco mode if my ETA is more than an hour.
There is a sensor/entity for Time to Arrival when the Destination is set. What it appears to provide is the Time OF arrival/ETA, not time until arrival. If it was Time until Arrival, and it was a numeric value, I could simply test if the value is less than 60 and be done with it.
I pulled up the history through Home Assistant for my morning commute and this appears to be what it is providing.
c2a32739-c84f-4a05-95d9-73793ed818f5-image.png
So what I need to do is to do a calculation of the the ETA from the sensor value and subtract the current time, and get a value in minutes that I can determine if it's less than 60.
I believe I can do this with the local expression, but I don't see anything for the system time, or local time. Also, do the local expressions update themselves if the sensors do?
Good morning,
I'm running userauth-24137-57b41335 on Fedora 39, bare metal installation.
ZWaveJSController 0.1.23254
Home Assistant:
Core, 2024.5.3 Supervisor, 2024.05.1 Operating System, 12.3 Frontend, 20240501.1I'm trying to troubleshoot a Dynamic Group Controller and notification alert that I've set up for low battery level.
In my Reactor.config, I have the following lines:
name: "Dynamic Group Controller" implementation: DynamicGroupController config: groups: "zwavejs_dead": select: - include_group: "zwavejs" filter_expression: "entity?.attributes?.zwave_device?.status == 3" group_actions: true "low_battery": select: - include_capability: battery_power filter_expression: > entity.attributes.battery_power.level < 0.35The idea here is that I should only have members of this group that have a battery level below 35%. When I go into Entities, I show a whole slew of devices, none of which have a battery level below the threshold.
a77e445b-ab78-4752-a624-3c4117f34f90-image.png
I also tried setting up a rule to generate a push notification once a day, but with all of the group members, I've had to disable the rule. I believe I have it set up correctly, but I'm not 100% sure. I want the notification to tell me the battery level for that device as well.
289b4f68-03ba-49c0-8275-f0f197d13a3a-image.png
ce24a76e-6865-40bd-bd85-632e54d315a8-image.png dc837424-deb5-4ef7-8f0d-3676f1769535-image.png
Can anyone point to me what I may have misconfigured to get these results?
I should also note I'm only interested in ZWaveJS devices. It's showing me battery status for my iPad and car as well, which I don't need it to send me.
Need Some Help Using browser_mod (HA integration)
-
You placed the entire ZIP file, not unzipped, in the
config
directory? -
Can you confirm that after restart of Reactor, you find a log message containing the text
ZIP data update found
, and another shortly afterZIP update file device configuration version 23240.2 overrides package version xxx.yyy
? -
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
-
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. -
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 thebrowser_id
would be for said entity? Thebrowser_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 thecall_service
command for the HA system entity to work since it just seems like thetarget
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
-
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 servicedata
. 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 nativeentity_id
,device_id
andarea_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). -
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 thebrowser_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
-
You need to send
browser_id
indata
-
Tried
browser_id
no popup on any devices, useddevice_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
-
OK, you can't put
device_id
in data; it goes intarget
. And you can't do that, because you can't modifytarget
, 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 HAentity_id
. That's neither here nor there, because (a) the docs for browser_mod are very specific thatbrowser_id
is to be used, and (b) both the service data from the API and my testing confirm thatentity_id
is supported and works fine to reach the browser_mod integration.In your attempt that used
browser_id
, you have used the HAdevice_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). Thebrowser_id
is much shorter than a HAdevice_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:
entity_id
as atarget
works fine every time, and- 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 orx_hass.call_service
in Reactor.
So you need to use
browser_id
in the data, and use the correct string for that ID.