Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Need Some Help Using browser_mod (HA integration)
Throttled problem
wmarcolinW

Hi @toggledbits

I found this very old post that talked about a way to limit device reading to avoid the throttled problem, because it's not a question of logic, it's that the device actually sends a lot of information, in my case the NUT ups installed in HE.

https://smarthome.community/topic/687/flapping-device?_=1737652139854

It mentions engine section of reactor.yaml by setting update_rate_limit, but I looked in the current MSR documentation and I can't find this information, so I don't know if it's still valid, its effect and parameters.

My situation is simple, when I have a UPS problem the NUT is sending dozens of reports per second and then I have the throttled problem. The same rule applies when the power is normal.

This is the rule, and the parameter that fails is the Tripp Lite UPS status.

cf9ddabf-3144-4e5a-80a4-0dc7664b9573-image.png

a813a077-974e-4737-897c-e383085b3d8f-image.png

All error is the same scenario.

[latest-25016]2025-01-23T12:01:32.753Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.756Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.769Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.772Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:32.776Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.780Z <Rule:WARN> UPS On Battery (rule-l4hjuka5 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling> [latest-25016]2025-01-23T12:01:32.781Z <Rule:WARN> UPS Info (rule-l4gheo63 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling... [latest-25016]2025-01-23T12:01:40.757Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.759Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:40.776Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.777Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:40.778Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott>

Thanks.

Multi-System Reactor
Dynamic Alert Based on Tripped Expression
T

Hello -

Long time. Hope everyone is good.

I have a rule that looks at a number of temperature sensors around the house. It simply sends a general alert if any of them fall below their threshold. (A basic “House is too cold” alert for when we’re away)

Generally, this has worked well. But I was wondering if there’s a way to make the message somewhat dynamic without creating separate rules for each sensor.

E.g. “House is too cold due to Sump Temperature below 45 degrees.”

I thought I remember reading about someone doing this in the past but couldn’t find it.

Thanks for any ideas!

Multi-System Reactor
latest-25016 toggle.toggle on VeraController Lock entity not working
CrilleC

After upgrade from 24366 to 25016 toggle on Vera (openLuup) lock entity doesn't seem to work.

VeraController log level 5
24366:

[latest-24366]2025-01-20T20:26:49.724Z <VeraController:INFO> VeraController#vera perform action toggle.toggle on Lock#vera>device_10016 with [Object]{ } [latest-24366]2025-01-20T20:26:49.725Z <VeraController:5:VeraController.js:514> [VeraController:verarequest] requesting http://127.0.0.1:3480/data_request?id=action&serviceId=urn%3Amicasaverde-com%3AserviceId%3ADoorLock1&action=SetTarget&newTargetValue=0&DeviceNum=10016&output_format=json&_r=1737404809725 ([Object]{ })

25016:

[latest-25016]2025-01-20T20:30:25.457Z <VeraController:INFO> VeraController#vera perform action toggle.toggle on Lock#vera>device_10016 with [Object]{ } [latest-25016]2025-01-20T20:30:25.458Z <VeraController:5:VeraController.js:1210> VeraController#vera no configured implementation for toggle.toggle on Lock#vera>device_10016; calling super [latest-25016]2025-01-20T20:30:25.458Z <VeraController:INFO> VeraController#vera perform action lock.set on Lock#vera>device_10016 with [Object]{ "state": false } [latest-25016]2025-01-20T20:30:25.461Z <VeraController:5:VeraController.js:1255> VeraController#vera sending action request [Object]{ "newTargetValue": "0", "DeviceNum": 10016, "id": "action", "serviceId": "urn:upnp-org:serviceId:DoorLock1", "action": "SetTarget" } [latest-25016]2025-01-20T20:30:25.461Z <VeraController:5:VeraController.js:515> [VeraController:verarequest] requesting http://127.0.0.1:3480/data_request?newTargetValue=0&DeviceNum=10016&id=action&serviceId=urn%3Aupnp-org%3AserviceId%3ADoorLock1&action=SetTarget&output_format=json&_r=1737405025461 ([Object]{ }) [latest-25016]2025-01-20T20:30:25.463Z <VeraController:NOTICE> VeraController#vera action lock.set([Object]{ "state": false }) on Lock#vera>device_10016 succeeded

I tried to log an issue in Mantis Bug Tracker but I can't log in anymore?

Multi-System Reactor
[Solved] Local expression evaluation
V

Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...

What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.

Any help would be appreciated

I have the following test rule:

eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png

2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png

Here is the expressioncode:

vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26  and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" end
Multi-System Reactor
[SOLVED] reactor_inet_check script... and containers
G

When on my bare metal RPi with MSR I had a rule that ran every minute to check Internet status via a script in MSR called reactor_inet_check.sh

I've moved to containerized MSR and see in the instructions that this cannot be run from the container.

The script cannot run within the Reactor docker container. If you are using Reactor in a docker container, the script needs to be run by cron or an equivalent facility on the host system (e.g. some systems, like Synology NAS, have separate task managers that may be used to schedule the repeated execution of tasks such as this).

I've put a script on my container host that calls the reator_inet_check.sh script and it isn't erroring... but I still see the internet status within MSR as null.

Before I go diving down the rabbit hole... should this work?

My cronjob on the proxmox host:
909fe6f0-77fd-4734-80a4-c9e354c910b6-image.png

The contents of msr_internet_check_caller.sh
16337528-cf31-4968-bffe-af1149f7103e-image.png

Multi-System Reactor
[Solved] Migrating MSR to Docker on Proxmox
G
Zero issues installing Proxmox on a new MiniPC. Zero issues migrating my HA instance over to the new hotness (I know, I was surprised, too!)

And then MSR...

My first issue: I'm logged into the msr CT as reactor (I used the suggested username just to keep things simple as this is new space for me and I was high off my success of migrating HA over).

When I run

docker pull toggledbits/reactor:latest-amd64

... it assigns the \reactor\ subdirectory where installed root ownership. I am absolutely logged in with the correct non-root user.
1c58aead-85ca-4b2c-8f48-c3d1f57d7fe3-image.png

Second issue: I copied over the following folders:
67e7e4a5-cee8-4de1-90c7-1df35f1070b9-image.png When MSR loads, all of my Global Expressions are missing.

Third issue:
All controllers connect wonderfully (Hubitat, etc)... except HA.
After changing ownership of the logs to reactor again I can see this when MSR calls HA:

[latest-24366]2025-01-12T00:03:43.128Z <HubitatController:INFO> HubitatController#hubitat successful connection to ws://192.168.1.214/eventsocket [latest-24366]2025-01-12T00:03:43.151Z <HubitatController:NOTICE> HubitatController#hubitat current mode is Evening (2) [latest-24366]2025-01-12T00:03:43.212Z <HubitatController:NOTICE> HubitatController#hubitat HSM status is disarmed [latest-24366]2025-01-12T00:03:43.214Z <Controller:NOTICE> Controller HubitatController#hubitat is now online. [latest-24366]2025-01-12T00:03:43.255Z <MQTTController:INFO> MQTTController#mqtt2 connected; opening subscriptions [latest-24366]2025-01-12T00:03:43.371Z <MQTTController:INFO> MQTTController#mqtt2 sending inits and going online! [latest-24366]2025-01-12T00:03:43.373Z <Controller:NOTICE> Controller MQTTController#mqtt2 is now online. [latest-24366]2025-01-12T00:03:47.179Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-] [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED [latest-24366]2025-01-12T00:03:47.180Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-] [latest-24366]2025-01-12T00:03:52.181Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-] [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED [latest-24366]2025-01-12T00:03:52.183Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]

Yes, I created a fresh new long-lived access token for the MSR containerized install and updated the reactor.yaml config file correctly.

Honestly, all-in-all, for my total lack of expertise here I'm very pleased that I only have these three issues. But they are def blockers atm.

My RPi bare metal install of MSR hooked right up to the new HA and is humming along just fine (I used hostnames were possible and shuffled some IPs in other places so I wouldn't run into things later that were mapped incorrectly that I'd forgotten about.)

Proxmox 8.3.2 MSR lives in an Ubuntu 24.04 Proxmox container MSR is latest docker version

What else can I provide to those smarter than me here?

Multi-System Reactor
Runtime error latest-24366 when Create New Reaction
B

Reactor (Multi-hub) latest-24366-3de60836
Running on Proxmox 8 VM
Ubuntu 22.04.5 LTS
Docker version 27.5.0, build a187fa5
Docker Compose version v2.32.3
Browsers being used on Mac OS Sequoia: Safari, Firefox also occurs with Safari on iPhone 16 Pro 18.2.1

This occurs on two different instances of MSR running at two different locations having the same environment detailed above.

When I select "Reactions->Create Reaction" I get an error window with a red “Runtime Error:” banner. Note that I can edit and save existing Reactions

—-------------------<SNIP>————————————
Runtime Error:

@http://192.168.119.137:8111/reactor/en-US/lib/js/reactor-ui-reactions.js:445:34

You may report this error, but do not screen shot it. Copy-paste the complete 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.
---------------------</SNIP>————————

apt update, apt upgrade, reboot have been performed as well as
docker system prune -a
docker compose down
docker compose up -d

Many thanks in advance,
-bh

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
Vera reload detected where there does not appear to be one.
CatmanV2C

I may have posted this in the wrong section. MSR running on Bare metal Debian bullseye. Both Openluup and MSR are on the same device (an Intel NUC) at IP 192.168.70.249. Any suggestions as to where I go to resolve?

TIA

Happy new year, everyone! Hope all are well!

Looking for some pointers troubleshooting a slightly puzzling to me issue. When digging around on a different issue I noticed this happening regularly in the MSR logs:

[latest-24366]2025-01-10T19:50:07.630Z <Engine:NOTICE> Starting reaction Garden lights on when the doors are open<SET> (rule-lb2h69nb:S) [latest-24366]2025-01-10T19:50:07.630Z <VeraController:INFO> VeraController#vera perform action power_switch.on on Switch#vera>device_20060 with [Object]{ } [latest-24366]2025-01-10T19:50:07.630Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20060 with [Object]{ "state": true } [latest-24366]2025-01-10T19:50:07.670Z <VeraController:NOTICE> VeraController#vera action power_switch.set([Object]{ "state": true }) on Switch#vera>device_20060 succeeded [latest-24366]2025-01-10T19:50:07.671Z <Engine:INFO> Resuming reaction Garden lights on when the doors are open<SET> (rule-lb2h69nb:S) from step 1 [latest-24366]2025-01-10T19:50:07.672Z <Engine:NOTICE> Garden lights on when the doors are open<SET> delaying until 1736538787672<10/01/2025, 19:53:07> [latest-24366]2025-01-10T19:50:19.595Z <Rule:INFO> Garden lights on when the doors are open (rule-lb2h69nb in Outside Lights) evaluated; rule state transition from SET to RESET! [latest-24366]2025-01-10T19:52:16.506Z <Rule:INFO> Garden lights on when the doors are open (rule-lb2h69nb in Outside Lights) evaluated; rule state transition from RESET to SET! [latest-24366]2025-01-10T19:52:16.515Z <Engine:INFO> [Engine]Engine#1 not enqueueing rule-lb2h69nb:S: already in queue with status 2 [latest-24366]2025-01-10T19:52:20.823Z <Rule:INFO> Garden lights on when the doors are open (rule-lb2h69nb in Outside Lights) evaluated; rule state transition from SET to RESET! [latest-24366]2025-01-10T19:53:07.676Z <Engine:INFO> Resuming reaction Garden lights on when the doors are open<SET> (rule-lb2h69nb:S) from step 2 [latest-24366]2025-01-10T19:53:07.677Z <VeraController:INFO> VeraController#vera perform action power_switch.off on Switch#vera>device_20060 with [Object]{ } [latest-24366]2025-01-10T19:53:07.678Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20060 with [Object]{ "state": false } [latest-24366]2025-01-10T19:53:07.719Z <VeraController:NOTICE> VeraController#vera action power_switch.set([Object]{ "state": false }) on Switch#vera>device_20060 succeeded [latest-24366]2025-01-10T19:53:07.720Z <Engine:INFO> Resuming reaction Garden lights on when the doors are open<SET> (rule-lb2h69nb:S) from step 3 [latest-24366]2025-01-10T19:53:07.721Z <Engine:INFO> Garden lights on when the doors are open<SET> all actions completed. [latest-24366]2025-01-10T19:55:04.468Z <VeraController:ERR> VeraController#vera update request failed: [FetchError] network timeout at: http://192.168.70.249:3480/data_request?id=status&Timeout=15&DataVersion=416912953&MinimumDelay=50&output_format=json&_r=1736538886459 [-] [latest-24366]2025-01-10T19:55:09.646Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20050: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20050) [-] [latest-24366]2025-01-10T19:55:09.646Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.646Z <VeraController:CRIT> *Entity#vera>device_20050 [latest-24366]2025-01-10T19:55:09.656Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20570: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20570) [-] [latest-24366]2025-01-10T19:55:09.656Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.656Z <VeraController:CRIT> *Entity#vera>device_20570 [latest-24366]2025-01-10T19:55:09.678Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20610: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20610) [-] [latest-24366]2025-01-10T19:55:09.679Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.679Z <VeraController:CRIT> *Entity#vera>device_20610 [latest-24366]2025-01-10T19:55:09.744Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20631: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20631) [-] [latest-24366]2025-01-10T19:55:09.744Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.744Z <VeraController:CRIT> *Entity#vera>device_20631 [latest-24366]2025-01-10T19:55:09.889Z <VeraController:NOTICE> VeraController#vera reload detected! [latest-24366]2025-01-10T19:55:09.910Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20050: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20050) [-] [latest-24366]2025-01-10T19:55:09.910Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.910Z <VeraController:CRIT> *Entity#vera>device_20050 [latest-24366]2025-01-10T19:55:09.935Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20570: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20570) [-] [latest-24366]2025-01-10T19:55:09.936Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.936Z <VeraController:CRIT> *Entity#vera>device_20570 [latest-24366]2025-01-10T19:55:09.937Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20610: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20610) [-] [latest-24366]2025-01-10T19:55:09.937Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.937Z <VeraController:CRIT> *Entity#vera>device_20610 [latest-24366]2025-01-10T19:55:09.939Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20631: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20631) [-] [latest-24366]2025-01-10T19:55:09.939Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.939Z <VeraController:CRIT> *Entity#vera>device_20631 [latest-24366]2025-01-10T19:55:09.968Z <Controller:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-24366]2025-01-10T19:55:10.037Z <VeraController:NOTICE> VeraController#vera reload detected!

That repeats until something like this:

[latest-24366]2025-01-10T19:55:10.049Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20050: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20050) [-] [latest-24366]2025-01-10T19:55:10.049Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:10.049Z <VeraController:CRIT> *Entity#vera>device_20050 [latest-24366]2025-01-10T19:55:10.053Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20570: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20570) [-] [latest-24366]2025-01-10T19:55:10.053Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:10.053Z <VeraController:CRIT> *Entity#vera>device_20570 [latest-24366]2025-01-10T19:55:10.062Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20610: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20610) [-] [latest-24366]2025-01-10T19:55:10.062Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:10.062Z <VeraController:CRIT> *Entity#vera>device_20610 [latest-24366]2025-01-10T19:55:10.112Z <VeraController:WARN> VeraController#vera failed to apply attribute scene_activation.scene_id to Entity#vera>device_20631: [TypeError] Can't set NaN on attribute scene_activation.scene_id (vera>device_20631) [-] [latest-24366]2025-01-10T19:55:10.112Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:10.113Z <VeraController:CRIT> *Entity#vera>device_20631 [latest-24366]2025-01-10T20:00:05.003Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "10/01/2025 20:00:05" (TZ offset 0 mins from UTC) [latest-24366]2025-01-10T20:13:51.872Z <Rule:INFO> No motion in Cinema (rule-m4ocglke in Cinema Environment) evaluated; rule state transition from SET to RESET! [latest-24366]2025-01-10T20:13:51.882Z <Rule:INFO> Cinema Heater On (rule-m4ocf1di in Cinema Environment) evaluated; rule state transition from RESET to SET! [latest-24366]2025-01-10T20:13:51.888Z <Engine:INFO> Enqueueing "Cinema Heater On<SET>" (rule-m4ocf1di:S)

And the errors / reloads just stop.

From Openluup:

2025-01-10 19:49:56.379 luup_log:63: BroadLink_Mk2 debug: RM3 Mini - IR 1: urn:schemas-micasaverde-com:device:IrTransmitter:1 2025-01-10 19:50:00.085 luup_log:0: 14Mb, 1.7%cpu, 36.1days 2025-01-10 19:50:07.591 luup.variable_set:: 20160.urn:micasaverde-com:serviceId:EnergyMetering1.KWH was: 18.6793008 now: 18.6805008 #hooks:0 2025-01-10 19:50:07.591 luup.variable_set:: 20160.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1736538000 now: 1736538600 #hooks:0 2025-01-10 19:50:07.591 luup.variable_set:: 20160.urn:micasaverde-com:serviceId:EnergyMetering1.Watts was: 7.4 now: 7.3 #hooks:0 2025-01-10 19:50:07.591 luup.variable_set:: 20170.urn:micasaverde-com:serviceId:EnergyMetering1.KWH was: 32.2417984 now: 32.2470016 #hooks:0 2025-01-10 19:50:07.591 luup.variable_set:: 20170.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1736538000 now: 1736538600 #hooks:0 2025-01-10 19:50:07.591 luup.variable_set:: 20330.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1736538000 now: 1736538600 #hooks:0 2025-01-10 19:50:07.592 luup.variable_set:: 20770.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:0 2025-01-10 19:50:07.592 luup.variable_set:: 20770.urn:micasaverde-com:serviceId:SecuritySensor1.LastTrip was: 1736534850 now: 1736538607 #hooks:0 2025-01-10 19:50:07.593 openLuup.server:: request completed (3392 bytes, 1 chunks, 12875 ms) tcp{client}: 0x55c3299a9cf8 2025-01-10 19:50:07.618 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c3299a9cf8 2025-01-10 19:50:07.624 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c329d0a5b8 2025-01-10 19:50:07.624 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912906&MinimumDelay=50&output_format=json&_r=1736538607623 HTTP/1.1 tcp{client}: 0x55c329d0a5b8 2025-01-10 19:50:07.632 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c3292ed678 2025-01-10 19:50:07.633 openLuup.server:: GET /data_request?newTargetValue=1&DeviceNum=20060&id=action&serviceId=urn%3Aupnp-org%3AserviceId%3ASwitchPower1&action=SetTarget&output_format=json&_r=1736538607631 HTTP/1.1 tcp{client}: 0x55c3 292ed678 2025-01-10 19:50:07.633 luup.call_action:: 20060.urn:upnp-org:serviceId:SwitchPower1.SetTarget 2025-01-10 19:50:07.633 luup.call_action:: action will be handled by parent: 37 2025-01-10 19:50:07.633 luup.variable_set:: 20060.urn:upnp-org:serviceId:SwitchPower1.Target was: 0 now: 1 #hooks:0 2025-01-10 19:50:07.669 openLuup.server:: request completed (35 bytes, 1 chunks, 35 ms) tcp{client}: 0x55c3292ed678 2025-01-10 19:50:07.673 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c3292ed678 2025-01-10 19:50:07.776 openLuup.server:: request completed (821 bytes, 1 chunks, 151 ms) tcp{client}: 0x55c329d0a5b8 2025-01-10 19:50:07.784 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c329d0a5b8 2025-01-10 19:50:07.795 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c3287bc8f8 2025-01-10 19:50:07.796 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912907&MinimumDelay=50&output_format=json&_r=1736538607794 HTTP/1.1 tcp{client}: 0x55c3287bc8f8 2025-01-10 19:50:08.644 luup.variable_set:: 20060.urn:upnp-org:serviceId:SwitchPower1.Status was: 0 now: 1 #hooks:0 2025-01-10 19:50:08.950 openLuup.server:: request completed (821 bytes, 1 chunks, 1154 ms) tcp{client}: 0x55c3287bc8f8 2025-01-10 19:50:08.958 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c3287bc8f8 2025-01-10 19:50:08.969 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c3297e95a8 2025-01-10 19:50:08.970 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912908&MinimumDelay=50&output_format=json&_r=1736538608969 HTTP/1.1 tcp{client}: 0x55c3297e95a8 2025-01-10 19:50:19.181 luup.variable_set:: 20770.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 1 now: 0 #hooks:0 2025-01-10 19:50:19.585 openLuup.server:: request completed (832 bytes, 1 chunks, 10615 ms) tcp{client}: 0x55c3297e95a8 2025-01-10 19:50:19.602 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c3297e95a8 2025-01-10 19:50:19.605 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c328d298a8 2025-01-10 19:50:19.605 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912909&MinimumDelay=50&output_format=json&_r=1736538619604 HTTP/1.1 tcp{client}: 0x55c328d298a8 2025-01-10 19:50:34.950 openLuup.server:: request completed (593 bytes, 1 chunks, 15344 ms) tcp{client}: 0x55c328d298a8 2025-01-10 19:50:34.953 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c328d298a8 2025-01-10 19:50:34.965 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c328c48a58 2025-01-10 19:50:34.966 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912909&MinimumDelay=50&output_format=json&_r=1736538634964 HTTP/1.1 tcp{client}: 0x55c328c48a58 2025-01-10 19:50:34.989 luup.variable_set:: 25019.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:0 2025-01-10 19:50:34.990 luup.variable_set:: 25019.urn:micasaverde-com:serviceId:SecuritySensor1.LastTrip was: 1736534437 now: 1736538634 #hooks:0 2025-01-10 19:50:35.094 openLuup.server:: request completed (975 bytes, 1 chunks, 127 ms) tcp{client}: 0x55c328c48a58 2025-01-10 19:50:35.101 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c328c48a58 2025-01-10 19:50:35.113 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c32985e298 2025-01-10 19:50:35.113 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912911&MinimumDelay=50&output_format=json&_r=1736538635111 HTTP/1.1 tcp{client}: 0x55c32985e298 2025-01-10 19:50:40.255 luup.variable_set:: 25021.urn:micasaverde-com:serviceId:LightSensor1.CurrentLevel was: 0 now: 30 #hooks:1 2025-01-10 19:50:40.256 scheduler.watch_callback:: 25021.urn:micasaverde-com:serviceId:LightSensor1.CurrentLevel called [20]DataWatcherCallback() function: 0x55c3288a8d20 2025-01-10 19:50:40.460 openLuup.server:: request completed (835 bytes, 1 chunks, 5346 ms) tcp{client}: 0x55c32985e298 2025-01-10 19:50:40.472 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c32985e298 2025-01-10 19:50:40.478 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c329b28238 2025-01-10 19:50:40.479 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912912&MinimumDelay=50&output_format=json&_r=1736538640478 HTTP/1.1 tcp{client}: 0x55c329b28238 2025-01-10 19:50:44.471 luup.variable_set:: 25007.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:1 2025-01-10 19:50:44.472 luup.variable_set:: 25007.urn:micasaverde-com:serviceId:SecuritySensor1.LastTrip was: 1736538400 now: 1736538644 #hooks:0 2025-01-10 19:50:44.472 scheduler.watch_callback:: 25007.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped called [20]DataWatcherCallback() function: 0x55c3288a8d20 2025-01-10 19:50:44.775 openLuup.server:: request completed (975 bytes, 1 chunks, 4296 ms) tcp{client}: 0x55c329b28238 2025-01-10 19:50:44.775 openLuup.server:: request completed (975 bytes, 1 chunks, 4296 ms) tcp{client}: 0x55c329b28238 2025-01-10 19:50:44.782 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c329b28238 2025-01-10 19:50:44.793 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c328f1e968 2025-01-10 19:50:44.793 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912914&MinimumDelay=50&output_format=json&_r=1736538644791 HTTP/1.1 tcp{client}: 0x55c328f1e968 2025-01-10 19:51:00.122 openLuup.server:: request completed (593 bytes, 1 chunks, 15328 ms) tcp{client}: 0x55c328f1e968 2025-01-10 19:51:00.125 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c328f1e968 2025-01-10 19:51:00.136 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c32995b318 2025-01-10 19:51:00.136 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912914&MinimumDelay=50&output_format=json&_r=1736538660134 HTTP/1.1 tcp{client}: 0x55c32995b318 2025-01-10 19:51:15.481 openLuup.server:: request completed (593 bytes, 1 chunks, 15344 ms) tcp{client}: 0x55c32995b318 2025-01-10 19:51:15.484 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c32995b318 2025-01-10 19:51:15.495 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c32998b068 2025-01-10 19:51:15.497 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912914&MinimumDelay=50&output_format=json&_r=1736538675493 HTTP/1.1 tcp{client}: 0x55c32998b068 2025-01-10 19:51:30.869 openLuup.server:: request completed (593 bytes, 1 chunks, 15371 ms) tcp{client}: 0x55c32998b068 2025-01-10 19:51:30.872 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c32998b068 2025-01-10 19:51:30.884 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c32905bda8 2025-01-10 19:51:30.885 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912914&MinimumDelay=50&output_format=json&_r=1736538690882 HTTP/1.1 tcp{client}: 0x55c32905bda8 2025-01-10 19:51:32.886 luup.variable_set:: 20380.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 21 now: 22 #hooks:0 2025-01-10 19:51:33.090 openLuup.server:: request completed (841 bytes, 1 chunks, 2205 ms) tcp{client}: 0x55c32905bda8 2025-01-10 19:51:33.100 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c32905bda8 2025-01-10 19:51:33.112 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c328de0d58 2025-01-10 19:51:33.112 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912915&MinimumDelay=50&output_format=json&_r=1736538693111 HTTP/1.1 tcp{client}: 0x55c328de0d58 2025-01-10 19:51:36.064 luup.variable_set:: 25007.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 1 now: 0 #hooks:1 2025-01-10 19:51:36.065 scheduler.watch_callback:: 25007.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped called [20]DataWatcherCallback() function: 0x55c3288a8d20 2025-01-10 19:51:36.369 openLuup.server:: request completed (832 bytes, 1 chunks, 3256 ms) tcp{client}: 0x55c328de0d58 2025-01-10 19:51:36.377 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c328de0d58 2025-01-10 19:51:36.387 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c329054188 2025-01-10 19:51:36.388 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912916&MinimumDelay=50&output_format=json&_r=1736538696386 HTTP/1.1 tcp{client}: 0x55c329054188 2025-01-10 19:51:37.134 luup.variable_set:: 20380.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 22 now: 21 #hooks:0 2025-01-10 19:51:37.540 openLuup.server:: request completed (841 bytes, 1 chunks, 1152 ms) tcp{client}: 0x55c329054188 2025-01-10 19:51:37.553 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c329054188 2025-01-10 19:51:37.566 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c328d97568 2025-01-10 19:51:37.566 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912917&MinimumDelay=50&output_format=json&_r=1736538697564 HTTP/1.1 tcp{client}: 0x55c328d97568 2025-01-10 19:51:41.367 luup.variable_set:: 20380.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 21 now: 22 #hooks:0 2025-01-10 19:51:41.874 openLuup.server:: request completed (841 bytes, 1 chunks, 4307 ms) tcp{client}: 0x55c328d97568 2025-01-10 19:51:41.884 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c328d97568 2025-01-10 19:51:41.895 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c329385678 2025-01-10 19:51:41.896 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912918&MinimumDelay=50&output_format=json&_r=1736538701894 HTTP/1.1 tcp{client}: 0x55c329385678 2025-01-10 19:51:57.168 openLuup.server:: request completed (593 bytes, 1 chunks, 15272 ms) tcp{client}: 0x55c329385678 2025-01-10 19:51:57.171 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c329385678 2025-01-10 19:51:57.183 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c329b092b8 2025-01-10 19:51:57.184 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912918&MinimumDelay=50&output_format=json&_r=1736538717182 HTTP/1.1 tcp{client}: 0x55c329b092b8 2025-01-10 19:52:00.124 luup_log:0: 14Mb, 1.6%cpu, 36.1days 2025-01-10 19:52:00.476 openLuup.server:: request completed (1841 bytes, 1 chunks, 3292 ms) tcp{client}: 0x55c329b092b8 2025-01-10 19:52:00.483 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c329b092b8 2025-01-10 19:52:00.495 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c3297be088 2025-01-10 19:52:00.495 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912929&MinimumDelay=50&output_format=json&_r=1736538720494 HTTP/1.1 tcp{client}: 0x55c3297be088 2025-01-10 19:52:09.867 luup.variable_set:: 25021.urn:micasaverde-com:serviceId:LightSensor1.CurrentLevel was: 30 now: 0 #hooks:1 2025-01-10 19:52:09.868 scheduler.watch_callback:: 25021.urn:micasaverde-com:serviceId:LightSensor1.CurrentLevel called [20]DataWatcherCallback() function: 0x55c3288a8d20 2025-01-10 19:52:10.071 openLuup.server:: request completed (834 bytes, 1 chunks, 9575 ms) tcp{client}: 0x55c3297be088 2025-01-10 19:52:10.079 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c3297be088 2025-01-10 19:52:10.088 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c329c16a08 2025-01-10 19:52:10.089 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=416912930&MinimumDelay=50&output_format=json&_r=1736538730087 HTTP/1.1 tcp{client}: 0x55c329c16a08 2025-01-10 19:52:16.194 luup.variable_set:: 20770.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:0 2025-01-10 19:52:16.195 luup.variable_set:: 20770.urn:micasaverde-com:serviceId:SecuritySensor1.LastTrip was: 1736538607 now: 1736538736 #hooks:0 2025-01-10 19:52:16.498 openLuup.server:: request completed (976 bytes, 1 chunks, 6409 ms) tcp{client}: 0x55c329c16a08 2025-01-10 19:52:16.515 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55c329c16a08 2025-01-10 19:52:16.516 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x55c328dbad18

Nothing I can see indicating that Openluup is reloading?

.249 IP address is the internal IP of the NUC that hosts both Openluup and MSR.

Any thoughts as to how I can troubleshoot this? It's not a big deal, but would like to get to the bottom of it.

I should add that all the devices listed in entries like this:

[latest-24366]2025-01-10T19:55:09.744Z <VeraController:INFO> VeraController#vera class scene_controller meta [Object]{ "source": "urn:micasaverde-com:serviceId:SceneController1/sl_SceneActivated", "expr": "int(value)" } orig final NaN [latest-24366]2025-01-10T19:55:09.744Z <VeraController:CRIT> *Entity#vera>device_20631

Are the tamper switches on Fibaro FGMS001 multifunction detectors, of which I have 4, and they correspond exactly to the devices listed.

TIA

C

Multi-System Reactor
Has something changed with the "Changes" operator in Constraint groups ?
cw-kidC

Hi

I was looking at an old rule and I wanted to edit it, to add another Constraint, however I cannot seem to do it.

On this screen shot you can see an existing entry in the Constraints and on its pull down menu the "Changes" option is available.

09735de3-8e92-4e12-bfa2-5191f48924a7-image.png

However on the new line I just added I have no changes option in its pull down menu.

d85c4067-880e-4281-a12b-dac4d316a4da-image.png

Here is the original now locked post about this topic.

https://smarthome.community/topic/395/contact-sensor-opened-1-minute-ago-how?_=1736354690742

If you look on the old screen shots on that post, I was using the "changes" operator. Like this:

a1262e01-d3fd-4723-872f-872f1f6d9899-image.png

However today when I edited this rule the operators are showing as == and not as changes on all the entries in the Constraints area.

Also the old entries now say -- and the value is blank. But on the new line I just added it says that is not valid, so not sure how the old lines are like that.
a458d52d-214d-4862-a2b7-d31009f89cde-image.png

So I am a bit confused what happened.

Thanks

Multi-System Reactor
Reactor-Editor / Reactor-ui-Status Errors
SnowmanS

@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.

I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.

I see these errors on the following browsers:

Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big Sur

Here are the errors

Safari while creating/updating an expression

@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040

DuckDuckGo while clicking on status

http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44

Firefox while updating a rule

@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58

Chrome while creating/updating an expression

TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``
Multi-System Reactor
[Solved] Error dialog running reaction in build 24302
V

Not sure that it is the same issue but just got this on built 24302 when running a reaction for testing purpose. Despite the error message, the reaction ran properly.

Error: Command timeout (195 start_reaction)
at _ClientAPI._commandTimeout (http://192.168.2.163:8111/client/ClientAPI.js:552:136)

1a3422eb-d760-4609-a740-a40d04a6bab2-Screenshot 2024-12-29 231851.png

Multi-System Reactor
every X days field uneditable
G

Wasn't able to create a Mantis ticket on this.

Attempted to add a month range to a ruleset and it seems the first field every X days is not editable. The rest are fine.

msr_field_unselectable.png

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
Which user to install nodejs as ? Debian Linux
cw-kidC

Hi

Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.

I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.

I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?

I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.

But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?

So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.

This is how I installed nodejs as whilst logged in as root

ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png

Thanks in advance.

Multi-System Reactor
OpenAI Controller for Reactor
therealdbT

As the title says, here's my OpenAI Controller for Reactor:

GitHub - dbochicchio/reactor-openai: OpenAI Controller per Reactor GitHub - dbochicchio/reactor-openai: OpenAI Controller per Reactor

OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.

It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.

- id: openai name: OpenAI implementation: OpenAIController enabled: true config: models: - id: openai name: OpenAI GPT-4 model: gpt-4 service: openai api_key: xxxxx # taken from your OpenAI dashboard max_tokens: 2000 # default temperature: 0.5 # default top_p: 1 # default frequency_penalty: 0 # default presence_penalty: 0 # default stop: null # default - id: azure name: Azure GPT-4 model: gpt-4 service: azure endpoint: "https://XXX.openai.azure.com/openai/deployments/gpt-4o/chat/completions?api-version=2023-03-15-preview" # taken from your Azure GPT-4 service api_key: xxxx # taken from Azure max_tokens: 2000 # default temperature: "0.5" # default top_p: 1 # default frequency_penalty: 0 # default presence_penalty: 0 # default stop: null # default

It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).

9013ae50-fd68-42a2-87c3-97479132e465-image.png

80a88eec-7c89-464a-8196-690b4b72d044-image.png

Have fun with LLM into your scenes!

Multi-System Reactor
Thanksgiving lighting took a holiday
G

18481340-4d9c-4d0c-8027-49adfa28f32a-image.png

e0e1c895-a830-48d5-8346-cbae551b441d-image.png

This has been working flawlessly each year incl this year until... Tonight... nada.

Is this due to the holiday being late this year ie because today is the 22nd, not after the 22nd?

Multi-System Reactor
Reference error - null object
tunnusT

In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.

Screenshot 2024-11-28 at 22.20.41.png

And the expression is

Screenshot 2024-11-28 at 22.38.19.png

Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.

Multi-System Reactor
Trouble Configuring Multi-System Reactor Logic Across Devices
G

Hello

I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:

-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.

Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.

Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.

Thank you !

Multi-System Reactor
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

Need Some Help Using browser_mod (HA integration)

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

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

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

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

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

      

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

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

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

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

          So it looks like the ZIP file worked this time

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

                You need to send browser_id in data

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

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

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

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

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

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

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

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

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

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

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

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

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

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits locked this topic on

                      Recent Topics

                      • Throttled problem
                        wmarcolinW
                        wmarcolin
                        0
                        1
                        5
                      • Dynamic Alert Based on Tripped Expression
                        T
                        tbully
                        0
                        3
                        32
                      • latest-25016 toggle.toggle on VeraController Lock entity not working
                        CrilleC
                        Crille
                        0
                        6
                        47
                      • [Solved] Local expression evaluation
                        V
                        vezinpi
                        0
                        7
                        45
                      • Hello and first network question
                        D
                        Dr Paul
                        1
                        8
                        158
                      • [SOLVED] reactor_inet_check script... and containers
                        G
                        gwp1
                        0
                        8
                        121
                      • Apple Home Automation Issue
                        CatmanV2C
                        CatmanV2
                        1
                        2
                        33
                      • Migration Vera to HA > how to send sensor data from Vera to HA?
                        M
                        Maipensato
                        0
                        7
                        128
                      • [Solved] Migrating MSR to Docker on Proxmox
                        G
                        gwp1
                        0
                        12
                        184
                      • Runtime error latest-24366 when Create New Reaction
                        B
                        basai
                        0
                        6
                        62
                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        116
                        15.8k
                      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