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.
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.
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
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)
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
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
I have the following 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?
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
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!
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: currentColorIn 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=33Is 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.
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]
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.
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?).
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" endI 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
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
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
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
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: intAnd 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: jsonSo 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 AMThis 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]
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 GUIFrom 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?
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
[Dev] Inheritance in MQTT templates?
-
That's probably more appropriate to post on Mantis for @toggledbits, but since I know there's at least @Crille publishing templates, my intent with this post is to open a broader discussion.
Long story short: I'm starting to slowly add new template for Shelly Plus and I noticed I'll end up with a dozen more templates, all similar but simply different in trivial details, all sharing a large amount of code and all needing special cares when fixing bugs/adding features (as the latest wifi_status addition).
So, I'm wondering if it's time to start thinking of some sort of inheritance in templates, where I could just create a generic shelly_gen1 and use it as a base for shelly_relay, and this be used as the base for shelly_relay_power and so on.
I could probably achieve this with some sort of scripting on my side to generate templates via code, but maybe there's a better way of doing this, or it's already on the radar.
-
Sounds great!
I thought of something like this when creating templates for combined humidity & temperature sensors where I in some locations want humidity as primary attribute and other temperature, this generates duplicate templates bundled in the same file and the only difference is theprimary_attributeor is this doable with therequires:key already?Base files for devices using the same keys would ease things up and could simply be included in a bundled zip file.
-
It's already done. Great minds think alike. I did it a couple of weeks ago, haven't released it yet. I also broke things out so that the templates can be spread out across any kind of directory structure you want to create.
I'll push it up for you.
-
@toggledbits Thanks for the quick build. I've updated to the latest version of MQTTController and I'll soon update my templates. I've found a minor problem related to custom capabilities.
In previous iteration, it was tolerated, but now it's emitting an arror (
Configuration for X is incomplete because the following requested capabilities are unrecognized: Y).Is there a way to define and pack definitions of capabilities with custom templates? Otherwise, I'll have to find an alternative way for my
shelly_hem.yaml, because I must expose 2 energy sensors in one device (one for imported, the other for exported KwH). Thanks. -
What is/are the capabilties?
-
it's a custom one, just to have two values:
https://github.com/dbochicchio/reactor-mqtt-contrib/blob/main/shelly_hem.yaml#L59-L63 -
Yes, yes, I've already looked at the definition in Github, I need you to be more specific. What are the names you redacted at Y in your previous post.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits oh, my bad. I'll try to re-pro again when home, but it should be
x_energy_sensor_exportedfor Y and the device name for X. -
OK. That helps. And problem understood. I think I have an answer. New build later today.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
OK. MQTTController build 24144 up. Adds support for a
capabilitiessection at the top level of any template file. Format is same as for system_capabilities.yaml. See MQTTController docs, updated.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Ok, version 24146 of my templates is now ready, refactored with this new feature and starting to include Shelly Gen 3 (I've also used a couple of system templates as base).
The only minor thing is that if I have a primary_attribute defined in a template, MQTTController will not use the last one in the hierarchy, but the first one, and complain. Maybe just a brief note on the docs to highlight this.
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Thanks!
-
Quick question, looking at MQTTController integrated templates for Shelly, they are in separate files. Is it possible to define all these in one yaml file? Because I'm trying to do that for common Zigbee2MQTT capabilities and getting errors in the log that I can't figure out why. If not possible I get it but if it is possible I will elaborate my issue.
-
Yes, it's possible.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
OK, here goes.
[1/2]
Reactor latest-24152 bare metal.
MQTTController 24144.I can't figure this out
"MQTTController:CRIT ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>sovrumsdorr [-]"reactor.log[latest-24152]2024-06-05T20:20:25.153Z <app:null> Reactor build latest-24152-3455578a starting on v20.13.1 /usr/local/bin/node [latest-24152]2024-06-05T20:20:25.153Z <app:null> Process ID 317180 user/group 1000/1000; bare-metal; platform linux/x64 #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024; locale sv_SE.utf8 [latest-24152]2024-06-05T20:20:25.154Z <app:null> Basedir /home/homebridge/reactor; data in /home/homebridge/reactor/storage [latest-24152]2024-06-05T20:20:25.154Z <app:null> NODE_PATH=/home/homebridge/reactor [latest-24152]2024-06-05T20:20:25.169Z <app:null> Resolved timezone=Europe/Stockholm, environment TZ=(undefined); offset minutes from UTC=120 [latest-24152]2024-06-05T20:20:25.171Z <app:null> Configured locale sv-SE; selected locale(s) sv-SE [latest-24152]2024-06-05T20:20:25.177Z <app:null> Loaded locale sv-SE for sv-SE [latest-24152]2024-06-05T20:20:25.178Z <app:null> Local date/time using configured timezone and locale formatting is "2024-06-05 22:20:25" [latest-24152]2024-06-05T20:20:25.180Z <Structure:null> Module Structure v24110 [latest-24152]2024-06-05T20:20:25.181Z <Capabilities:null> Module Capabilities v23331 [latest-24152]2024-06-05T20:20:25.191Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 24108 revision 1 [latest-24152]2024-06-05T20:20:25.197Z <Plugin:null> Module Plugin v22300 [latest-24152]2024-06-05T20:20:25.214Z <TimerBroker:null> Module TimerBroker v22283 [latest-24152]2024-06-05T20:20:25.216Z <Entity:null> Module Entity v24138 [latest-24152]2024-06-05T20:20:25.218Z <Controller:null> Module Controller v24099 [latest-24152]2024-06-05T20:20:25.232Z <default:null> Module Ruleset v24099 [latest-24152]2024-06-05T20:20:25.232Z <default:null> Module Rulesets v24099 [latest-24152]2024-06-05T20:20:25.250Z <GlobalExpression:null> Module GlobalExpression v24099 [latest-24152]2024-06-05T20:20:25.275Z <Predicate:null> Module Predicate v23093 [latest-24152]2024-06-05T20:20:25.277Z <AlertManager:null> Module AlertManager v24099 [latest-24152]2024-06-05T20:20:25.278Z <Rule:null> Module Rule v24149 [latest-24152]2024-06-05T20:20:25.280Z <GlobalReaction:null> Module GlobalReaction v24099 [latest-24152]2024-06-05T20:20:25.289Z <Engine:null> Module Engine v24113 [latest-24152]2024-06-05T20:20:25.292Z <httpapi:null> Module httpapi v24148 [latest-24152]2024-06-05T20:20:25.298Z <wsapi:null> Module wsapi v24148 [latest-24152]2024-06-05T20:20:25.299Z <app:NOTICE> Starting Structure... [latest-24152]2024-06-05T20:20:25.308Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-24152]2024-06-05T20:20:25.331Z <TaskQueue:null> Module TaskQueue 24138 [latest-24152]2024-06-05T20:20:25.332Z <VeraController:null> Module VeraController v24050 [latest-24152]2024-06-05T20:20:25.375Z <Structure:INFO> Structure#1 loading controller interface ezlo (EzloController) [latest-24152]2024-06-05T20:20:25.381Z <EzloController:null> Module EzloController v23345 [latest-24152]2024-06-05T20:20:25.384Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-24152]2024-06-05T20:20:25.386Z <DynamicGroupController:null> Module DynamicGroupController v24128 [latest-24152]2024-06-05T20:20:25.390Z <Structure:INFO> Structure#1 loading controller interface virtual (VirtualEntityController) [latest-24152]2024-06-05T20:20:25.393Z <VirtualEntityController:null> Module VirtualEntityController v24147 [latest-24152]2024-06-05T20:20:25.395Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-24152]2024-06-05T20:20:25.399Z <HassController:null> Module HassController v24146 [latest-24152]2024-06-05T20:20:25.450Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-24152]2024-06-05T20:20:25.452Z <SystemController:null> Module SystemController v24076 [latest-24152]2024-06-05T20:20:25.453Z <Structure:INFO> Structure#1 loading controller interface scheman (ScheduleController) [latest-24152]2024-06-05T20:20:25.455Z <ScheduleController:null> Module ScheduleController v24097 [latest-24152]2024-06-05T20:20:25.455Z <Controller:INFO> Loaded ScheduleController version "0.1.24097"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> [latest-24152]2024-06-05T20:20:25.456Z <Structure:INFO> Structure#1 loading controller interface mosquitto-mqtt (MQTTController) [latest-24152]2024-06-05T20:20:25.459Z <MQTTController:null> Module MQTTController v24144 [latest-24152]2024-06-05T20:20:25.491Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24152]2024-06-05T20:20:25.503Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-24152]2024-06-05T20:20:25.503Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24152]2024-06-05T20:20:25.507Z <Structure:INFO> Starting controller VeraController#vera [latest-24152]2024-06-05T20:20:25.507Z <VeraController:NOTICE> VeraController#vera starting... [latest-24152]2024-06-05T20:20:25.510Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.521Z <Controller:INFO> VeraController#vera loaded implementation data ver 23109 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.521Z <Structure:INFO> Starting controller EzloController#ezlo [latest-24152]2024-06-05T20:20:25.523Z <Controller:INFO> EzloController#ezlo loaded ezlo capabilities ver 22266 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.528Z <Controller:INFO> EzloController#ezlo loaded implementation data ver 22344 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.528Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-24152]2024-06-05T20:20:25.530Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-24152]2024-06-05T20:20:25.530Z <Structure:INFO> Starting controller VirtualEntityController#virtual [latest-24152]2024-06-05T20:20:25.531Z <Controller:INFO> VirtualEntityController#virtual loaded virtualentity capabilities ver 22263 rev 2 format 1 [latest-24152]2024-06-05T20:20:25.532Z <Controller:INFO> VirtualEntityController#virtual loaded implementation data ver 22280 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.532Z <Structure:INFO> Starting controller HassController#hass [latest-24152]2024-06-05T20:20:25.532Z <HassController:NOTICE> HassController#hass starting... [latest-24152]2024-06-05T20:20:25.533Z <Controller:INFO> HassController#hass loaded hass capabilities ver 23289 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.536Z <Controller:INFO> HassController#hass loaded implementation data ver 24146 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.536Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-24152]2024-06-05T20:20:25.537Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-24152]2024-06-05T20:20:25.580Z <Structure:INFO> Starting controller ScheduleController#scheman [latest-24152]2024-06-05T20:20:25.580Z <ScheduleController:INFO> ScheduleController#scheman Sun Information entity is reactor_system>sun [latest-24152]2024-06-05T20:20:25.582Z <Controller:NOTICE> Controller ScheduleController#scheman is now online. [latest-24152]2024-06-05T20:20:25.582Z <Structure:INFO> Starting controller MQTTController#mosquitto-mqtt [latest-24152]2024-06-05T20:20:25.583Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.583Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.583Z <Structure:INFO> Starting controller MQTTController#mqtt [latest-24152]2024-06-05T20:20:25.583Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt [latest-24152]2024-06-05T20:20:25.584Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt_device [latest-24152]2024-06-05T20:20:25.584Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt [latest-24152]2024-06-05T20:20:25.584Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt_device [latest-24152]2024-06-05T20:20:25.584Z <Controller:INFO> MQTTController#mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.584Z <Controller:INFO> MQTTController#mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.587Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-24152]2024-06-05T20:20:25.587Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-24152]2024-06-05T20:20:25.588Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking... [latest-24152]2024-06-05T20:20:25.588Z <EzloController:WARN> EzloController: implementation of capability battery_maintenance does not provide attribute state [latest-24152]2024-06-05T20:20:25.589Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-24152]2024-06-05T20:20:25.602Z <EzloController:INFO> EzloController#ezlo: connecting to hub "xxxxxx" via anonymous local connection to wss://xxx.xxx.xxx.xxx [latest-24152]2024-06-05T20:20:25.605Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Dyr El (dyrEl) [latest-24152]2024-06-05T20:20:25.612Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Solar Production Forecast (solar_production_forecast) [latest-24152]2024-06-05T20:20:25.617Z <Controller:INFO> VirtualEntityController#virtual 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.617Z <HassController:NOTICE> HassController#hass connecting to ws://xxx.xxx.xxx.xxx/api/websocket [latest-24152]2024-06-05T20:20:25.622Z <MQTTController:WARN> MQTTController#mqtt file my_tasmota_generic_relay.yaml in /home/homebridge/reactor/config/mqtt_templates/my_tasmota_generic_relay.yaml overrides existing template definition my_tasmota_generic_relay [latest-24152]2024-06-05T20:20:25.622Z <MQTTController:WARN> MQTTController#mqtt file shelly_plug_s.yaml in /home/homebridge/reactor/config/mqtt_templates/shelly_plug_s.yaml overrides existing template definition shelly_plug_s [latest-24152]2024-06-05T20:20:25.622Z <MQTTController:WARN> MQTTController#mqtt file tasmota_sensor_lyw.yaml in /home/homebridge/reactor/config/mqtt_templates/tasmota_sensor_lyw.yaml overrides existing template definition tasmota_sensor_lyw [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file wallbox_pulsar_plus.yaml in /home/homebridge/reactor/config/mqtt_templates/wallbox_pulsar_plus.yaml overrides existing template definition wallbox_pulsar_plus [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file xiaofang_motion_light_sensor.yaml in /home/homebridge/reactor/config/mqtt_templates/xiaofang_motion_light_sensor.yaml overrides existing template definition xiaofang_motion_light_sensor [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_availability [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_availability_no_get [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_lqi [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_ota [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_power_switch [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_dimming [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_battery_power [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_control_outlet.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_control_outlet.yaml overrides existing template definition zigbee2mqtt_tradfri_control_outlet [latest-24152]2024-06-05T20:20:25.625Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb [latest-24152]2024-06-05T20:20:25.625Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_d [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws_d [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_door_sensor.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_door_sensor.yaml overrides existing template definition zigbee2mqtt_tuya_door_sensor [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_light_bulb_rgbcw.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_light_bulb_rgbcw.yaml overrides existing template definition zigbee2mqtt_tuya_light_bulb_rgbcw [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_tuya_motion_light_sensor [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_tuya_light_motion_sensor [latest-24152]2024-06-05T20:20:25.627Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_smart_plug_pm.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_smart_plug_pm.yaml overrides existing template definition zigbee2mqtt_tuya_smart_plug_pm [latest-24152]2024-06-05T20:20:25.628Z <Controller:NOTICE> Controller VirtualEntityController#virtual is now online. [latest-24152]2024-06-05T20:20:25.642Z <ScheduleController:INFO> ScheduleController#scheman entity ValueSensor#scheman>weekends edge "22:00" active, setting primary attribute value to natt [latest-24152]2024-06-05T20:20:25.651Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-24152]2024-06-05T20:20:25.654Z <HassController:INFO> HassController#hass successful authentication with ws://xxx.xxx.xxx.xxx; fetching initial data... [latest-24152]2024-06-05T20:20:25.658Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_mini_switch.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_mini_switch.yaml overrides existing template definition zigbee2mqtt_aqara_mini_switch [latest-24152]2024-06-05T20:20:25.658Z <HassController:INFO> HassController#hass Hass reports version "2024.5.5" location Hem timezone Europe/Stockholm state RUNNING safe_mode false [latest-24152]2024-06-05T20:20:25.661Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_motion_light_sensor [latest-24152]2024-06-05T20:20:25.661Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_light_motion_sensor [latest-24152]2024-06-05T20:20:25.664Z <MQTTController:INFO> MQTTController#mosquitto-mqtt instance topic ident is mosquitto-mqtt [latest-24152]2024-06-05T20:20:25.669Z <Controller:INFO> MQTTController#mosquitto-mqtt 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.669Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt connecting to broker at mqtt://127.0.0.1:1885/ [latest-24152]2024-06-05T20:20:25.686Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml overrides existing template definition zigbee2mqtt_aqara_sensor_temperature_humidity [latest-24152]2024-06-05T20:20:25.686Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml overrides existing template definition zigbee2mqtt_aqara_sensor_humidity_temperature [latest-24152]2024-06-05T20:20:25.687Z <MQTTController:INFO> MQTTController#mqtt instance topic ident is mqtt [latest-24152]2024-06-05T20:20:25.689Z <Controller:INFO> MQTTController#mqtt 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.689Z <MQTTController:NOTICE> MQTTController#mqtt connecting to broker at mqtt://127.0.0.1:1888/ [latest-24152]2024-06-05T20:20:25.690Z <app:NOTICE> Starting HTTP server and API... [latest-24152]2024-06-05T20:20:25.692Z <httpapi:NOTICE> [HTTPAPI]#1 starting HTTP service on port 8111 [latest-24152]2024-06-05T20:20:25.695Z <app:NOTICE> Starting Reaction Engine... [latest-24152]2024-06-05T20:20:25.695Z <Engine:INFO> Reaction Engine starting [latest-24152]2024-06-05T20:20:25.696Z <Engine:INFO> Checking rule sets... [latest-24152]2024-06-05T20:20:25.697Z <Engine:INFO> Checking rules... [latest-24152]2024-06-05T20:20:25.750Z <Engine:INFO> Data check complete; no corrections. --- Rules redacted to posting limits [latest-24152]2024-06-05T20:20:25.883Z <httpapi:NOTICE> [HTTPAPI]#1 HTTP server listening on "0.0.0.0":8111 [latest-24152]2024-06-05T20:20:25.896Z <httpapi:INFO> [HTTPAPI]#1 local docs found in /home/homebridge/reactor/docs/html; setting up static service [latest-24152]2024-06-05T20:20:25.897Z <app:NOTICE> Starting WSAPI... [latest-24152]2024-06-05T20:20:25.898Z <wsapi:NOTICE> wsapi: starting version 24148 [latest-24152]2024-06-05T20:20:25.919Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "2024-06-05 22:20:25" (TZ offset 120 mins from UTC) [latest-24152]2024-06-05T20:20:25.966Z <Controller:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.968Z <Controller:NOTICE> Controller VeraController#vera is now online. [latest-24152]2024-06-05T20:20:25.973Z <MQTTController:INFO> MQTTController#mosquitto-mqtt connected; opening subscriptions [latest-24152]2024-06-05T20:20:25.978Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_supervisor_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_core_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.terminal_ssh_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.esphome_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.file_editor_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_operating_system_update [latest-24152]2024-06-05T20:20:25.980Z <HassController:NOTICE> HassController#hass no signature match for conversation.home_assistant [latest-24152]2024-06-05T20:20:25.980Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-24152]2024-06-05T20:20:25.982Z <HassController:NOTICE> HassController#hass no signature match for remote.samsung_vardagsrummet [latest-24152]2024-06-05T20:20:26.005Z <HassController:NOTICE> HassController#hass no signature match for update.infopanel_hall_firmware [latest-24152]2024-06-05T20:20:26.009Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:26.020Z <MQTTController:INFO> MQTTController#mosquitto-mqtt sending inits and going online! [latest-24152]2024-06-05T20:20:26.021Z <Controller:NOTICE> Controller MQTTController#mosquitto-mqtt is now online. [latest-24152]2024-06-05T20:20:26.025Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyix3-98CDAC2F5883/online) for ljussensor [latest-24152]2024-06-05T20:20:26.026Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyplug-s-80646F811E35/online) for server [latest-24152]2024-06-05T20:20:26.029Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending shellies/shellyplug-s-80646F811E35/command with 6 byte payload to server [latest-24152]2024-06-05T20:20:26.033Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending shellies/shellyuni-C45BBE6C6DE8/command with 6 byte payload to poolvarmepump [latest-24152]2024-06-05T20:20:26.034Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Datarummet/get with 12 byte payload to datarummet [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Sovrummet/get with 12 byte payload to sovrummet [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Milia/get with 12 byte payload to milia [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Hallen 1/get with 12 byte payload to hallen1 [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Hallen 2/get with 12 byte payload to hallen2 [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Hallen 3/get with 12 byte payload to hallen3 [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Fönster köket/get with 12 byte payload to fonster_koket [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Soffan/get with 12 byte payload to soffan [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Framsida/get with 12 byte payload to framsida [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Skänk/get with 12 byte payload to skank [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Baksida/get with 12 byte payload to baksida [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa spel/get with 12 byte payload to lampa_spel [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Ellas rum/get with 12 byte payload to lampa_ella [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa gym/get with 12 byte payload to lampa_gym [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa TV/get with 12 byte payload to lampa_tv [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Vitrinskåp/get with 12 byte payload to vitrinskap [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending shellies/shelly1-34945471EBCF/relay/0/command with 6 byte payload to vvb [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Framsida/get with 12 byte payload to jul_framsida [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Köket/get with 12 byte payload to jul_köket [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Sovrummet/get with 12 byte payload to jul_sovrummet [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Datarummet/get with 12 byte payload to jul_datarummet [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Element gillestugan/get with 12 byte payload to element_gillestugan [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Växtbelysning källare/get with 12 byte payload to vaxtbelysning_kallare [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Kompressor/get with 12 byte payload to kompressor [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Luftrenare/get with 12 byte payload to luftrenare [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Uttag uterummet/get with 12 byte payload to uttag_uterummet [latest-24152]2024-06-05T20:20:26.039Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Entrebelysning/get with 12 byte payload to entrebelysning [latest-24152]2024-06-05T20:20:26.039Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa uterummet/get with 12 byte payload to lampa_uterummet [latest-24152]2024-06-05T20:20:26.050Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-24152]2024-06-05T20:20:26.051Z <MQTTController:INFO> MQTTController#mqtt connected; opening subscriptions [latest-24152]2024-06-05T20:20:26.062Z <MQTTController:ERR> MQTTController#mosquitto-mqtt event handler failed for zigbee2mqtt/Rörelse förrådet on rorelse_forradet: [ReferenceError] Capability string_sensor not extended (mosquitto-mqtt>rorelse_forradet [-] [latest-24152]2024-06-05T20:20:26.062Z <MQTTController:CRIT> ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>rorelse_forradet [-] ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>rorelse_forradet at Entity.setAttribute (/home/homebridge/reactor/server/lib/Entity.js:465:19) at MQTTController.handle_event (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:1240:19) at MqttClient.<anonymous> (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:591:38) at MqttClient.emit (node:events:519:28) at MqttClient.emit (node:domain:488:12) at MqttClient._handlePublish (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:1551:12) at MqttClient._handlePacket (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:533:12) at work (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:436:12) at process.processTicksAndRejections (node:internal/process/task_queues:77:11) [latest-24152]2024-06-05T20:20:26.063Z <MQTTController:ERR> MQTTController#mosquitto-mqtt event handler failed for zigbee2mqtt/Sovrumsdörr on sovrumsdorr: [ReferenceError] Capability string_sensor not extended (mosquitto-mqtt>sovrumsdörr [-] [latest-24152]2024-06-05T20:20:26.063Z <MQTTController:CRIT> ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>sovrumsdorr [-] ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>sovrumsdorr at Entity.setAttribute (/home/homebridge/reactor/server/lib/Entity.js:465:19) at MQTTController.handle_event (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:1240:19) at MqttClient.<anonymous> (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:591:38) at MqttClient.emit (node:events:519:28) at MqttClient.emit (node:domain:488:12) at MqttClient._handlePublish (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:1551:12) at MqttClient._handlePacket (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:533:12) at work (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:436:12) at process.processTicksAndRejections (node:internal/process/task_queues:77:11) [latest-24152]2024-06-05T20:20:26.071Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyuni-C45BBE6C6DE8/online) for poolvarmepump [latest-24152]2024-06-05T20:20:26.072Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyplug-s-80646F811E35/online) for server [latest-24152]2024-06-05T20:20:26.074Z <MQTTController:INFO> MQTTController#mqtt sending inits and going online! [latest-24152]2024-06-05T20:20:26.075Z <Controller:NOTICE> Controller MQTTController#mqtt is now online.reactor.yaml"sovrumsdorr": name: "Sovrumsdörr" topic: "Sovrumsdörr" include: zigbee2mqtt_tuya_door_sensor -
[2/2]
zigbee2mqtt_common.yaml# Requires: "topic". # Optional: "prefix" (default: zigbee2mqtt). # mqtt_device.online requires "availability: true" in Zigbee2MQTT config. # https://www.zigbee2mqtt.io/guide/configuration/device-availability.html description: "Zigbee2MQTT base templates" author: "@Crille, Smart Home Community" license: MIT repository: "https://github.com/calmen77/MSR-mqtt_templates" version: 24155 templates: # Availability with query zigbee2mqtt_availability: capabilities: [x_mqtt_device] requires: [topic] query: topic: "%prefix:zigbee2mqtt%/%topic%/get" payload: state: "" type: json events: "%prefix:zigbee2mqtt%/%topic%/availability": "x_mqtt_device.online": if_expr: '! isnull(payload)' expr: 'lower(payload) == "online"' # Availability without query for device not supporting /get zigbee2mqtt_availability_no_get: capabilities: [x_mqtt_device] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%/availability": "x_mqtt_device.online": if_expr: '! isnull(payload)' expr: 'lower(payload) == "online"' # Link quality in lqi zigbee2mqtt_lqi: capabilities: [value_sensor] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "value_sensor.value": json_payload: true if_expr: '! isnull(payload)' expr: 'payload.linkquality' "value_sensor.units": "lqi" # String sensor for available OTA update for device zigbee2mqtt_ota: capabilities: [string_sensor] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "string_sensor.value": json_payload: true if_expr: '! isnull(payload)' expr: 'payload?.update_available ? "OTA firmware update available!" : "no update available"' # Power switch capability zigbee2mqtt_power_switch: capabilities: - power_switch - toggle requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "power_switch.state": json_payload: true expr: 'payload?.state == "ON"' actions: power_switch: "on": topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: "ON" "off": topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: "OFF" set: topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: expr: "parameters.state ? 'on' : 'off'" type: raw # Dimming capability zigbee2mqtt_dimming: capabilities: [dimming] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "dimming.level": json_payload: true expr: 'round(payload?.brightness / 100 / 2.55 , 2)' actions: dimming: set: topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: expr: '{"brightness": round(parameters.level * 100 * 2.55 , 2)}' type: json # Battery level zigbee2mqtt_battery_power: capabilities: [battery_power] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "battery_power.level": json_payload: true expr: 'payload?.battery / 100' "battery_power.since": expr: 'time()' actions: x_mqtt_device: poll: falsezigbee2mqtt_tuya_door_sensor.yaml# Requires: "topic". # Optional: "prefix" (default: zigbee2mqtt). # mqtt_device.online requires "availability: true" in Zigbee2MQTT config. # https://www.zigbee2mqtt.io/devices/SNZB-04.html description: "Zigbee2MQTT template for TuYa Smart Door Sensor." author: "@Crille, Smart Home Community" license: MIT repository: "https://github.com/calmen77/MSR-mqtt_templates" version: 24155 templates: zigbee2mqtt_tuya_door_sensor: #type: capabilities: - door_sensor primary_attribute: door_sensor.state requires: [topic] include: - zigbee2mqtt_availability_no_get - zigbee2mqtt_lqi - zigbee2mqtt_battery_power events: "%prefix:zigbee2mqtt%/%topic%": "door_sensor.state": json_payload: true expr: 'payload?.contact' -
Turn debug level 5 on for MQTTController. It will show you how it's loading the templates and building the final entity configuration. The message fragment you'll want to look for is
merged template for sovrumsdorr... then work backwards in the log from there toconfiguring entity sovrumsdorr. Everything in between is the setup.Also examine the debug messages at startup for where it's finding templates and loading them... make sure everything it's loading is what's intended, and you don't have a stray old file sitting around somewhere that it's sucking in.
Edit: your logs are showing a lot of duplicate definitions in the startup messages...
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
It seems to merge the
events:section ofstring_sensorandpower_switchin...common.yamland wrapvalue_sensor.unitsinstring_sensorcapability.
I've looked for strange characters that could cause it but found nothing, validated all files OK in yamllint.[latest-24152]2024-06-06T06:29:11.699Z <MQTTController:5:MQTTController.js:146> MQTTController#mosquitto-mqtt configuring entity sovrumsdorr [latest-24152]2024-06-06T06:29:11.699Z <MQTTController:5:MQTTController.js:205> MQTTController#mosquitto-mqtt merged template for sovrumsdorr (from /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml/zigbee2mqtt_common.yaml): { "capabilities": [ "door_sensor", "x_mqtt_device", "value_sensor", "battery_power" ], "primary_attribute": "door_sensor.state", "requires": [ "topic" ], "include": [ "zigbee2mqtt_availability_no_get", "zigbee2mqtt_lqi", "zigbee2mqtt_battery_power", "zigbee2mqtt_tuya_door_sensor" ], "events": { "%prefix:zigbee2mqtt%/%topic%": { "door_sensor.state": { "json_payload": true, "expr": "payload?.contact" }, "value_sensor.value": { "json_payload": true, "if_expr": "! isnull(payload)", "expr": "payload.linkquality", "attribute": "value_sensor.value" }, "value_sensor.units": "lqi", "string_sensor.value": { "json_payload": true, "if_expr": "! isnull(payload)", "expr": "payload?.update_available ? \"OTA firmware update available!\" : \"no update available\"", "attribute": "string_sensor.value" }, "power_switch.state": { "json_payload": true, "expr": "payload?.state == \"ON\"", "attribute": "power_switch.state" }, "battery_power.level": { "json_payload": true, "expr": "payload?.battery / 100", "attribute": "battery_power.level" }, "battery_power.since": { "expr": "time()", "attribute": "battery_power.since" } }, "%prefix:zigbee2mqtt%/%topic%/availability": { "x_mqtt_device.online": { "if_expr": "! isnull(payload)", "expr": "lower(payload) == \"online\"", "attribute": "x_mqtt_device.online" } } }, "__source": "/home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml/zigbee2mqtt_common.yaml", "actions": { "x_mqtt_device": { "poll": false } }, "name": "Sovrumsdörr", "topic": "Sovrumsdörr" } [latest-24152]2024-06-06T06:29:11.699Z <MQTTController:5:MQTTController.js:264> MQTTController#mosquitto-mqtt set primary attribute of door_sensor.state to Entity#mosquitto-mqtt>sovrumsdorr [latest-24152]2024-06-06T06:29:11.700Z <MQTTController:5:MQTTController.js:289> MQTTController#mosquitto-mqtt registering event handler %prefix:zigbee2mqtt%/%topic% for sovrumsdorr [latest-24152]2024-06-06T06:29:11.700Z <MQTTController:5:MQTTController.js:289> MQTTController#mosquitto-mqtt registering event handler %prefix:zigbee2mqtt%/%topic%/availability for sovrumsdorr [latest-24152]2024-06-06T06:29:11.700Z <MQTTController:5:MQTTController.js:368> MQTTController#mosquitto-mqtt registering action x_mqtt_device.poll for sovrumsdorrRegarding the duplicates, it could be the templates with different
primary_attribute:and it is on my roadmap to bring it up for discussion if attributes also could be parameterized with defaults like%primary_attribute:[temperature / humidity / power_switch / dimming / motion / light]%or%temperature_sensor.units:[C / F]%.EDIT: Or is caused by the mystery of this issue? e.g.
string_sensorandpower_switchis somehow included in all templates. -
@Crille at some point I had similar problems, I fixed them and I reported here. Now I cannot repro it again, but it seems very similar and related to primary attributes in base templates. It seems like the first one is used and that’s causing troubles along the hierarchy, but, as I said, I’m not able to repro it again.
-
It also looks like something may be getting a shallow copy when it needs a deep copy, and it's being modified later and polluting the other references. I'm really tied up today, but I'll look at this as soon as I can.
Did you address the template redefinitions that were being logged at startup? That has nothing to do with primary attributes; the entire template is trying to be redefined.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
