Multi-System Reactor

Good morning,
I'm trying to figure out if there is a way to evaluate if a command was completed and retry if it did not complete.

I have 14 iBlinds 3.1 z-wave controllers in my home. 95% of the time, they work just fine. Occasionally, I'll get a blind that does not open on the first attempt. When I go into Home Assistant, and manually open or close the blind, it works.

I have 3 reactions set up for each room. One to open, one to close, and one partial open for sun glare. Each of them is set up as below.

5afc9924-4300-4718-9e23-8855c4a3a9fd-image.png

The reactions are set up to wait for 5 seconds before going onto the next blind, so the z-wave network doesn't get overwhelmed.

In addition, the set command to run the reactions has "Wait for completion" checked.

3919fc06-c1f1-4c49-bf95-716028d18a27-image.png

I also have a routine set up whenever a z-wave device reports as non-functional (dead), it'll get pinged to wake it up. This usually works to wake them up.

16df4bff-c733-4ec2-a55c-c964238ada3b-image.png

Appreciate any ideas to make this more reliable.

I'm running:

Reactor latest-24190-bd310acc, Bare-metal on Fedora WaveJSController [0.1.23326] Home Assistant: 2024.7.0

I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.

For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.

Good morning,
I'm going through my ruleset this morning, trying to get away from haas>blahblablah entries and completely migrate them all to zwavejs>xx-0 entries where possible.

I have 3 Aeon MultiSensor 6 devices in my home, all USB powered.

When using Haas entries, I see an entry for hass>binary_sensor_guest_bedroom_multisensor_home_security_motion_detection, and motion_sensor.state (primary)

Screenshot 2024-07-25 at 8.25.53 AM.png

Under ZwaveJS, this entry appears to be missing.

Screenshot 2024-07-25 at 8.26.51 AM.png

From the Entities page:

