• Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
MSR UI on a mobile browser
tunnusT

I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.

Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.

( *Drag & drop of rule conditions have never worked on a mobile)

Multi-System Reactor
[Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment
therealdbT

Hi @toggledbits,

I have lots of logs with this:

<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignment

Any hints to where look at to avoid this? Thanks.

Multi-System Reactor
[Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types
therealdbT

Hi @toggledbits

I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.

Could you please elaborate more? Thanks.

Multi-System Reactor
Access to log file viewer denied
tunnusT

I have the following ACL defined:

groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true

And I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log

So what I'm missing, is my ACL incorrectly defined?

Using build 24302 on Docker.

Multi-System Reactor
Darker Reactor style
therealdbT

Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.

Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce

A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.

Multi-System Reactor
TTS in MSR?
F

Hi!

In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan

Multi-System Reactor
Should MSR import this device type from an Ezlo controller?
cw-kidC

Hi

I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

This is how that device looks in the Ezlo API.

Devices Info:

_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"

Items Info:

_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"

There is also an Analog Gas sensor that one did import in to MSR OK.

68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png

Devices Info:

_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"

Items Info:

_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"

And this is how this MQ2 Gas Sensor looks like on their dashboard:

Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png

Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png

They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

THANKS.

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

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

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

A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.

Local expressions cannot be deleted. Pushing the X button has no effect for me.

When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png

When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png

Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.

On the bright side:

I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!
Multi-System Reactor
Error on start for MSR after update to 24293
T

@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:

TypeError: Cannot read properties of undefined (reading 'value') at Rulesets.getRulesets (https://*************************/client/Rulesets.js:111:38) at async StatusTab.updateSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:276:28) at async StatusTab.drawSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:270:13) You may report this error, but do not screen shot it. Copy-paste the text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

I followed the new directions about npm

npm i --no-save --no-package-lock --omit dev

Any idea what the issue is?

Multi-System Reactor
Dark Mode not Working - 24293
PablaP

Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)

Things I have tried:

Hard refresh
Different browser
Different computer
Restarting Reactor

Failed troubleshooting attempts:

No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)

Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS

3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled

ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled

Multi-System Reactor
Is there a way to restart an add-on in HAAS from MSR?
T

Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.

What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?

Running:

Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]

HAAS:

RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Multi-System Reactor
Log files
wmarcolinW

Hi!

Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?

And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?

And being more ambitious, does Windget have an icon to open these TXT files in the navigated?

Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂

Multi-System Reactor
[Reactor] Services with sync response
therealdbT

Hi @toggledbits

I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.

I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.

Thanks.

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

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

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

Thanks in advance.

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

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

@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.

Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0

Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.

motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=null

Zooz ZSE18 Motion Sensor.jpg

Tilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.

tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null

TILT-ZWAVE2.5-ECO.jpg

Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT

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:

GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor

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 🙂

Multi-System Reactor

Need Some Help Using browser_mod (HA integration)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    You need to send browser_id in data

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

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

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

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

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

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

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

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

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

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

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

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

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

    1 Reply Last reply
    0
  • toggledbitsT toggledbits locked this topic

Recent Topics

  • G
    High temperature sensor for Zigbee
  • M
    MSR UI on a mobile browser
  • G
    New to Home Automation Looking for a Single app?
  • H
    UZB/RaZberry Firmwares - Update
  • therealdbT
    Sending data to a USB port to interface with a wireless switch
  • G
    Seeking Advice:
  • toggledbitsT
    [Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment
  • therealdbT
    [Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types
  • akbooerA
    Looking for Remote Switch boxes that can also be used with a wireless Decora Style Switch.
  • parkercP
    Openluup - verabridge can not load devices.
  • toggledbitsT
    Access to log file viewer denied
Powered by NodeBB | Contributors
Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved