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)
Organizing/ structuring rule sets and rules
R

Hi guys,

Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.

Maybe there are better ways to organize my rule sets.

I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.

Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT

I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.

Screenshot 2025-04-06 201446.png

My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)

I have probably done something stupid or missed a step but I am stuck.

Thanks for any help.

Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M

Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?

Also the landing page after login is empty and seems be have some JS issues on the dev console:

Screenshot from 2025-04-07 18-06-19.png

fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png

Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)

br,
mgvra

Multi-System Reactor
Need help reducing false positive notifications
T

Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)

- name: "Washing Machine" state: > {% if states("sensor.washer_switch_0_power")|float == 0 %} Off {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} Standby {% else %} Washing {% endif %} icon: > {% if states("sensor.washer_switch_0_power") == "off" %} mdi:washing-machine-alert {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} mdi:washing-machine-off {% else %} mdi:washing-machine {% endif %} minutes: 2

The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.

6774565a-06cc-443f-99c1-e71301b33d83-image.png

What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.

The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.

What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.

I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?

Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0

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
Deleting widgets
tunnusT

Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266

Multi-System Reactor
MQTT configuration question
tunnusT

I have the following yaml configuration in local_mqtt_devices file

x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'

While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?

Multi-System Reactor
System Configuration Check - time is offset
F

Hi!

I get this message when I'm on the status tab:

System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.

I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1

I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan

Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT

I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.

While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.

So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.

While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits

Thanks!

Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N

Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945

Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.

I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.

This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.

x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}

The "cold white" and "warm white" settings interfer with the rgb color settings.

Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.

So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have

x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor

In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.

x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33

Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?

x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}

Thanks in advance.

Multi-System Reactor
Problem with simultaneous notifications.
T

Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.

I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.

96b3f7db-ba09-499e-a78c-86903b603857-image.png

36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.

Any idea what could be happening?

Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]

Multi-System Reactor
Problem after upgrading to 25067
R

MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.

Multi-System Reactor
Global expressions not always evaluated
tunnusT

Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.

Consider the following test case:

Screenshot 2025-03-13 at 16.29.42.png

Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.

Screenshot 2025-03-13 at 16.31.43.png

Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).

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] Runtime error when exiting global reaction that contains a group
S

I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.

The Runtime Error is different in the two browsers
Safari v18.3

@http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 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.

Google Chrome 133.0.6943.142

TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171: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.

Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.

I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.

Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks

Multi-System Reactor
Cannot delete Global Expressions
SnowmanS

I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.

I have not created a global expression for some times and just noticed this while doing some clean-up.

I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.

Here's what the log shows.

[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }

Reactor latest-25067-62e21a2d
Docker on Synology NAS

Multi-System Reactor
Local notification methods?
CatmanV2C

Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.

This was prompted by yesterday's fun and games with my ISP.

I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)

I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?

TIA

C

Multi-System Reactor
Custom capabilities in MQTT templates
M

Hi,
I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far.
But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter.

So this is what I have in the local_mqtt_devices.yaml

capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int

And this is the template:

templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json

So the speak action should send something like this to topic sonos/cmd/speak

{ "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" }

At startup the MSR seems to be quite unhappy with my configuration:

reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM

This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction.
Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable.

br,
mgvra

MSR latest-25016-d47fea38 / MQTTController [0.2.24293]

Multi-System Reactor
[SOLVED]Hass websocket falsely reporting ready on boot??
V

Hi, @toggledbits

I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting.

Here is the sequence of the test case (All time converted to Zulu to match logs):

Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI

From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error.

Here is what I see from the log:

14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready.

Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...).

Questions:

Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas?

Here is the log:

OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?

Multi-System Reactor
[SOLVED]Logs permissions for Docker Install
V

Not a big issue simply a request if easily doable.

The MSR logs files inside the container are owned by root witch is fine however, the permissions are very restrictive. I do not know if there is something wrong with my installation but the logs permission are set to 222 (write only). Even if the docker volume is set for Read/Write the log files are retaining these values.

I go around the problem by doing a chmod 777 on all reactor logs but every time there is an MSR log rotation the permissions are set back to 222. So unless the permission are implemented in the container there is no permanent solution to this (that I know of).

I do not know much about Docker container so I do not know what is involved here.

Can the logfiles permission be simply chaged in the container to at least allow "other" read permission?

Could the MSR log rotation routine implement a chmod to set the permission?

Just a small anoyance

Thanks

Multi-System Reactor

Need Some Help Using browser_mod (HA integration)

Scheduled Pinned Locked Moved Multi-System Reactor
26 Posts 2 Posters 2.2k 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

                      • Disaster recovery and virtualisation
                        CatmanV2C
                        CatmanV2
                        0
                        5
                        371
                      • Remote access of Zwave stick from Z-wave server
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        103
                      • Organizing/ structuring rule sets and rules
                        G
                        gwp1
                        0
                        5
                        142
                      • Moving MSR from a QNAP container to RP 5 - some issues
                        G
                        gwp1
                        0
                        5
                        127
                      • Widget deletion does not work and landing page (status) is empy
                        G
                        gwp1
                        0
                        4
                        118
                      • Need help reducing false positive notifications
                        T
                        tamorgen
                        0
                        7
                        233
                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        120
                        17.3k
                      • Deleting widgets
                        toggledbitsT
                        toggledbits
                        0
                        4
                        291
                      • MQTT configuration question
                        tunnusT
                        tunnus
                        0
                        11
                        304
                      • System Configuration Check - time is offset
                        G
                        gwp1
                        0
                        8
                        295
                      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