battery_power.level=1
battery_power.since=1721910337433
binary_sensor.state=false
humidity_sensor.units="%"
humidity_sensor.value=46
light_sensor.units="Lux"
light_sensor.value=5
tamper.state=false
temperature_sensor.units="°F"
temperature_sensor.value=73.8
x_debug.dt={}
x_zwave_values.Basic_currentValue=0
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Binary_Sensor_Any=false
x_zwave_values.Configuration_Automatic_Report_Group_1_Battery_1=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Humidity_64=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Luminance_128=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Temperature_32=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Ultraviolet_16=1
x_zwave_values.Configuration_Automatic_Report_Group_2_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_1=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_2=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_3=3600
x_zwave_values.Configuration_Automatic_Temperature_Reporting_Unit=2
x_zwave_values.Configuration_Battery_Level_Threshold=10
x_zwave_values.Configuration_Current_Power_Mode_65280=0
x_zwave_values.Configuration_Humidity_Above_Lower_Limit_32=0
x_zwave_values.Configuration_Humidity_Below_Lower_Limit_2=0
x_zwave_values.Configuration_Humidity_Change_Threshold=10
x_zwave_values.Configuration_Humidity_Recover_Limit=5
x_zwave_values.Configuration_Humidity_Sensor_Calibration=0
x_zwave_values.Configuration_LED_Blinking=0
x_zwave_values.Configuration_Lighting_Recover_Limit=10
x_zwave_values.Configuration_Lock_Configuration=0
x_zwave_values.Configuration_Low_Battery_Threshold=20
x_zwave_values.Configuration_Low_Temperature_Alarm_15_C=0
x_zwave_values.Configuration_Lower_Humidity_Limit=50
x_zwave_values.Configuration_Lower_Lighting_Limit=100
x_zwave_values.Configuration_Lower_Temperature_Limit_4294901760=320
x_zwave_values.Configuration_Lower_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Lower_Ultraviolet_Limit=4
x_zwave_values.Configuration_Luminance_Above_Lower_Limit_64=0
x_zwave_values.Configuration_Luminance_Below_Lower_Limit_4=0
x_zwave_values.Configuration_Luminance_Change_Threshold=100
x_zwave_values.Configuration_Luminance_Sensor_Calibration=0
x_zwave_values.Configuration_Motion_Sensor_Report_Type_to_Send=2
x_zwave_values.Configuration_PIR_Sensitivity=3
x_zwave_values.Configuration_PIR_Sensor_Timeout=20
x_zwave_values.Configuration_Recover_Limit_Temperature_Unit_255=2
x_zwave_values.Configuration_Report_Above_Humidity_Threshold_32=0
x_zwave_values.Configuration_Report_Above_Luminance_Threshold_64=0
x_zwave_values.Configuration_Report_Above_Temperature_Threshold_16=0
x_zwave_values.Configuration_Report_Above_Ultraviolet_Threshold_128=0
x_zwave_values.Configuration_Report_Below_Humidity_Threshold_2=0
x_zwave_values.Configuration_Report_Below_Luminance_Threshold_4=0
x_zwave_values.Configuration_Report_Below_Temperature_Threshold_1=0
x_zwave_values.Configuration_Report_Below_Ultraviolet_Threshold_8=0
x_zwave_values.Configuration_Reset_Parameters_101_103_to_Default_Values=null
x_zwave_values.Configuration_Reset_Parameters_111_113_to_Default_Values=null
x_zwave_values.Configuration_Reset_to_Factory_Default_Setting=null
x_zwave_values.Configuration_Selective_Reporting=0
x_zwave_values.Configuration_Sleep_State_255=2
x_zwave_values.Configuration_Temperature_Above_Lower_Limit_16=0
x_zwave_values.Configuration_Temperature_Below_Lower_Limit_1=0
x_zwave_values.Configuration_Temperature_Calibration_Offset_65280=0
x_zwave_values.Configuration_Temperature_Calibration_Unit_255=2
x_zwave_values.Configuration_Temperature_Change_Threshold_4294901760=20
x_zwave_values.Configuration_Temperature_Recover_Limit_65280=20
x_zwave_values.Configuration_Temperature_Threshold_Unit_3840=2
x_zwave_values.Configuration_Ultraviolet_Above_Lower_Limit_128=0
x_zwave_values.Configuration_Ultraviolet_Below_Lower_Limit_8=0
x_zwave_values.Configuration_Ultraviolet_Change_Threshold=2
x_zwave_values.Configuration_Ultraviolet_Recover_Limit=2
x_zwave_values.Configuration_Ultraviolet_Sensor_Calibration=0
x_zwave_values.Configuration_Upper_Humidity_Limit=60
x_zwave_values.Configuration_Upper_Lighting_Limit=1000
x_zwave_values.Configuration_Upper_Temperature_Limit_4294901760=824
x_zwave_values.Configuration_Upper_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Upper_Ultraviolet_Limit=8
x_zwave_values.Configuration_Wake_Device_for_10_minutes_After_Power_On=1
x_zwave_values.Configuration_Wake_Up_Timeout=15
x_zwave_values.Manufacturer_Specific_manufacturerId=134
x_zwave_values.Manufacturer_Specific_productId=100
x_zwave_values.Manufacturer_Specific_productType=258
x_zwave_values.Multilevel_Sensor_Air_temperature=73.8
x_zwave_values.Multilevel_Sensor_Humidity=46
x_zwave_values.Multilevel_Sensor_Illuminance=5
x_zwave_values.Multilevel_Sensor_Ultraviolet=0
x_zwave_values.Notification_Home_Security_Cover_status=0
x_zwave_values.Notification_Home_Security_Motion_sensor_status=0
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Version_firmwareVersions=["1.17"]
x_zwave_values.Version_hardwareVersion=100
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="4.54"
x_zwave_values.Wake_Up_controllerNodeId=1
x_zwave_values.Wake_Up_wakeUpInterval=3600
zwave_device.capabilities=[32,48,49,112,113,114,128,132,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Sensor"
zwave_device.impl_sig="23326:1:22315:1"
zwave_device.is_beaming=false
zwave_device.is_listening=true
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[134,258,100]
zwave_device.max_data_rate=null
zwave_device.node_id=53
zwave_device.specific_class="Routing Multilevel Sensor"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"1.17"]
zwave_device.wakeup_interval=3600

