I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me.
While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users.
I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do.
Just an idea
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/dbochicchio/reactor-mqtt-contrib
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
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.
That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
Example: Light 1 ON → OFF, then Light 2 ON → OFF.
The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.
Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
Probably a really dumb question.
Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.
Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly.
Any thoughts?
Apologies if the ask is not clear/
TIA
C
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
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 foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page.
Once logged back in I can no longer remove errant panes nor is the + available to add new ones.
Brave Browser v1.80.122 (Jul 16, 2025)
What have I done?!
Will check other browsers on my M1.
UPDATE: Safari exhibits same behaviour.
I've tried both sans last-four public key entry and with - no change.
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded).
Get it at (install is similar to MQTTController and such):
https://github.com/dbochicchio/reactor-opensprinkler
Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty.
Since I've learnt a lot from this controller, I'll explore new controllers soon.
Good day all,
I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing.
I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container.
Has anyone done this? Any advice?
Need Some Help Using browser_mod (HA integration)
-
First, I can see that
targetis being passed correctly.According to their documentation, the
browser_idis 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_idandarea_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: 34ae76561192c4bb0b64fb07ad0f01c1But the
target: device_id: 34ae76561192c4bb0b64fb07ad0f01c1is not being passed through correctly and the popup shows up on all devices. I also have set thebrowser_idfor 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: 34ae76561192c4bb0b64fb07ad0f01c1Here 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_idindata -
Tried
browser_idno popup on any devices, useddevice_idand 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_idin 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_idis to be used, and (b) both the service data from the API and my testing confirm thatentity_idis 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_idis much shorter than a HAdevice_idby 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_idas atargetworks fine every time, and- if you don't include
browser_idin 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_servicein Reactor.
So you need to use
browser_idin the data, and use the correct string for that ID.
-
T toggledbits locked this topic on
