Hi,
Running the latest MSR latest-24152-3455578a with the latest HA 2024.6.1. When trying to call a service I get the following in the MSR logs. Is this a version mismatch? I am not seeing anything in the HA logs.
[latest-24152]2024-06-11T10:29:56.162Z <Rule:INFO> rule-Monitor-DHW (rule-lsvq5k3x in Central Heating) started [latest-24152]2024-06-11T10:29:58.625Z <HassController:WARN> HassController#hass unknown service opentherm_gw.set_hot_water_setpoint in x_hass.call_service action on Thermostat#hass>climate_living_room_otgw [latest-24152]2024-06-11T10:29:58.626Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Thermostat#hass>climate_living_room_otgw action: [Object]{ "type": "call_service", "service_data": { "gateway_id": "living_room_otgw", "temperature": 65 }, "domain": "opentherm_gw", "service": "set_hot_water_setpoint", "target": { "entity_id": "climate.living_room_otgw" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:ERR> HassController#hass request 1718101798626<6/11/2024, 12:29:58 PM> (call_service) failed: [Object]{ "id": 1718101798626, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "extra keys not allowed @ data['entity_id']" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:WARN> HassController#hass action x_hass.call_service([Object]{ "service": "opentherm_gw.set_hot_water_setpoint", "data": "{ \"gateway_id\": \"living_room_otgw\", \"temperature\": 65 }" }) on Thermostat#hass>climate_living_room_otgw failed!Cheers Rene
Some background
I'm trying to integrate a Zigbee device into the MSR using zigbee2mqtt bridge and MQTTController. The device in question is a cheap mood light that has following properties that I'd like to control:
I'v already managed to get the switch part working and can toggle the light on/off. Also the brightness value is mapped back to MSR. In zigbee2mqtt it has a value range from 0 to 254, so this the reason for the expression:
expr: 'payload.brightness / 254'Here's the entity definition (don't know whether the type should be something else than the Switch)
zigbee-lidl-mood-light: name: 'Lidl Mood Light' friendly_name: 'Mood Light' type: Switch uses_template: lidl-moodlightAnd the corresponding template (NOTE: rgb_color has not been defined in this example):
lidl-moodlight: init: "zigbee2mqtt/%friendly_name%/get/state" query: "zigbee2mqtt/%friendly_name%/get/state" capabilities: - power_switch - toggle - dimming primary_attribute: power_switch.state events: "zigbee2mqtt/%friendly_name%": "power_switch.state": json_payload: true expr: 'upper(payload.state) == "ON"' "dimming.level": json_payload: true expr: 'payload.brightness / 254' actions: power_switch: "on": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'ON' "off": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'OFF' set: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: expr: "parameters.state ? 'ON' : 'OFF'" type: raw toggle: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'TOGGLE'The problem
In order to control the brightness or the RGB color values, I would have send a JSON payload in corresponding actions. But I have no idea how to define it in the template. The reason why the switch part is working is that the zigbee2mqtt accepts also plain ON / OFF / TOGGLE string payloads in that case.
But the brightness should be controlled with the following payload:
{"brightness": 196}And the RGB color like:
{"color":{"rgb":"46,102,150"}}Here's the link for the documentation (the Exposes part defines the messages).
So how should I define the JSON payload for example for the dimming action? It definitely should be some sort of expressions since I have to map the MSR real value (0...1) to (0...254) for the zigbee2mqtt.
actions: dimming: set: topic: "zigbee2mqtt/%friendly_name%/set" payload: expr: ????? type: jsonAnother problem is the RGB value. I could use the rgb_color capability for the setting but the problem is that the zigbee2mqtt only reports the current color in hue/saturation or xy coordinates.
Here's an example of published message after setting the color:
Topic: zigbee2mqtt/Mood Light QoS: 0 { "brightness":254, "color":{ "hue":240, "saturation":100, "x":0.1355, "y":0.0399 }, "color_mode":"xy", "color_temp":574, "linkquality":96, "state":"ON" }I would have to map those values back to RGB, but is it even possible with existing constructs in MQTTController's templates?
Help would be appreciated @toggledbits
br,
mgvra
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.
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 need a handful of victims volunteers to help test previews of the next build of Reactor. A long-standing request was for "a simple login mechanism," but in practice, adding user authentication and competent access control turned out to be a pretty big project with a lot of big changes on both server and client sides. It's a bit more than I'm comfortable testing myself and springing out to everyone at once, so I'd like to work with a small group to put it through "sea trials."
Major changes/features include:
User authentication with hashed password storage; User group configuration with application restriction (admin, dashboard, API); Detailed control over API access, with user- and token-based authentication/authorization; Improvements to the HTTPS service; Improvements to UI coordination with the core for Rules and Reactions.If this sounds like something you'd like to help with, drop me a reply here in this thread or privately.
[Solution: Reactor 24115 is not compatible with MQTTController > 24120]
Reactor latest-24115 bare metal.
All MQTT entities stop working after updating MQTTController to 24142, downgrade to 24120 and they are back. Templates and configured entities has not been changed between versions.
I'm not sure if uses_template should be replaced by ìnclude in entity configuration in reactor.yaml but I guess not, I've tried it and it did not do any difference.
I have not tried to update Reactor to userauth version.
Example entity in reactor.yaml that uses MQTTController included template:
entities: "takflakt_kallare": name: "Takfläkt källare" topic: "Källartemp" unit: "" uses_template: tasmota_generic_relay init: "cmnd/%topic%/POWER%unit%"Any hints? Do you need more info, please let me know.
Log from startup:
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
![](https://github.com/fluidicon.png)
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Is the following config correct?
- id: time_series name: "Out temp" capabilities: temperature_sensor: attributes: value: model: time series entity: "hass>sensor_outdoor_temperature" attribute: "temperature_sensor.value" interval: 5 # minutes retention: 20 # minutes aggregate: wma primary_attribute: temperature_sensor.value type: ValueSensorSpecifically, is "depth" directive needed/mandatory here? Reason I'm asking is that I'm not getting a "final" value in MSR, only debug values are shown:
temperature_sensor.units=null temperature_sensor.value=null x_virtualentity.last_request_time=null x_virtualentity.request_failures=null x_virtualentity.template=null x_virtualentity.timeseries_debug=[{"time":1716537360000,"value":22.1},{"time":1716537660000,"value":22},{"time":1716537960000,"value":22},{"time":1716538260000,"value":21.9},{"time":1716538560000,"value":22}]Good morning,
I apologize if this subject has been covered. I did try the search, but I'm not coming up with any topics on my issue.
I'm running userauth-24137-57b41335, bare metal installation on Fedora 39 Server.
I have a rule set up to turn the Eco mode off on my Nest Thermostat when the thermostat is set to Away (Rule State: Away Mode), the user (Driver) presence in my car changes to true, and the destination is set to home.
93804f7c-62d6-42c0-ae04-ff602011a6fd-image.png
This works fine for most days, where I'm headed home from work (commute is about 45 minutes). What I don't want it to do is set change it to Eco mode if my ETA is more than an hour.
There is a sensor/entity for Time to Arrival when the Destination is set. What it appears to provide is the Time OF arrival/ETA, not time until arrival. If it was Time until Arrival, and it was a numeric value, I could simply test if the value is less than 60 and be done with it.
I pulled up the history through Home Assistant for my morning commute and this appears to be what it is providing.
c2a32739-c84f-4a05-95d9-73793ed818f5-image.png
So what I need to do is to do a calculation of the the ETA from the sensor value and subtract the current time, and get a value in minutes that I can determine if it's less than 60.
I believe I can do this with the local expression, but I don't see anything for the system time, or local time. Also, do the local expressions update themselves if the sensors do?
Good morning,
I'm running userauth-24137-57b41335 on Fedora 39, bare metal installation.
ZWaveJSController 0.1.23254
Home Assistant:
Core, 2024.5.3 Supervisor, 2024.05.1 Operating System, 12.3 Frontend, 20240501.1I'm trying to troubleshoot a Dynamic Group Controller and notification alert that I've set up for low battery level.
In my Reactor.config, I have the following lines:
name: "Dynamic Group Controller" implementation: DynamicGroupController config: groups: "zwavejs_dead": select: - include_group: "zwavejs" filter_expression: "entity?.attributes?.zwave_device?.status == 3" group_actions: true "low_battery": select: - include_capability: battery_power filter_expression: > entity.attributes.battery_power.level < 0.35The idea here is that I should only have members of this group that have a battery level below 35%. When I go into Entities, I show a whole slew of devices, none of which have a battery level below the threshold.
a77e445b-ab78-4752-a624-3c4117f34f90-image.png
I also tried setting up a rule to generate a push notification once a day, but with all of the group members, I've had to disable the rule. I believe I have it set up correctly, but I'm not 100% sure. I want the notification to tell me the battery level for that device as well.
289b4f68-03ba-49c0-8275-f0f197d13a3a-image.png
ce24a76e-6865-40bd-bd85-632e54d315a8-image.png dc837424-deb5-4ef7-8f0d-3676f1769535-image.png
Can anyone point to me what I may have misconfigured to get these results?
I should also note I'm only interested in ZWaveJS devices. It's showing me battery status for my iPad and car as well, which I don't need it to send me.
I have a case where I'm trying to send a MQTT message similar to the example below:
Topic: pool/set { "command": 4, "value": 1, "time": 0, "interval": 0 }But I need to set "value" so that it is an integer between 20-30. I thought I could use "dimming" capability here, but there's probably a better way. @therealdb ?
(Using userauth-24120-7745fb8d build in Docker)
There's a filtering capability for entities in reactor.yaml, but I have a case where I don't want to filter an entity altogether, but would like to "throttle" it, as this sensor updates every 1-2 seconds (and therefore unnecessarily takes database space).
Sensor data comes through home assistant, and seems that there's no way to control update interval at that end.
So I'm asking if plugin configuration could support limiting/throttling updates for certain entities?
Good morning,
Hopefully this is a simple request. I believe the title should be self explanatory, but just in case, I'll elaborate.
On the status tab, we all get alerts if a device state has changed (i.e., been removed). This is great, but when I go into the entities tab, I have to either type the name (or a portion thereof) of the device that has been removed, or I need to scroll all the way through my list of devices. This is infrequent, however, yesterday I replaced a failed device in my HAAS environment. It was a Z-Wave switch that is added using the Smart Scan QR code, which normally makes it pretty easy. However, some devices don't get fully added the first time around, so it'll add multiple entries into HAAS until it get's the S2 authentication correct and the device fully included. It did this to me yesterday, and I had to delete the incomplete device from my installation. MSR still saw the entities of that failed/incomplete switch entity, and I was left with 8 alerts and entities that I needed to removed.
It's not a huge problem, but this example was just one switch. If I were to add replace multiple devices at once, this could be a bit more annoying to remove. It would be helpful to be able to filter by removed entities, so I can find them all quickly and delete them. Continuing that train of thought, it would also be useful to have check boxes next to those lines, and perhaps do a select all type of thing so they could be deleted in one mouse click.
@toggledbits I have finally finished up the SSL using Let's Encrypt and am getting this from my local browser:
f3d0ac22-272e-46c1-b7e3-57b08bdd1555-image.png
21c04fe1-1760-4ce6-a4de-2285d3349940-image.png
3a7022db-5add-40a1-b9a2-0c0b97fa211b-image.png
I know you said in the docs that using a self-signed could lead to this but this is LE.
Hi @toggledbits,
I don't know if I'm the only one, so I'm reporting here first instead of opening a bug.
Basically, with the latest 2-3 updates of Reactor and MQTTController, after a restart previous statuses are lost (for both Virtual and MQTT entities), until they're restored.
It's particularly annoying for Virtual Entities, because I have to set them all over again (I've coded some defaults at startup if the values are empty, but sometimes these are not the correct values before the update).
Not easy to reproduce, and logs are gone, but the first time I tought it was me hallucinating, the second one didn't bother too much, after the third I realized it's something not coming from me.
the behavior could be seen in this screenshot:
1c007fc2-4dbc-4476-8dca-e5aa111e4642-image.png
Any hint is appreciated.
Good morning,
So Home Assistant decided to change the default weather home format that I've been using for the past year and a half. I had two Global Expressions set up to pull the high and low temp forecast for the day. Now it's pulling null values.
094c9205-cc9e-4fcc-ac4f-1bf54acea299-image.png
In the dev tools, it now uses a new service (Weather. get forecasts), plural, where the old Weather.get forecast is depreciated and now longer functions.
8c7a1fcc-dd3f-4268-a0b7-29d542f86adc-image.png
It shows a templow field, and a temperature field, which I presume is the forecast high.
When I head back over to MSR, I'm having a hard time finding those values in the Entities tab.
c5ea1048-a72e-4647-9c50-9d0c5fd20767-image.png
wx.asoftime=null wx.ceiling=null wx.ceiling_unit=null wx.cloud_cover=null wx.condition_code=null wx.description="partlycloudy" wx.feels_like=null wx.humidity=57 wx.humidity_unit="%" wx.icon=null wx.location=null wx.precipitation_1hr=null wx.precipitation_24hr=null wx.precipitation_other=null wx.precipitation_type=null wx.precipitation_unit="in" wx.pressure=30 wx.pressure_unit="inHg" wx.temperature=55 wx.temperature_unit="°F" wx.visibility=null wx.visibility_unit="mi" wx.wind_compass=210.3 wx.wind_conditions=null wx.wind_direction="SSW" wx.wind_gust=null wx.wind_speed=6.28 wx.wind_speed_unit="mph" x_hass.domain="weather" x_hass.entity_id="weather.forecast_home" x_hass.services=["weather"] x_hass.state="partlycloudy" x_hass_attr.attribution="Weather forecast from met.no, delivered by the Norwegian Meteorological Institute." x_hass_attr.cloud_coverage=85.9 x_hass_attr.dew_point=40 x_hass_attr.friendly_name="New Windsor Weather" x_hass_attr.humidity=57 x_hass_attr.precipitation_unit="in" x_hass_attr.pressure=30 x_hass_attr.pressure_unit="inHg" x_hass_attr.supported_features=3 x_hass_attr.temperature=55 x_hass_attr.temperature_unit="°F" x_hass_attr.visibility_unit="mi" x_hass_attr.wind_bearing=210.3 x_hass_attr.wind_speed=6.28 x_hass_attr.wind_speed_unit="mph"There is a x_hass_attr.temperature, but that appears to be the current temperature, not the high that I found on the dev tools screenshot.
Any ideas?
Running:
Core
2024.4.3
Supervisor
2024.04.0
Operating System
12.2
Frontend
20240404.2
MSR: latest-24057-e9add9f5
Hey Patrick, I recently have been noticing that MSR has been acting up ie. it's been needing restarts and has been slow. I began trouble shooting by looking at the logs and have noticed the following errors for a lot of entities. I thought maybe a simple reboot of RPi was needed and I kept seeing the same errors in the system logs. I am oddly enough not seeing these same errors in the MSR logs. Where things started getting weird is whenever I rebooted MSR it wouldn't come back online .I would have to restart the RPi then it would come back online. I just restarted MSR again to capture logs and it restarted fine, so I guess its good for now? I think this is more or so a corrupted SD card issue rather a MSR issue but well being troubleshooting from here. The SD card is about 1-2 years old.
Apologies if this post is everywhere, I cannot consistently recreate any oddities that are happening, that's what is leading me to believe my SD is going bad.
PS: If anyone knows how to diagnose a corrupt SD card please chime in.
MSR latest-24057-e9add9f5
Home Assistant 2024.4.3
Raspberry Pi 3b+
This system has been running flawlessly year after year for the time changes twice a year literally since MSR came out so I was caught off-guard when this happened this morning.
Time in MSR browser is EST, time on RPi is local time (DST).
76ed5313-b9b9-46d4-b0f9-462c40e99750-image.png
195e61c5-58a7-4453-b96a-18cebae75550-image.png
I've rebooted the RPi I've restarted MSR after double-checking the time on the RPi. Used a completely different browser to eliminate any caching concerns. Double-checked MSR reactor.yamla5f23151-d691-4343-8499-8e77a55528e5-image.png
What am I missing here @toggledbits ?
Hi,
For the standard capabilities MSR sends both a value record and a units record to InfluxDB. The latter I would like not to send as they are not really any use for me and it will reduce the number of records send to my InfluxDB.
Is there a quick way to do this with a filter_entities line like: *>units?
Or do I have to update all capabilities to read like this:
power_sensor:
attributes:
value: true
Cheers Rene
[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_attribute
or 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?
-
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.
-
@toggledbits oh, my bad. I'll try to re-pro again when home, but it should be
x_energy_sensor_exported
for Y and the device name for X. -
OK. That helps. And problem understood. I think I have an answer. New build later today.
-
OK. MQTTController build 24144 up. Adds support for a
capabilities
section at the top level of any template file. Format is same as for system_capabilities.yaml. See MQTTController docs, updated. -
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.
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.
-
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: false
zigbee2mqtt_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...
-
It seems to merge the
events:
section ofstring_sensor
andpower_switch
in...common.yaml
and wrapvalue_sensor.units
instring_sensor
capability.
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 sovrumsdorr
Regarding 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_sensor
andpower_switch
is 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.