I'm running:

Reactor latest-24190-bd310acc, Bare-metal on Fedora
WaveJSController [0.1.23326]
Home Assistant: 2024.7.0

I'm fetching certain data five past every hour, but I would like to do it closer to the hour, e.g. 1 or 2 past (but not at the hour).

I experimented with the following rule that almost works (triggers also at the hour which is not the intention). Any advice for a solution?

Screenshot 2024-07-23 at 16.27.40.png

It would be nice to have an ability to bookmark a direct link to a dashboard item. In my case I would use this feature to access a virtual switch directly.

Hi @toggledbits

Would you please consider adding an extra sublevel in the rulesets?

I have grouped my rules in rooms/ areas. This works great for me, but I would also like to group rules for the same functionality (in a room). This would make the rules easier to find and name.

Please let me know if this is an option. Thanks!

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

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

Thanks in advance.

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

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

@toggledbits,
I have this device attached to my system, but use a DSC panel. If you need testers to move forward, I'm happy to help.

I'm curious what your thinking the use case is for this. I currently have it integrated into HomeAssistant, and it works fine for the most part. The one thing I can't do is bypass zones, which I would like to have the ability to do.

Are you looking at more direct control for the panel, as opposed to having to jump through HA (or another system) first?

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 ruleset which I though had been working well until this morning when I noticed it's not.

I've put four weather conditions in an in array and one of them is the current weather condition - but the rule is not true. Now the cloud cover percentage is not yet met but this is an or rule so as long as the "Current Conditions" are met then it should go true.

