Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
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
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullI'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 🙂
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.Hi @toggledbits.
After a couple of weeks, I noticed that my Remotec zrc90 isn't working as expected.
Scenes are working in ZWaveJS, but this device has a strange behavior: the scene change, but then it's set again to null. In Reactor, this remains null:
battery_power.level=0.7 battery_power.since=1725817957361 x_debug.dt={"description":"Scene master 8 button remote","model":"BW8510/ZRC-90US","default_name":"Scene master 8 button remote","manufacturerId":21076,"productType":0,"productId":34064} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=70 x_zwave_values.Central_Scene_scene_001=null x_zwave_values.Central_Scene_scene_002=null x_zwave_values.Central_Scene_scene_003=null x_zwave_values.Central_Scene_scene_004=null x_zwave_values.Central_Scene_scene_005=null x_zwave_values.Central_Scene_scene_006=null x_zwave_values.Central_Scene_scene_007=null x_zwave_values.Central_Scene_scene_008=null x_zwave_values.Central_Scene_slowRefresh=null x_zwave_values.Manufacturer_Specific_manufacturerId=21076 x_zwave_values.Manufacturer_Specific_productId=34064 x_zwave_values.Manufacturer_Specific_productType=1 x_zwave_values.Version_firmwareVersions=["1.1","1.1"] x_zwave_values.Version_hardwareVersion=3 x_zwave_values.Version_libraryType=2 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=0 zwave_device.capabilities=[91,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Remote Controller" zwave_device.impl_sig="24242:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=false zwave_device.is_secure=false zwave_device.manufacturer_info=[21076,1,34064] zwave_device.max_data_rate=null zwave_device.node_id=154 zwave_device.specific_class="Simple Remote Control" zwave_device.status=2 zwave_device.status_text="awake" zwave_device.version_info=[null,"1.1"] zwave_device.wakeup_interval=0Anything I could look at? Thanks.
Hi, @toggledbits!
I have a question about the execution behavior. See the code below, and I'll explain the situation.
12957c3e-ff06-46c9-929d-b53f936665df-image.png
This is a routine that, at a certain point, determines that the desktop on which the VM hosting the Reactor is located receives an instruction to perform a shutdown (Shell Command).
When this happens, the desktop is turned off, and then Hubitat detects by a "ping" that the VM has been down, waits 15 seconds, turns off the power to this desktop, and then 15 seconds later turns on the desktop with the Reactor VM again.
After restarting the desktop, the VM is loaded, and the Reactor is triggered. Still, the following problem occurs: I expected that when the rule was continued to be executed again, the next step would be executed, that of the 900-second delay after shutdown, but the Shell command is executed again, and then it goes into a loop, the rule does not advance.
To break the loop, I first have to make the VM not load, change the desktop password, and then start the VM. In this case, Reactor generates an error when trying to execute the Shell Command because of the invalid password and then finishes the routine following the 900 delay step.
b58b0d4a-d6c1-4fe3-bab7-4222acea9607-image.png
Is my interpretation that when it returns, the routine should continue to the next step that has not yet been executed incorrectly? Or does Reactor, through the shutdown command, interpret that it hasn't finished this step and keep trying, which is the correct reaction?
Thanks for clarifying.
Hi @toggledbits ,
I'm slowly moving my ZWave network from Vera to ZWaveJS. I successfully cloned my ZWave network using a spare Vera Edge (a new post for the community later when I'll be fully back from vacation) and I'm testing a couple of things before moving everything to ZWaveJS.
In the meanwhile, I have a couple of venetian blinds connected to Fibaro Roller Shutters 2 (FGR222) and I'm using some proprietary ZWave commands to control the tilt position, that right now I'm sending via Vera (with some code from the old place, messing with this):
af7f883c-f49e-419c-a2fe-8669572e3792-image.png
The ZWaveJS values are reported via this:
x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=0 x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsTilt=0I hope there's a way to expose a separate device to control the tilt position directly, without doing the mess I'm doing now. Let me know if you need some files. Thanks.
As per @toggledbits request, new topic.
Position and cover commands not working and position/cover attributes are incorrect. Dimming is OK.
cover.state=null dimming.level=1 dimming.step=0.1 energy_sensor.units="kWh" energy_sensor.value=0.41 position.value=null power_sensor.units="W" power_sensor.value=0 power_switch.state=true x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state"} x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=0.41 x_zwave_values.Meter_value_66049=0 x_zwave_values.Multilevel_Switch_Down=null x_zwave_values.Multilevel_Switch_Up=null x_zwave_values.Multilevel_Switch_currentValue=99 x_zwave_values.Multilevel_Switch_duration="unknown" x_zwave_values.Multilevel_Switch_restorePrevious=null x_zwave_values.Multilevel_Switch_targetValue=99 x_zwave_values.Notification_Power_Management_Over_current_status=0 x_zwave_values.Notification_System_Hardware_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null zwave_device.capabilities=[38,50,113] zwave_device.endpoint=1 zwave_device.failed=null zwave_device.impl_sig="24225:1:22315:1" zwave_device.manufacturer_info=null zwave_device.node_id=148 zwave_device.version_info=nullThanks!
Another one for you, @toggledbits.
I have two water sensors (same device, NAS-WS01Z), but one is reporting leak_detector.state=true even if no alarm is detected (I double checked from ZWaveJS UI):
battery_power.level=0.86 battery_power.since=null leak_detector.state=true x_debug.dt={"entity_class":"Notification Sensor","match":"deviceClass.generic.key=7"} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=86 x_zwave_values.Binary_Sensor_Water=false x_zwave_values.Configuration_Alarm_Activity_Duration=5 x_zwave_values.Configuration_Alarm_Beep=1 x_zwave_values.Configuration_Alarm_Duration=120 x_zwave_values.Configuration_Alarm_Interval=null x_zwave_values.Configuration_Basic_Set_Level=255 x_zwave_values.Configuration_First_Alarm_Activity_Duration=null x_zwave_values.Configuration_Water_Detection=1 x_zwave_values.Manufacturer_Specific_manufacturerId=600 x_zwave_values.Manufacturer_Specific_productId=4229 x_zwave_values.Manufacturer_Specific_productType=3 x_zwave_values.Notification_Water_Alarm_Sensor_status=null x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=null x_zwave_values.Version_hardwareVersion=null x_zwave_values.Version_libraryType=null x_zwave_values.Version_protocolVersion=null x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=43200 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="24225:1:22315: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=1724143899220 zwave_device.manufacturer_info=[600,3,4229] zwave_device.max_data_rate=null zwave_device.node_id=114 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,null] zwave_device.wakeup_interval=43200here's the other one, correctly report the leak status:
battery_power.level=1 battery_power.since=null leak_detector.state=false x_debug.dt={"entity_class":"Notification Sensor","match":"deviceClass.generic.key=7"} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=100 x_zwave_values.Binary_Sensor_Water=false x_zwave_values.Configuration_Alarm_Activity_Duration=5 x_zwave_values.Configuration_Alarm_Beep=1 x_zwave_values.Configuration_Alarm_Duration=120 x_zwave_values.Configuration_Alarm_Interval=1 x_zwave_values.Configuration_Basic_Set_Level=255 x_zwave_values.Configuration_First_Alarm_Activity_Duration=60 x_zwave_values.Configuration_Water_Detection=1 x_zwave_values.Manufacturer_Specific_manufacturerId=600 x_zwave_values.Manufacturer_Specific_productId=4229 x_zwave_values.Manufacturer_Specific_productType=3 x_zwave_values.Notification_Water_Alarm_Sensor_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null x_zwave_values.Version_firmwareVersions=["2.54"] x_zwave_values.Version_hardwareVersion=48 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=43200 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="24225:1:22315: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=1724105239533 zwave_device.manufacturer_info=[600,3,4229] zwave_device.max_data_rate=null zwave_device.node_id=113 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,"2.54"] zwave_device.wakeup_interval=43200Also, both seems to have no primary value. Thanks.
Hi-
I have an android media player entity publishing from HA. I watch for changes in transport state and media title to trigger some actions.
Though those attributes report as expected, the set rule is being throttled for possible flapping.
There is an attribute for media position that continually updates, I suspect it is causing the evaluations to run constantly.
The workaround I am seeking is to ignore those attributes in HA or MSR. Anyone know how, or have a better idea??
Thx
Btw- this problem has spanned versions of HA and reactor, but I am current on both. Too current on HA for transparency, but the issue has survived several updates.
Referencing an expression inside a reaction is in the form of ${{ expression }}. When referenced inside my shell command to set the watering delay duration for my Rachio sprinkler system, it just does not work.
If I enter "86400" instead of referencing the expression lWateringDelayDuration, it works. Either I am doing something wrong or referencing an expression inside a shell command is not supported.
Reactor version: 24212
Local Expression
lWateringDelayDuration =
Setting Reaction using Shell command
curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer xxxxxxxxxx -d '{ "id" : "xxxxxxxxxx", "duration" : ${{ lWateringDelayDuration}} }' https://api.rach.io/1/public/device/rain_delayThanks in advance
As per @toggledbits request, here's a new topic.
My Fibaro Door Window Sensor 2 (FGDW002) is always reporting as open, even if
x_zwave_values.Notification_Access_Control_Door_state=23 x_zwave_values.Notification_Access_Control_Door_state_simple=23which means that the door is closed. It was working before and I could downgrade to test, if necessary. Thanks.
Hi @toggledbits,
I'm not sure if it's a bug or something, but I have a lot of Fibaro Double Switch (FGS223) as follows.
In the example, it's zwavejs>65-2:
energy_sensor.units="kWh" energy_sensor.value=0.21 power_sensor.units="W" power_sensor.value=0 power_switch.state=false x_debug.dt={"entity_class":"Switch","match":"deviceClass.generic.key=16","capabilities":["power_switch","toggle"],"primary_attribute":"power_switch.state"} x_zwave_values.Binary_Switch_currentValue=false x_zwave_values.Binary_Switch_targetValue=false x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=0.21 x_zwave_values.Meter_value_66049=0 zwave_device.capabilities=[37,50] zwave_device.endpoint=2 zwave_device.failed=null zwave_device.impl_sig="23326:1:22315:1" zwave_device.manufacturer_info=null zwave_device.node_id=65 zwave_device.version_info=nullWhen operating endpoint 2, it's triggered endpoint 1. Endpoint 1 is fine. This is causing a lot of troubles, as you may imagine.
Also, endpoint 0 is not really a switch, and the associated actions are not doing anything at all. Maybe these could be removed. Also, I see battery_maintenance and power_source capabilities, all with null values.
battery_maintenance.charging=null battery_maintenance.rechargeable=false battery_maintenance.replace=false battery_maintenance.state=null heat_detector.state=false power_source.source=null power_switch.state=null x_debug.dt={"entity_class":"Switch","match":"deviceClass.generic.key=16","capabilities":["power_switch","toggle"],"primary_attribute":"power_switch.state","description":"Double Switch 2","model":"FGS223","default_name":"Double Switch 2","manufacturerId":271,"productType":515,"productId":4096} x_zwave_values.Central_Scene_scene_001=null x_zwave_values.Central_Scene_scene_002=null x_zwave_values.Central_Scene_slowRefresh=null x_zwave_values.Configuration_First_Channel_Energy_Reports_Threshold=100 x_zwave_values.Configuration_First_Channel_Operating_Mode=0 x_zwave_values.Configuration_First_Channel_Power_Reports_Minimum_Time_Between_Reports=10 x_zwave_values.Configuration_First_Channel_Power_Reports_Threshold=20 x_zwave_values.Configuration_First_Channel_Pulse_Time_for_Blink_Mode=5 x_zwave_values.Configuration_First_Channel_Reaction_to_Key_S1_for_Delay_Auto_ON_OFF_Modes=0 x_zwave_values.Configuration_First_Channel_Time_Parameter_for_Delay_Auto_ON_OFF_Modes=50 x_zwave_values.Configuration_General_Purpose_Alarm_Response=3 x_zwave_values.Configuration_Include_Consumption_By_Device_Itself_in_Reports=0 x_zwave_values.Configuration_Input_Button_Switch_Configuration=2 x_zwave_values.Configuration_Key_S1_Associations_Double_Click_Value_Sent=99 x_zwave_values.Configuration_Key_S1_Associations_Send_OFF_With_Single_Click_2=0 x_zwave_values.Configuration_Key_S1_Associations_Send_ON_With_Single_Click_1=0 x_zwave_values.Configuration_Key_S1_Associations_Send_When_Double_Clicking_8=0 x_zwave_values.Configuration_Key_S1_Associations_Send_When_Holding_and_Releasing_4=0 x_zwave_values.Configuration_Key_S1_Associations_Switch_OFF_Value_Sent=0 x_zwave_values.Configuration_Key_S1_Associations_Switch_ON_Value_Sent=255 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Held_Down_and_Released_8=1 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_1_Time_1=1 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_2_Times_2=1 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_3_Times_4=1 x_zwave_values.Configuration_Key_S2_Associations_Double_Click_Value_Sent=99 x_zwave_values.Configuration_Key_S2_Associations_Send_OFF_With_Single_Click_2=0 x_zwave_values.Configuration_Key_S2_Associations_Send_ON_With_Single_Click_1=0 x_zwave_values.Configuration_Key_S2_Associations_Send_When_Double_Clicking_8=0 x_zwave_values.Configuration_Key_S2_Associations_Send_When_Holding_and_Releasing_4=0 x_zwave_values.Configuration_Key_S2_Associations_Switch_OFF_Value_Sent=0 x_zwave_values.Configuration_Key_S2_Associations_Switch_ON_Value_Sent=255 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Held_Down_and_Released_8=1 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_1_Time_1=1 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_2_Times_2=1 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_3_Times_4=1 x_zwave_values.Configuration_Periodic_Active_Power_Reports=3600 x_zwave_values.Configuration_Periodic_Energy_Reports=3600 x_zwave_values.Configuration_Report_During_Blink_Mode=0 x_zwave_values.Configuration_Second_Channel_Energy_Reports_Threshold=100 x_zwave_values.Configuration_Second_Channel_Operating_Mode=0 x_zwave_values.Configuration_Second_Channel_Power_Reports_Minimum_Time_Between_Reports=10 x_zwave_values.Configuration_Second_Channel_Power_Reports_Threshold=20 x_zwave_values.Configuration_Second_Channel_Pulse_Time_for_Blink_Mode=5 x_zwave_values.Configuration_Second_Channel_Reaction_to_Key_S2_for_Delay_Auto_ON_OFF_Modes=0 x_zwave_values.Configuration_Second_Channel_Time_Parameter_for_Delay_Auto_ON_OFF_Modes=50 x_zwave_values.Configuration_Send_Secure_Commands_to_2nd_Association_Group_1=1 x_zwave_values.Configuration_Send_Secure_Commands_to_3rd_Association_Group_2=1 x_zwave_values.Configuration_Send_Secure_Commands_to_4th_Association_Group_4=1 x_zwave_values.Configuration_Send_Secure_Commands_to_5th_Association_Group_8=1 x_zwave_values.Configuration_Smoke_CO_or_CO2_Alarm_Response=3 x_zwave_values.Configuration_State_After_Power_Failure=1 x_zwave_values.Configuration_Temperature_Alarm_Response=1 x_zwave_values.Configuration_Time_of_Alarm_State=600 x_zwave_values.Configuration_Water_Flood_Alarm_Response=2 x_zwave_values.Manufacturer_Specific_manufacturerId=271 x_zwave_values.Manufacturer_Specific_productId=4096 x_zwave_values.Manufacturer_Specific_productType=515 x_zwave_values.Notification_Heat_Alarm_Heat_sensor_status=0 x_zwave_values.Notification_Power_Management_Over_current_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null x_zwave_values.Protection_exclusiveControlNodeId=null x_zwave_values.Protection_local=0 x_zwave_values.Protection_rf=0 x_zwave_values.Protection_timeout=null x_zwave_values.Version_firmwareVersions=["3.2"] x_zwave_values.Version_hardwareVersion=3 x_zwave_values.Version_libraryType=3 x_zwave_values.Version_protocolVersion="4.5" zwave_device.capabilities=[91,112,113,114,117,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Binary Switch" 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=[271,515,4096] zwave_device.max_data_rate=null zwave_device.node_id=65 zwave_device.specific_class="Binary Power Switch" zwave_device.status=4 zwave_device.status_text="alive" zwave_device.version_info=[null,"3.2"]Thanks.
Good morning,
I'm having an issue with controlling my Zooz Zen14 outdoor double outlet. I should be able to control each outlet individually, and this does work when use Home Assistant (haas) from Reactor.
When I use zwavejs, I see 3 entries:
8305eccf-a99e-421f-ad18-1f08da9c8c9c-image.png
The first entry is for the overall device. I can turn both outlets on and off (in theory) by setting the power_switch state to on or off. This does turn them on and off when using zwavejs.
When I go to the individual outlets, performing the power_switch.on or power_switch.off actions turns them all (main, 1 and 2) on or off, and not just the individual outlets. When I perform the same action from haas, turning on outlet 1 will turn on the main switch and 1, but not 2.
I reviewed the logs for that node and I'm not seeing anything obvious.
:~/reactor/logs$ cat reactor.log.1 | grep ZWaveJSController#zwavejs | grep "node 216" [latest-24212]2024-08-07T00:19:00.233Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "endpoint": 0, "property": "targetValue", "newValue": true, "prevValue": false, "propertyName": "targetValue" } } [latest-24212]2024-08-07T00:19:00.235Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": false, "propertyName": "currentValue" } } [latest-24212]2024-08-07T00:19:00.321Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "currentValue" } } [latest-24212]2024-08-07T00:19:00.322Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "targetValue" } } [latest-24212]2024-08-07T00:19:00.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 0, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } } [latest-24212]2024-08-07T00:19:02.189Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "currentValue" } } [latest-24212]2024-08-07T00:19:02.192Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "targetValue" } } [latest-24212]2024-08-07T00:19:02.193Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 1, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } } [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 0 (entity "216-0") [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 1 (entity "216-1") [latest-24212]2024-08-07T05:32:30.128Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 2 (entity "216-2")I'm running:
Reactor (Multi-hub) latest-24212-3ce15e25
ZWaveJSController [0.1.23326] (with zwavejs_data from 7/25/2024)
HA:
Core 2024.7.3
Supervisor 2024.08.0
Operating System 12.3
Frontend 20240710.0
[Dev] Inheritance in MQTT templates?
-
That's probably more appropriate to post on Mantis for @toggledbits, but since I know there's at least @Crille publishing templates, my intent with this post is to open a broader discussion.
Long story short: I'm starting to slowly add new template for Shelly Plus and I noticed I'll end up with a dozen more templates, all similar but simply different in trivial details, all sharing a large amount of code and all needing special cares when fixing bugs/adding features (as the latest wifi_status addition).
So, I'm wondering if it's time to start thinking of some sort of inheritance in templates, where I could just create a generic shelly_gen1 and use it as a base for shelly_relay, and this be used as the base for shelly_relay_power and so on.
I could probably achieve this with some sort of scripting on my side to generate templates via code, but maybe there's a better way of doing this, or it's already on the radar.
-
Sounds great!
I thought of something like this when creating templates for combined humidity & temperature sensors where I in some locations want humidity as primary attribute and other temperature, this generates duplicate templates bundled in the same file and the only difference is theprimary_attributeor is this doable with therequires:key already?Base files for devices using the same keys would ease things up and could simply be included in a bundled zip file.
-
It's already done. Great minds think alike. I did it a couple of weeks ago, haven't released it yet. I also broke things out so that the templates can be spread out across any kind of directory structure you want to create.
I'll push it up for you.
-
@toggledbits Thanks for the quick build. I've updated to the latest version of MQTTController and I'll soon update my templates. I've found a minor problem related to custom capabilities.
In previous iteration, it was tolerated, but now it's emitting an arror (
Configuration for X is incomplete because the following requested capabilities are unrecognized: Y).Is there a way to define and pack definitions of capabilities with custom templates? Otherwise, I'll have to find an alternative way for my
shelly_hem.yaml, because I must expose 2 energy sensors in one device (one for imported, the other for exported KwH). Thanks. -
What is/are the capabilties?
-
it's a custom one, just to have two values:
https://github.com/dbochicchio/reactor-mqtt-contrib/blob/main/shelly_hem.yaml#L59-L63 -
Yes, yes, I've already looked at the definition in Github, I need you to be more specific. What are the names you redacted at Y in your previous post.
-
@toggledbits oh, my bad. I'll try to re-pro again when home, but it should be
x_energy_sensor_exportedfor Y and the device name for X. -
OK. That helps. And problem understood. I think I have an answer. New build later today.
-
OK. MQTTController build 24144 up. Adds support for a
capabilitiessection at the top level of any template file. Format is same as for system_capabilities.yaml. See MQTTController docs, updated. -
Ok, version 24146 of my templates is now ready, refactored with this new feature and starting to include Shelly Gen 3 (I've also used a couple of system templates as base).
The only minor thing is that if I have a primary_attribute defined in a template, MQTTController will not use the last one in the hierarchy, but the first one, and complain. Maybe just a brief note on the docs to highlight this.
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Thanks!
-
Quick question, looking at MQTTController integrated templates for Shelly, they are in separate files. Is it possible to define all these in one yaml file? Because I'm trying to do that for common Zigbee2MQTT capabilities and getting errors in the log that I can't figure out why. If not possible I get it but if it is possible I will elaborate my issue.
-
Yes, it's possible.
-
OK, here goes.
[1/2]
Reactor latest-24152 bare metal.
MQTTController 24144.I can't figure this out
"MQTTController:CRIT ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>sovrumsdorr [-]"reactor.log[latest-24152]2024-06-05T20:20:25.153Z <app:null> Reactor build latest-24152-3455578a starting on v20.13.1 /usr/local/bin/node [latest-24152]2024-06-05T20:20:25.153Z <app:null> Process ID 317180 user/group 1000/1000; bare-metal; platform linux/x64 #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024; locale sv_SE.utf8 [latest-24152]2024-06-05T20:20:25.154Z <app:null> Basedir /home/homebridge/reactor; data in /home/homebridge/reactor/storage [latest-24152]2024-06-05T20:20:25.154Z <app:null> NODE_PATH=/home/homebridge/reactor [latest-24152]2024-06-05T20:20:25.169Z <app:null> Resolved timezone=Europe/Stockholm, environment TZ=(undefined); offset minutes from UTC=120 [latest-24152]2024-06-05T20:20:25.171Z <app:null> Configured locale sv-SE; selected locale(s) sv-SE [latest-24152]2024-06-05T20:20:25.177Z <app:null> Loaded locale sv-SE for sv-SE [latest-24152]2024-06-05T20:20:25.178Z <app:null> Local date/time using configured timezone and locale formatting is "2024-06-05 22:20:25" [latest-24152]2024-06-05T20:20:25.180Z <Structure:null> Module Structure v24110 [latest-24152]2024-06-05T20:20:25.181Z <Capabilities:null> Module Capabilities v23331 [latest-24152]2024-06-05T20:20:25.191Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 24108 revision 1 [latest-24152]2024-06-05T20:20:25.197Z <Plugin:null> Module Plugin v22300 [latest-24152]2024-06-05T20:20:25.214Z <TimerBroker:null> Module TimerBroker v22283 [latest-24152]2024-06-05T20:20:25.216Z <Entity:null> Module Entity v24138 [latest-24152]2024-06-05T20:20:25.218Z <Controller:null> Module Controller v24099 [latest-24152]2024-06-05T20:20:25.232Z <default:null> Module Ruleset v24099 [latest-24152]2024-06-05T20:20:25.232Z <default:null> Module Rulesets v24099 [latest-24152]2024-06-05T20:20:25.250Z <GlobalExpression:null> Module GlobalExpression v24099 [latest-24152]2024-06-05T20:20:25.275Z <Predicate:null> Module Predicate v23093 [latest-24152]2024-06-05T20:20:25.277Z <AlertManager:null> Module AlertManager v24099 [latest-24152]2024-06-05T20:20:25.278Z <Rule:null> Module Rule v24149 [latest-24152]2024-06-05T20:20:25.280Z <GlobalReaction:null> Module GlobalReaction v24099 [latest-24152]2024-06-05T20:20:25.289Z <Engine:null> Module Engine v24113 [latest-24152]2024-06-05T20:20:25.292Z <httpapi:null> Module httpapi v24148 [latest-24152]2024-06-05T20:20:25.298Z <wsapi:null> Module wsapi v24148 [latest-24152]2024-06-05T20:20:25.299Z <app:NOTICE> Starting Structure... [latest-24152]2024-06-05T20:20:25.308Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-24152]2024-06-05T20:20:25.331Z <TaskQueue:null> Module TaskQueue 24138 [latest-24152]2024-06-05T20:20:25.332Z <VeraController:null> Module VeraController v24050 [latest-24152]2024-06-05T20:20:25.375Z <Structure:INFO> Structure#1 loading controller interface ezlo (EzloController) [latest-24152]2024-06-05T20:20:25.381Z <EzloController:null> Module EzloController v23345 [latest-24152]2024-06-05T20:20:25.384Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-24152]2024-06-05T20:20:25.386Z <DynamicGroupController:null> Module DynamicGroupController v24128 [latest-24152]2024-06-05T20:20:25.390Z <Structure:INFO> Structure#1 loading controller interface virtual (VirtualEntityController) [latest-24152]2024-06-05T20:20:25.393Z <VirtualEntityController:null> Module VirtualEntityController v24147 [latest-24152]2024-06-05T20:20:25.395Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-24152]2024-06-05T20:20:25.399Z <HassController:null> Module HassController v24146 [latest-24152]2024-06-05T20:20:25.450Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-24152]2024-06-05T20:20:25.452Z <SystemController:null> Module SystemController v24076 [latest-24152]2024-06-05T20:20:25.453Z <Structure:INFO> Structure#1 loading controller interface scheman (ScheduleController) [latest-24152]2024-06-05T20:20:25.455Z <ScheduleController:null> Module ScheduleController v24097 [latest-24152]2024-06-05T20:20:25.455Z <Controller:INFO> Loaded ScheduleController version "0.1.24097"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> [latest-24152]2024-06-05T20:20:25.456Z <Structure:INFO> Structure#1 loading controller interface mosquitto-mqtt (MQTTController) [latest-24152]2024-06-05T20:20:25.459Z <MQTTController:null> Module MQTTController v24144 [latest-24152]2024-06-05T20:20:25.491Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24152]2024-06-05T20:20:25.503Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-24152]2024-06-05T20:20:25.503Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24152]2024-06-05T20:20:25.507Z <Structure:INFO> Starting controller VeraController#vera [latest-24152]2024-06-05T20:20:25.507Z <VeraController:NOTICE> VeraController#vera starting... [latest-24152]2024-06-05T20:20:25.510Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.521Z <Controller:INFO> VeraController#vera loaded implementation data ver 23109 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.521Z <Structure:INFO> Starting controller EzloController#ezlo [latest-24152]2024-06-05T20:20:25.523Z <Controller:INFO> EzloController#ezlo loaded ezlo capabilities ver 22266 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.528Z <Controller:INFO> EzloController#ezlo loaded implementation data ver 22344 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.528Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-24152]2024-06-05T20:20:25.530Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-24152]2024-06-05T20:20:25.530Z <Structure:INFO> Starting controller VirtualEntityController#virtual [latest-24152]2024-06-05T20:20:25.531Z <Controller:INFO> VirtualEntityController#virtual loaded virtualentity capabilities ver 22263 rev 2 format 1 [latest-24152]2024-06-05T20:20:25.532Z <Controller:INFO> VirtualEntityController#virtual loaded implementation data ver 22280 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.532Z <Structure:INFO> Starting controller HassController#hass [latest-24152]2024-06-05T20:20:25.532Z <HassController:NOTICE> HassController#hass starting... [latest-24152]2024-06-05T20:20:25.533Z <Controller:INFO> HassController#hass loaded hass capabilities ver 23289 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.536Z <Controller:INFO> HassController#hass loaded implementation data ver 24146 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.536Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-24152]2024-06-05T20:20:25.537Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-24152]2024-06-05T20:20:25.580Z <Structure:INFO> Starting controller ScheduleController#scheman [latest-24152]2024-06-05T20:20:25.580Z <ScheduleController:INFO> ScheduleController#scheman Sun Information entity is reactor_system>sun [latest-24152]2024-06-05T20:20:25.582Z <Controller:NOTICE> Controller ScheduleController#scheman is now online. [latest-24152]2024-06-05T20:20:25.582Z <Structure:INFO> Starting controller MQTTController#mosquitto-mqtt [latest-24152]2024-06-05T20:20:25.583Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.583Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.583Z <Structure:INFO> Starting controller MQTTController#mqtt [latest-24152]2024-06-05T20:20:25.583Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt [latest-24152]2024-06-05T20:20:25.584Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt_device [latest-24152]2024-06-05T20:20:25.584Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt [latest-24152]2024-06-05T20:20:25.584Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt_device [latest-24152]2024-06-05T20:20:25.584Z <Controller:INFO> MQTTController#mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.584Z <Controller:INFO> MQTTController#mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24152]2024-06-05T20:20:25.587Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-24152]2024-06-05T20:20:25.587Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-24152]2024-06-05T20:20:25.588Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking... [latest-24152]2024-06-05T20:20:25.588Z <EzloController:WARN> EzloController: implementation of capability battery_maintenance does not provide attribute state [latest-24152]2024-06-05T20:20:25.589Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-24152]2024-06-05T20:20:25.602Z <EzloController:INFO> EzloController#ezlo: connecting to hub "xxxxxx" via anonymous local connection to wss://xxx.xxx.xxx.xxx [latest-24152]2024-06-05T20:20:25.605Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Dyr El (dyrEl) [latest-24152]2024-06-05T20:20:25.612Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Solar Production Forecast (solar_production_forecast) [latest-24152]2024-06-05T20:20:25.617Z <Controller:INFO> VirtualEntityController#virtual 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.617Z <HassController:NOTICE> HassController#hass connecting to ws://xxx.xxx.xxx.xxx/api/websocket [latest-24152]2024-06-05T20:20:25.622Z <MQTTController:WARN> MQTTController#mqtt file my_tasmota_generic_relay.yaml in /home/homebridge/reactor/config/mqtt_templates/my_tasmota_generic_relay.yaml overrides existing template definition my_tasmota_generic_relay [latest-24152]2024-06-05T20:20:25.622Z <MQTTController:WARN> MQTTController#mqtt file shelly_plug_s.yaml in /home/homebridge/reactor/config/mqtt_templates/shelly_plug_s.yaml overrides existing template definition shelly_plug_s [latest-24152]2024-06-05T20:20:25.622Z <MQTTController:WARN> MQTTController#mqtt file tasmota_sensor_lyw.yaml in /home/homebridge/reactor/config/mqtt_templates/tasmota_sensor_lyw.yaml overrides existing template definition tasmota_sensor_lyw [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file wallbox_pulsar_plus.yaml in /home/homebridge/reactor/config/mqtt_templates/wallbox_pulsar_plus.yaml overrides existing template definition wallbox_pulsar_plus [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file xiaofang_motion_light_sensor.yaml in /home/homebridge/reactor/config/mqtt_templates/xiaofang_motion_light_sensor.yaml overrides existing template definition xiaofang_motion_light_sensor [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_availability [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_availability_no_get [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_lqi [latest-24152]2024-06-05T20:20:25.623Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_ota [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_power_switch [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_dimming [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_common.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml overrides existing template definition zigbee2mqtt_battery_power [latest-24152]2024-06-05T20:20:25.624Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_control_outlet.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_control_outlet.yaml overrides existing template definition zigbee2mqtt_tradfri_control_outlet [latest-24152]2024-06-05T20:20:25.625Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb [latest-24152]2024-06-05T20:20:25.625Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_d [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws_d [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_door_sensor.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_door_sensor.yaml overrides existing template definition zigbee2mqtt_tuya_door_sensor [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_light_bulb_rgbcw.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_light_bulb_rgbcw.yaml overrides existing template definition zigbee2mqtt_tuya_light_bulb_rgbcw [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_tuya_motion_light_sensor [latest-24152]2024-06-05T20:20:25.626Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_tuya_light_motion_sensor [latest-24152]2024-06-05T20:20:25.627Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_tuya_smart_plug_pm.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_smart_plug_pm.yaml overrides existing template definition zigbee2mqtt_tuya_smart_plug_pm [latest-24152]2024-06-05T20:20:25.628Z <Controller:NOTICE> Controller VirtualEntityController#virtual is now online. [latest-24152]2024-06-05T20:20:25.642Z <ScheduleController:INFO> ScheduleController#scheman entity ValueSensor#scheman>weekends edge "22:00" active, setting primary attribute value to natt [latest-24152]2024-06-05T20:20:25.651Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-24152]2024-06-05T20:20:25.654Z <HassController:INFO> HassController#hass successful authentication with ws://xxx.xxx.xxx.xxx; fetching initial data... [latest-24152]2024-06-05T20:20:25.658Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_mini_switch.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_mini_switch.yaml overrides existing template definition zigbee2mqtt_aqara_mini_switch [latest-24152]2024-06-05T20:20:25.658Z <HassController:INFO> HassController#hass Hass reports version "2024.5.5" location Hem timezone Europe/Stockholm state RUNNING safe_mode false [latest-24152]2024-06-05T20:20:25.661Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_motion_light_sensor [latest-24152]2024-06-05T20:20:25.661Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_light_motion_sensor [latest-24152]2024-06-05T20:20:25.664Z <MQTTController:INFO> MQTTController#mosquitto-mqtt instance topic ident is mosquitto-mqtt [latest-24152]2024-06-05T20:20:25.669Z <Controller:INFO> MQTTController#mosquitto-mqtt 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.669Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt connecting to broker at mqtt://127.0.0.1:1885/ [latest-24152]2024-06-05T20:20:25.686Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml overrides existing template definition zigbee2mqtt_aqara_sensor_temperature_humidity [latest-24152]2024-06-05T20:20:25.686Z <MQTTController:WARN> MQTTController#mqtt file zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_aqara_temperature_humidity.yaml overrides existing template definition zigbee2mqtt_aqara_sensor_humidity_temperature [latest-24152]2024-06-05T20:20:25.687Z <MQTTController:INFO> MQTTController#mqtt instance topic ident is mqtt [latest-24152]2024-06-05T20:20:25.689Z <Controller:INFO> MQTTController#mqtt 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.689Z <MQTTController:NOTICE> MQTTController#mqtt connecting to broker at mqtt://127.0.0.1:1888/ [latest-24152]2024-06-05T20:20:25.690Z <app:NOTICE> Starting HTTP server and API... [latest-24152]2024-06-05T20:20:25.692Z <httpapi:NOTICE> [HTTPAPI]#1 starting HTTP service on port 8111 [latest-24152]2024-06-05T20:20:25.695Z <app:NOTICE> Starting Reaction Engine... [latest-24152]2024-06-05T20:20:25.695Z <Engine:INFO> Reaction Engine starting [latest-24152]2024-06-05T20:20:25.696Z <Engine:INFO> Checking rule sets... [latest-24152]2024-06-05T20:20:25.697Z <Engine:INFO> Checking rules... [latest-24152]2024-06-05T20:20:25.750Z <Engine:INFO> Data check complete; no corrections. --- Rules redacted to posting limits [latest-24152]2024-06-05T20:20:25.883Z <httpapi:NOTICE> [HTTPAPI]#1 HTTP server listening on "0.0.0.0":8111 [latest-24152]2024-06-05T20:20:25.896Z <httpapi:INFO> [HTTPAPI]#1 local docs found in /home/homebridge/reactor/docs/html; setting up static service [latest-24152]2024-06-05T20:20:25.897Z <app:NOTICE> Starting WSAPI... [latest-24152]2024-06-05T20:20:25.898Z <wsapi:NOTICE> wsapi: starting version 24148 [latest-24152]2024-06-05T20:20:25.919Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "2024-06-05 22:20:25" (TZ offset 120 mins from UTC) [latest-24152]2024-06-05T20:20:25.966Z <Controller:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:25.968Z <Controller:NOTICE> Controller VeraController#vera is now online. [latest-24152]2024-06-05T20:20:25.973Z <MQTTController:INFO> MQTTController#mosquitto-mqtt connected; opening subscriptions [latest-24152]2024-06-05T20:20:25.978Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_supervisor_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_core_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.terminal_ssh_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.esphome_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.file_editor_update [latest-24152]2024-06-05T20:20:25.979Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_operating_system_update [latest-24152]2024-06-05T20:20:25.980Z <HassController:NOTICE> HassController#hass no signature match for conversation.home_assistant [latest-24152]2024-06-05T20:20:25.980Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-24152]2024-06-05T20:20:25.982Z <HassController:NOTICE> HassController#hass no signature match for remote.samsung_vardagsrummet [latest-24152]2024-06-05T20:20:26.005Z <HassController:NOTICE> HassController#hass no signature match for update.infopanel_hall_firmware [latest-24152]2024-06-05T20:20:26.009Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-24152]2024-06-05T20:20:26.020Z <MQTTController:INFO> MQTTController#mosquitto-mqtt sending inits and going online! [latest-24152]2024-06-05T20:20:26.021Z <Controller:NOTICE> Controller MQTTController#mosquitto-mqtt is now online. [latest-24152]2024-06-05T20:20:26.025Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyix3-98CDAC2F5883/online) for ljussensor [latest-24152]2024-06-05T20:20:26.026Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyplug-s-80646F811E35/online) for server [latest-24152]2024-06-05T20:20:26.029Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending shellies/shellyplug-s-80646F811E35/command with 6 byte payload to server [latest-24152]2024-06-05T20:20:26.033Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending shellies/shellyuni-C45BBE6C6DE8/command with 6 byte payload to poolvarmepump [latest-24152]2024-06-05T20:20:26.034Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Datarummet/get with 12 byte payload to datarummet [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Sovrummet/get with 12 byte payload to sovrummet [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Milia/get with 12 byte payload to milia [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Hallen 1/get with 12 byte payload to hallen1 [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Hallen 2/get with 12 byte payload to hallen2 [latest-24152]2024-06-05T20:20:26.035Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Hallen 3/get with 12 byte payload to hallen3 [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Fönster köket/get with 12 byte payload to fonster_koket [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Soffan/get with 12 byte payload to soffan [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Framsida/get with 12 byte payload to framsida [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Skänk/get with 12 byte payload to skank [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Baksida/get with 12 byte payload to baksida [latest-24152]2024-06-05T20:20:26.036Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa spel/get with 12 byte payload to lampa_spel [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Ellas rum/get with 12 byte payload to lampa_ella [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa gym/get with 12 byte payload to lampa_gym [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa TV/get with 12 byte payload to lampa_tv [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Vitrinskåp/get with 12 byte payload to vitrinskap [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending shellies/shelly1-34945471EBCF/relay/0/command with 6 byte payload to vvb [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Framsida/get with 12 byte payload to jul_framsida [latest-24152]2024-06-05T20:20:26.037Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Köket/get with 12 byte payload to jul_köket [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Sovrummet/get with 12 byte payload to jul_sovrummet [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Jul Datarummet/get with 12 byte payload to jul_datarummet [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Element gillestugan/get with 12 byte payload to element_gillestugan [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Växtbelysning källare/get with 12 byte payload to vaxtbelysning_kallare [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Kompressor/get with 12 byte payload to kompressor [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Luftrenare/get with 12 byte payload to luftrenare [latest-24152]2024-06-05T20:20:26.038Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Uttag uterummet/get with 12 byte payload to uttag_uterummet [latest-24152]2024-06-05T20:20:26.039Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Entrebelysning/get with 12 byte payload to entrebelysning [latest-24152]2024-06-05T20:20:26.039Z <MQTTController:INFO> MQTTController#mosquitto-mqtt x_mqtt_device.poll action sending zigbee2mqtt/Lampa uterummet/get with 12 byte payload to lampa_uterummet [latest-24152]2024-06-05T20:20:26.050Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-24152]2024-06-05T20:20:26.051Z <MQTTController:INFO> MQTTController#mqtt connected; opening subscriptions [latest-24152]2024-06-05T20:20:26.062Z <MQTTController:ERR> MQTTController#mosquitto-mqtt event handler failed for zigbee2mqtt/Rörelse förrådet on rorelse_forradet: [ReferenceError] Capability string_sensor not extended (mosquitto-mqtt>rorelse_forradet [-] [latest-24152]2024-06-05T20:20:26.062Z <MQTTController:CRIT> ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>rorelse_forradet [-] ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>rorelse_forradet at Entity.setAttribute (/home/homebridge/reactor/server/lib/Entity.js:465:19) at MQTTController.handle_event (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:1240:19) at MqttClient.<anonymous> (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:591:38) at MqttClient.emit (node:events:519:28) at MqttClient.emit (node:domain:488:12) at MqttClient._handlePublish (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:1551:12) at MqttClient._handlePacket (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:533:12) at work (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:436:12) at process.processTicksAndRejections (node:internal/process/task_queues:77:11) [latest-24152]2024-06-05T20:20:26.063Z <MQTTController:ERR> MQTTController#mosquitto-mqtt event handler failed for zigbee2mqtt/Sovrumsdörr on sovrumsdorr: [ReferenceError] Capability string_sensor not extended (mosquitto-mqtt>sovrumsdörr [-] [latest-24152]2024-06-05T20:20:26.063Z <MQTTController:CRIT> ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>sovrumsdorr [-] ReferenceError: Capability string_sensor not extended (mosquitto-mqtt>sovrumsdorr at Entity.setAttribute (/home/homebridge/reactor/server/lib/Entity.js:465:19) at MQTTController.handle_event (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:1240:19) at MqttClient.<anonymous> (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:591:38) at MqttClient.emit (node:events:519:28) at MqttClient.emit (node:domain:488:12) at MqttClient._handlePublish (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:1551:12) at MqttClient._handlePacket (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:533:12) at work (/home/homebridge/reactor/config/ext/MQTTController/node_modules/mqtt/lib/client.js:436:12) at process.processTicksAndRejections (node:internal/process/task_queues:77:11) [latest-24152]2024-06-05T20:20:26.071Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyuni-C45BBE6C6DE8/online) for poolvarmepump [latest-24152]2024-06-05T20:20:26.072Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt received LWT (shellies/shellyplug-s-80646F811E35/online) for server [latest-24152]2024-06-05T20:20:26.074Z <MQTTController:INFO> MQTTController#mqtt sending inits and going online! [latest-24152]2024-06-05T20:20:26.075Z <Controller:NOTICE> Controller MQTTController#mqtt is now online.reactor.yaml"sovrumsdorr": name: "Sovrumsdörr" topic: "Sovrumsdörr" include: zigbee2mqtt_tuya_door_sensor -
[2/2]
zigbee2mqtt_common.yaml# Requires: "topic". # Optional: "prefix" (default: zigbee2mqtt). # mqtt_device.online requires "availability: true" in Zigbee2MQTT config. # https://www.zigbee2mqtt.io/guide/configuration/device-availability.html description: "Zigbee2MQTT base templates" author: "@Crille, Smart Home Community" license: MIT repository: "https://github.com/calmen77/MSR-mqtt_templates" version: 24155 templates: # Availability with query zigbee2mqtt_availability: capabilities: [x_mqtt_device] requires: [topic] query: topic: "%prefix:zigbee2mqtt%/%topic%/get" payload: state: "" type: json events: "%prefix:zigbee2mqtt%/%topic%/availability": "x_mqtt_device.online": if_expr: '! isnull(payload)' expr: 'lower(payload) == "online"' # Availability without query for device not supporting /get zigbee2mqtt_availability_no_get: capabilities: [x_mqtt_device] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%/availability": "x_mqtt_device.online": if_expr: '! isnull(payload)' expr: 'lower(payload) == "online"' # Link quality in lqi zigbee2mqtt_lqi: capabilities: [value_sensor] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "value_sensor.value": json_payload: true if_expr: '! isnull(payload)' expr: 'payload.linkquality' "value_sensor.units": "lqi" # String sensor for available OTA update for device zigbee2mqtt_ota: capabilities: [string_sensor] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "string_sensor.value": json_payload: true if_expr: '! isnull(payload)' expr: 'payload?.update_available ? "OTA firmware update available!" : "no update available"' # Power switch capability zigbee2mqtt_power_switch: capabilities: - power_switch - toggle requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "power_switch.state": json_payload: true expr: 'payload?.state == "ON"' actions: power_switch: "on": topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: "ON" "off": topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: "OFF" set: topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: expr: "parameters.state ? 'on' : 'off'" type: raw # Dimming capability zigbee2mqtt_dimming: capabilities: [dimming] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "dimming.level": json_payload: true expr: 'round(payload?.brightness / 100 / 2.55 , 2)' actions: dimming: set: topic: "%prefix:zigbee2mqtt%/%topic%/set" payload: expr: '{"brightness": round(parameters.level * 100 * 2.55 , 2)}' type: json # Battery level zigbee2mqtt_battery_power: capabilities: [battery_power] requires: [topic] events: "%prefix:zigbee2mqtt%/%topic%": "battery_power.level": json_payload: true expr: 'payload?.battery / 100' "battery_power.since": expr: 'time()' actions: x_mqtt_device: poll: falsezigbee2mqtt_tuya_door_sensor.yaml# Requires: "topic". # Optional: "prefix" (default: zigbee2mqtt). # mqtt_device.online requires "availability: true" in Zigbee2MQTT config. # https://www.zigbee2mqtt.io/devices/SNZB-04.html description: "Zigbee2MQTT template for TuYa Smart Door Sensor." author: "@Crille, Smart Home Community" license: MIT repository: "https://github.com/calmen77/MSR-mqtt_templates" version: 24155 templates: zigbee2mqtt_tuya_door_sensor: #type: capabilities: - door_sensor primary_attribute: door_sensor.state requires: [topic] include: - zigbee2mqtt_availability_no_get - zigbee2mqtt_lqi - zigbee2mqtt_battery_power events: "%prefix:zigbee2mqtt%/%topic%": "door_sensor.state": json_payload: true expr: 'payload?.contact' -
Turn debug level 5 on for MQTTController. It will show you how it's loading the templates and building the final entity configuration. The message fragment you'll want to look for is
merged template for sovrumsdorr... then work backwards in the log from there toconfiguring entity sovrumsdorr. Everything in between is the setup.Also examine the debug messages at startup for where it's finding templates and loading them... make sure everything it's loading is what's intended, and you don't have a stray old file sitting around somewhere that it's sucking in.
Edit: your logs are showing a lot of duplicate definitions in the startup messages...
-
It seems to merge the
events:section ofstring_sensorandpower_switchin...common.yamland wrapvalue_sensor.unitsinstring_sensorcapability.
I've looked for strange characters that could cause it but found nothing, validated all files OK in yamllint.[latest-24152]2024-06-06T06:29:11.699Z <MQTTController:5:MQTTController.js:146> MQTTController#mosquitto-mqtt configuring entity sovrumsdorr [latest-24152]2024-06-06T06:29:11.699Z <MQTTController:5:MQTTController.js:205> MQTTController#mosquitto-mqtt merged template for sovrumsdorr (from /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml/zigbee2mqtt_common.yaml): { "capabilities": [ "door_sensor", "x_mqtt_device", "value_sensor", "battery_power" ], "primary_attribute": "door_sensor.state", "requires": [ "topic" ], "include": [ "zigbee2mqtt_availability_no_get", "zigbee2mqtt_lqi", "zigbee2mqtt_battery_power", "zigbee2mqtt_tuya_door_sensor" ], "events": { "%prefix:zigbee2mqtt%/%topic%": { "door_sensor.state": { "json_payload": true, "expr": "payload?.contact" }, "value_sensor.value": { "json_payload": true, "if_expr": "! isnull(payload)", "expr": "payload.linkquality", "attribute": "value_sensor.value" }, "value_sensor.units": "lqi", "string_sensor.value": { "json_payload": true, "if_expr": "! isnull(payload)", "expr": "payload?.update_available ? \"OTA firmware update available!\" : \"no update available\"", "attribute": "string_sensor.value" }, "power_switch.state": { "json_payload": true, "expr": "payload?.state == \"ON\"", "attribute": "power_switch.state" }, "battery_power.level": { "json_payload": true, "expr": "payload?.battery / 100", "attribute": "battery_power.level" }, "battery_power.since": { "expr": "time()", "attribute": "battery_power.since" } }, "%prefix:zigbee2mqtt%/%topic%/availability": { "x_mqtt_device.online": { "if_expr": "! isnull(payload)", "expr": "lower(payload) == \"online\"", "attribute": "x_mqtt_device.online" } } }, "__source": "/home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_common.yaml/zigbee2mqtt_common.yaml", "actions": { "x_mqtt_device": { "poll": false } }, "name": "Sovrumsdörr", "topic": "Sovrumsdörr" } [latest-24152]2024-06-06T06:29:11.699Z <MQTTController:5:MQTTController.js:264> MQTTController#mosquitto-mqtt set primary attribute of door_sensor.state to Entity#mosquitto-mqtt>sovrumsdorr [latest-24152]2024-06-06T06:29:11.700Z <MQTTController:5:MQTTController.js:289> MQTTController#mosquitto-mqtt registering event handler %prefix:zigbee2mqtt%/%topic% for sovrumsdorr [latest-24152]2024-06-06T06:29:11.700Z <MQTTController:5:MQTTController.js:289> MQTTController#mosquitto-mqtt registering event handler %prefix:zigbee2mqtt%/%topic%/availability for sovrumsdorr [latest-24152]2024-06-06T06:29:11.700Z <MQTTController:5:MQTTController.js:368> MQTTController#mosquitto-mqtt registering action x_mqtt_device.poll for sovrumsdorrRegarding the duplicates, it could be the templates with different
primary_attribute:and it is on my roadmap to bring it up for discussion if attributes also could be parameterized with defaults like%primary_attribute:[temperature / humidity / power_switch / dimming / motion / light]%or%temperature_sensor.units:[C / F]%.EDIT: Or is caused by the mystery of this issue? e.g.
string_sensorandpower_switchis somehow included in all templates. -
@Crille at some point I had similar problems, I fixed them and I reported here. Now I cannot repro it again, but it seems very similar and related to primary attributes in base templates. It seems like the first one is used and that’s causing troubles along the hierarchy, but, as I said, I’m not able to repro it again.
-
It also looks like something may be getting a shallow copy when it needs a deep copy, and it's being modified later and polluting the other references. I'm really tied up today, but I'll look at this as soon as I can.
Did you address the template redefinitions that were being logged at startup? That has nothing to do with primary attributes; the entire template is trying to be redefined.