What's the obvious thing I'm missing here? (I've tried spaces/no spaces in the in and no difference.)

4b7631d5-9766-4092-8eaf-70b147a11e0f-image.png

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:

switch (on/off) brightness color

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-moodlight

And 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: json

Another 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.

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:

[latest-24115]2024-05-28T14:42:35.995Z <app:null> Reactor build latest-24115-55b591da starting on v20.13.1 [latest-24115]2024-05-28T14:42:35.996Z <app:null> Process ID 38403 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-24115]2024-05-28T14:42:35.996Z <app:null> Basedir /home/homebridge/reactor; data in /home/homebridge/reactor/storage [latest-24115]2024-05-28T14:42:35.996Z <app:null> NODE_PATH=/home/homebridge/reactor [latest-24115]2024-05-28T14:42:36.010Z <app:null> Resolved timezone=Europe/Stockholm, environment TZ=(undefined); offset minutes from UTC=120 [latest-24115]2024-05-28T14:42:36.012Z <app:null> Configured locale sv-SE; selected locale(s) sv-SE [latest-24115]2024-05-28T14:42:36.018Z <app:null> Loaded locale sv-SE for sv-SE [latest-24115]2024-05-28T14:42:36.018Z <app:null> Local date/time using configured timezone and locale formatting is "2024-05-28 16:42:36" [latest-24115]2024-05-28T14:42:36.020Z <Structure:null> Module Structure v24099 [latest-24115]2024-05-28T14:42:36.021Z <Capabilities:null> Module Capabilities v23331 [latest-24115]2024-05-28T14:42:36.028Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 24108 revision 1 [latest-24115]2024-05-28T14:42:36.035Z <Plugin:null> Module Plugin v22300 [latest-24115]2024-05-28T14:42:36.038Z <TimerBroker:null> Module TimerBroker v22283 [latest-24115]2024-05-28T14:42:36.039Z <Entity:null> Module Entity v24108 [latest-24115]2024-05-28T14:42:36.041Z <Controller:null> Module Controller v24099 [latest-24115]2024-05-28T14:42:36.047Z <default:null> Module Ruleset v24099 [latest-24115]2024-05-28T14:42:36.047Z <default:null> Module Rulesets v24099 [latest-24115]2024-05-28T14:42:36.050Z <GlobalExpression:null> Module GlobalExpression v24099 [latest-24115]2024-05-28T14:42:36.056Z <Predicate:null> Module Predicate v23093 [latest-24115]2024-05-28T14:42:36.058Z <AlertManager:null> Module AlertManager v24099 [latest-24115]2024-05-28T14:42:36.060Z <Rule:null> Module Rule v24115 [latest-24115]2024-05-28T14:42:36.061Z <GlobalReaction:null> Module GlobalReaction v24099 [latest-24115]2024-05-28T14:42:36.062Z <Engine:null> Module Engine v24099 [latest-24115]2024-05-28T14:42:36.064Z <httpapi:null> Module httpapi v24099 [latest-24115]2024-05-28T14:42:36.072Z <wsapi:null> Module wsapi v24115 [latest-24115]2024-05-28T14:42:36.072Z <app:NOTICE> Starting Structure... [latest-24115]2024-05-28T14:42:36.075Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-24115]2024-05-28T14:42:36.092Z <TaskQueue:null> Module TaskQueue 21351 [latest-24115]2024-05-28T14:42:36.093Z <VeraController:null> Module VeraController v24050 [latest-24115]2024-05-28T14:42:36.144Z <Structure:INFO> Structure#1 loading controller interface ezlo (EzloController) [latest-24115]2024-05-28T14:42:36.150Z <EzloController:null> Module EzloController v23345 [latest-24115]2024-05-28T14:42:36.153Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-24115]2024-05-28T14:42:36.155Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-24115]2024-05-28T14:42:36.159Z <Structure:INFO> Structure#1 loading controller interface virtual (VirtualEntityController) [latest-24115]2024-05-28T14:42:36.162Z <VirtualEntityController:null> Module VirtualEntityController v24076 [latest-24115]2024-05-28T14:42:36.164Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-24115]2024-05-28T14:42:36.168Z <HassController:null> Module HassController v24115 [latest-24115]2024-05-28T14:42:36.217Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-24115]2024-05-28T14:42:36.218Z <SystemController:null> Module SystemController v24076 [latest-24115]2024-05-28T14:42:36.220Z <Structure:INFO> Structure#1 loading controller interface mosquitto-mqtt (MQTTController) [latest-24115]2024-05-28T14:42:36.223Z <MQTTController:null> Module MQTTController v24144 [latest-24115]2024-05-28T14:42:36.252Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24115]2024-05-28T14:42:36.263Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-24115]2024-05-28T14:42:36.263Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24115]2024-05-28T14:42:36.267Z <Structure:INFO> Starting controller VeraController#vera [latest-24115]2024-05-28T14:42:36.268Z <VeraController:NOTICE> VeraController#vera starting... [latest-24115]2024-05-28T14:42:36.270Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.283Z <Controller:INFO> VeraController#vera loaded implementation data ver 23109 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.283Z <Structure:INFO> Starting controller EzloController#ezlo [latest-24115]2024-05-28T14:42:36.284Z <Controller:INFO> EzloController#ezlo loaded ezlo capabilities ver 22266 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.288Z <Controller:INFO> EzloController#ezlo loaded implementation data ver 22344 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.288Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-24115]2024-05-28T14:42:36.290Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-24115]2024-05-28T14:42:36.290Z <Structure:INFO> Starting controller VirtualEntityController#virtual [latest-24115]2024-05-28T14:42:36.291Z <Controller:INFO> VirtualEntityController#virtual loaded virtualentity capabilities ver 22263 rev 2 format 1 [latest-24115]2024-05-28T14:42:36.291Z <Controller:INFO> VirtualEntityController#virtual loaded implementation data ver 22280 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.291Z <Structure:INFO> Starting controller HassController#hass [latest-24115]2024-05-28T14:42:36.291Z <HassController:NOTICE> HassController#hass starting... [latest-24115]2024-05-28T14:42:36.292Z <Controller:INFO> HassController#hass loaded hass capabilities ver 23289 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.295Z <Controller:INFO> HassController#hass loaded implementation data ver 24004 rev 3 format 1 [latest-24115]2024-05-28T14:42:36.295Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-24115]2024-05-28T14:42:36.296Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-24115]2024-05-28T14:42:36.337Z <Structure:INFO> Starting controller MQTTController#mosquitto-mqtt [latest-24115]2024-05-28T14:42:36.338Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.338Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.338Z <Structure:INFO> Starting controller MQTTController#mqtt [latest-24115]2024-05-28T14:42:36.338Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt [latest-24115]2024-05-28T14:42:36.338Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt_device [latest-24115]2024-05-28T14:42:36.338Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt [latest-24115]2024-05-28T14:42:36.339Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt_device [latest-24115]2024-05-28T14:42:36.339Z <Controller:INFO> MQTTController#mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.339Z <Controller:INFO> MQTTController#mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.341Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-24115]2024-05-28T14:42:36.341Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-24115]2024-05-28T14:42:36.342Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking... [latest-24115]2024-05-28T14:42:36.342Z <EzloController:WARN> EzloController: implementation of capability battery_maintenance does not provide attribute state [latest-24115]2024-05-28T14:42:36.343Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-24115]2024-05-28T14:42:36.343Z <HassController:WARN> HassController: implementation of capability light_effect does not provide attribute speed [latest-24115]2024-05-28T14:42:36.344Z <HassController:WARN> HassController: implementation of capability battery_maintenance does not provide attribute state [latest-24115]2024-05-28T14:42:36.344Z <HassController:WARN> HassController: implementation of capability input_select.selector does not provide attribute values [latest-24115]2024-05-28T14:42:36.355Z <EzloController:INFO> EzloController#ezlo: connecting to hub "xxxxxxxx" via anonymous local connection to wss://xxx.xxx.xxx.xxx [latest-24115]2024-05-28T14:42:36.358Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Dyr El (dyrEl) [latest-24115]2024-05-28T14:42:36.365Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Solar Production Forecast (solar_production_forecast) [latest-24115]2024-05-28T14:42:36.369Z <Controller:INFO> VirtualEntityController#virtual 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.369Z <HassController:NOTICE> HassController#hass connecting to ws://xxx.xxx.xxx.xxx/api/websocket [latest-24115]2024-05-28T14:42:36.371Z <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-24115]2024-05-28T14:42:36.372Z <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-24115]2024-05-28T14:42:36.372Z <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-24115]2024-05-28T14:42:36.372Z <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_puls ar_plus [latest-24115]2024-05-28T14:42:36.372Z <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 defin ition xiaofang_motion_light_sensor [latest-24115]2024-05-28T14:42:36.374Z <Controller:NOTICE> Controller VirtualEntityController#virtual is now online. [latest-24115]2024-05-28T14:42:36.394Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-24115]2024-05-28T14:42:36.396Z <HassController:INFO> HassController#hass successful authentication with ws://xxx.xxx.xxx.xxx; fetching initial data... [latest-24115]2024-05-28T14:42:36.400Z <HassController:INFO> HassController#hass Hass reports version "2024.5.5" location Hem timezone Europe/Stockholm state RUNNING safe_mode false [latest-24115]2024-05-28T14:42:36.402Z <HassController:ERR> HassController#hass reported Hass version "2024.5.5" is not supported! [latest-24115]2024-05-28T14:42:36.403Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_control_outlet.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_trad fri.zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_control_outlet.yaml overrides existing template definition zigbee2mqtt_tradfri_control_outlet [latest-24115]2024-05-28T14:42:36.405Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri. zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb [latest-24115]2024-05-28T14:42:36.405Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri. zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_d [latest-24115]2024-05-28T14:42:36.416Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_supervisor_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_core_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.terminal_ssh_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.esphome_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.file_editor_update [latest-24115]2024-05-28T14:42:36.418Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_operating_system_update [latest-24115]2024-05-28T14:42:36.418Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-24115]2024-05-28T14:42:36.420Z <HassController:NOTICE> HassController#hass no signature match for conversation.home_assistant [latest-24115]2024-05-28T14:42:36.420Z <HassController:NOTICE> HassController#hass no signature match for remote.samsung_vardagsrummet [latest-24115]2024-05-28T14:42:36.457Z <HassController:NOTICE> HassController#hass no signature match for update.infopanel_hall_firmware [latest-24115]2024-05-28T14:42:36.465Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.466Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradf ri.zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws [latest-24115]2024-05-28T14:42:36.466Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradf ri.zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws_d [latest-24115]2024-05-28T14:42:36.466Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_door_sensor.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_door_sensor.yaml overrides existing temp late definition zigbee2mqtt_tuya_door_sensor [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_light_bulb_rgbcw.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_light_bulb_rgbcw.yaml overrides exi sting template definition zigbee2mqtt_tuya_light_bulb_rgbcw [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml ove rrides existing template definition zigbee2mqtt_tuya_motion_light_sensor [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml ove rrides existing template definition zigbee2mqtt_tuya_light_motion_sensor [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-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-24115]2024-05-28T14:42:36.528Z <Controller:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.529Z <Controller:NOTICE> Controller VeraController#vera is now online. [latest-24115]2024-05-28T14:42:36.531Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-24115]2024-05-28T14:42:36.533Z <EzloController:INFO> EzloController#ezlo: successful unauthenticated local connection to "xxxxxxx" [latest-24115]2024-05-28T14:42:36.534Z <EzloController:INFO> EzloController#ezlo starting hub inventory [latest-24115]2024-05-28T14:42:36.535Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_xiaomi_aqara_mini_switch.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_a qara_mini_switch.yaml overrides existing template definition zigbee2mqtt_aqara_mini_switch [latest-24115]2024-05-28T14:42:36.537Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqt t_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_motion_light_sensor [latest-24115]2024-05-28T14:42:36.537Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqt t_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_light_motion_sensor [latest-24115]2024-05-28T14:42:36.538Z <MQTTController:INFO> MQTTController#mqtt instance topic ident is mqtt [latest-24115]2024-05-28T14:42:36.540Z <MQTTController:ERR> MQTTController#mqtt error initializing entity takflakt_kallare: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.540Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.541Z <MQTTController:ERR> MQTTController#mqtt error initializing entity kaminflakt: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.541Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.542Z <MQTTController:ERR> MQTTController#mqtt error initializing entity kallartemp: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.542Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.543Z <MQTTController:ERR> MQTTController#mqtt error initializing entity fasadvedbod: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.543Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.544Z <MQTTController:ERR> MQTTController#mqtt error initializing entity fasadgarage: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.544Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.545Z <MQTTController:ERR> MQTTController#mqtt error initializing entity draneringspump: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.545Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) ... "same error for all configured MQTT entities" ... [latest-24115]2024-05-28T14:42:36.642Z <Controller:INFO> MQTTController#mosquitto-mqtt 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.642Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt connecting to broker at mqtt://xxx.xxx.xxx.xxx/ [latest-24115]2024-05-28T14:42:36.643Z <app:NOTICE> Starting HTTP server and API... [latest-24115]2024-05-28T14:42:36.645Z <httpapi:NOTICE> httpapi: starting HTTP service on port 8111 [latest-24115]2024-05-28T14:42:36.647Z <app:NOTICE> Starting Reaction Engine... [latest-24115]2024-05-28T14:42:36.648Z <Engine:INFO> Reaction Engine starting [latest-24115]2024-05-28T14:42:36.648Z <Engine:INFO> Checking rule sets... [latest-24115]2024-05-28T14:42:36.649Z <Engine:INFO> Checking rules... [latest-24115]2024-05-28T14:42:36.692Z <Engine:INFO> Data check complete; no corrections.

I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).

Anyway, here's my reactor-mqtt-contrib package:

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

Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

Simply download yaml files (everything or just the ones you need) and you're good to go.

I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.

The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.

Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂

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: ValueSensor

Specifically, 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?

e7f2ffa6-0ae2-4137-9238-65868d9a9f50-image.png

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.1

I'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.35

The 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.