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.
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 ,
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.
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.0Hi-
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
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.
Hi,
Running the latest version 24212 on docker.
I want to run some appliances when my solar panels deliver over 1200 watts to the net. In this example the dryer. So when the dryer is turned on, the rule starts (SET). There first is a 3 min delay in case the dryer is turned on manually, that is group "Check if auto start is needed". If the dryer is not running, the status is set to waiting, and the shown Repeat Until should wait as long the power delivered is higher than -1200 for at least 120 seconds and the status is still waiting. Higher as the value is negative. For some reason that repeat until "DR Wait for solar high or manual start" looks skipped. Nothing in the logs. What am I missing?
Reactor Automation.png (g_DryerStatus should have been "waiting" and not "running" the moment the log was captured, so that should not be the issue. Unless it takes some time for a variable to actually change?)
Cheers Rene
I have got some warnings i reactor that a rule is throttled because it update rate is over 120/minute, happens now and when with a week or two in between.
The rule monitors my house power consumption when charging my car, and if if consumption risks to kill a main fuse, it stops the charging.
Thought I was clever when I in Constraints added that my car should be located at home and charging is active, but apparantly it wasn't clever enough...
I had understand it that if Constraints isn't true, then the triggers isn't evaluated.
I have a Shelly 3EM meter that measure three channel/phases and updates every second. So just for this three channels it is 180 updates per minute...
And now when I start to take a closer look I can se in my logs that this rule is evaluated with every value change on any of the three phases...
So ~11MB of logs only goes back in time around 16 hours...🙀
So what is the best solution?
Should move my "Constraints" in an new trigger group, before my existing triggers?
Rule as it is now
e5486a1b-7c3c-4ffc-b259-beed64948f2e-image.png
Hi!
I'm wondering if it's possible now, or if it's something that can be solved in a future version, to be able to remove the entities that no longer exist and are crossed out all at once. Currently, you have to mark them one by one, which takes a lot of time. Is there any way to make this more efficient?
I'm on MSR version 24212-3ce15e25.
Thanks!
/Fanan
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
![](https://github.com/fluidicon.png)
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
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[Solved] Issue with Tasmota sensors and MQTTController later than 22024
-
MSR: latest-22080-ae7212f bare metal.
I tried several times to update MQTTController but all my Tasmota sensors shows
null
and never updates if I go above version 22024 of MQTTController.I tried both my own
local_mqtt_devices.yaml
and the default template but getting these errors in the log for all my sensors after an update.[latest-22080]2022-03-30T13:26:02.821Z <MQTTController:ERR> MQTTController#mqtt event handler failed for tele/Pooltemp/SENSOR on pooltemp: [ReferenceError]ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-03-30T15:26:02","DS18B20":{"Id":"02049245CBF4","Temperature":3.4},"TempUnit":"C"} [latest-22080]2022-03-30T13:26:02.821Z <MQTTController:CRIT> ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-03-30T15:26:02","DS18B20":{"Id":"02049245CBF4","Temperature":3.4},"TempUnit":"C"} [latest-22080]2022-03-30T13:26:02.828Z <MQTTController:ERR> MQTTController#mqtt event handler failed for stat/Pooltemp/RESULT on dräneringspump: [ReferenceError]ReferenceError: Invalid reference to member [object Object] of {"Var1":"3.4"} [latest-22080]2022-03-30T13:26:02.828Z <MQTTController:CRIT> ReferenceError: Invalid reference to member [object Object] of {"Var1":"3.4"} [latest-22080]2022-03-30T13:26:03.113Z <MQTTController:ERR> MQTTController#mqtt event handler failed for stat/Pooltemp/RESULT on dräneringspump: [ReferenceError]ReferenceError: Invalid reference to member [object Object] of {"WebSend":"Done"} [latest-22080]2022-03-30T13:26:03.113Z <MQTTController:CRIT> ReferenceError: Invalid reference to member [object Object] of {"WebSend":"Done"}
The example device is running fine with this config on 22024.
"pooltemp": name: "Pooltemp" topic: "Pooltemp" source: "DS18B20" uses_template: my_tasmota_sensor_temperature
local_mqtt_devices.yaml
my_tasmota_sensor_temperature: type: ValueSensor capabilities: [temperature_sensor] primary_attribute: temperature_sensor.value init: - topic: "cmnd/%topic%/STATUS" payload: 10 type: raw events: "tele/%topic%/SENSOR": "temperature_sensor.value": expr: 'payload[source]?.Temperature' "temperature_sensor.units": expr: payload.TempUnit "stat/%topic%/STATUS10": "temperature_sensor.value": expr: 'payload.StatusSNS[source]?.Temperature' "temperature_sensor.units": expr: payload.StatusSNS.TempUnit
Any clues on how I could proceed troubleshooting? and as always, what critical information have I missed in this post?
-
I'm wondering why you made a custom template. Why not use the
tasmota_sensor_temperature
built-in template?On your own template, you're not declaring that the payload is JSON, so it will be unparseable by your expressions as given. So I would try the built-in template first and see if that fixes at least half of the issue (there's no template for your special STATUS10 topic, but you can use the built-in template in
mqtt_devices.yaml
as a model for the changes you'd likely need to make.Upping the log level to 5 or 6 (+restart) is often good before trying again and then posting logs, to increase traceable information. Also, it's really vital that you post a dozen or more lines of log before the error, not just the error. Context is vital in determining what it thinks its doing before the error. The error alone may not tell much (other than that there was an error).
-
I made custom templates because I never got the default to work and I wanted a init on restarts of MSR.
My templates is based on what was in the default templates when I created them and then it was not mandatory to declare payload as JSON, it may have changed and I might have missed that release note so I tried declaring a JSON payload in my templates but made no difference.
I'm now running default template for tasmota temperature sensor with log level 6 and all that is set from SENSOR topic istemperature_sensor.units
log with version 22024
[latest-22080]2022-04-02T17:02:21.892Z <MQTTController:6:MQTTController.js:242> MQTTController#mqtt message topic=tele/Pooltemp/SENSOR, payload=[Buffer]{"Time":"2022-04-02T19:02:21","DS18B20":{"Id":"02049245CBF4","Temperature":3.8},"TempUnit":"C"} [latest-22080]2022-04-02T17:02:21.892Z <MQTTController:6:MQTTController.js:270> MQTTController#mqtt dispatching tele/Pooltemp/SENSOR to pooltemp [latest-22080]2022-04-02T17:02:21.892Z <MQTTController:5:MQTTController.js:500> MQTTController#mqtt handling tele/Pooltemp/SENSOR for pooltemp: {"Time":"2022-04-02T19:02:21","DS18B20":{"Id":"02049245CBF4","Temperature":3.8},"TempUnit":"C"} [latest-22080]2022-04-02T17:02:21.892Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>pooltemp: [Object]{ "temperature_sensor.value": { "expr": "payload[source]?.Temperature" }, "temperature_sensor.units": { "expr": "payload.TempUnit" } } [latest-22080]2022-04-02T17:02:21.892Z <MQTTController:6:MQTTController.js:589> MQTTController#mqtt setting Entity#mqtt>pooltemp temperature_sensor.value=3.8 [latest-22080]2022-04-02T17:02:21.892Z <MQTTController:6:MQTTController.js:589> MQTTController#mqtt setting Entity#mqtt>pooltemp temperature_sensor.units=C
log with 22086.
[latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=tele/Pooltemp/SENSOR, payload=[Buffer]{"Time":"2022-04-02T19:14:21","DS18B20":{"Id":"02049245CBF4","Temperature":3.4},"TempUnit":"C"} [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching tele/Pooltemp/SENSOR to pooltemp [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling tele/Pooltemp/SENSOR for pooltemp: {"Time":"2022-04-02T19:14:21","DS18B20":{"Id":"02049245CBF4","Temperature":3.4},"TempUnit":"C"} [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>pooltemp: [Object]{ "temperature_sensor.value": { "json_payload": true, "if_expr": "! isnull( payload?[ source ?? \"Global\" ] )", "expr": "payload[ source ?? \"Global\" ]?.Temperature" }, "temperature_sensor.units": { "json_payload": true, "if_expr": "! isnull( payload?.TempUnit )", "expr": "payload.TempUnit" } } [latest-22080]2022-04-02T17:14:21.911Z <MQTTController:5:MQTTController.js:604> MQTTController#mqtt setting Entity#mqtt>pooltemp temperature_sensor.units=C
long snippet from that time with 22086.
[latest-22080]2022-04-02T17:14:19.496Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_active_power/state/value_sensor {"value":167,"units":"W"} [latest-22080]2022-04-02T17:14:19.496Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_active_power/state/string_sensor {"value":"167"} [latest-22080]2022-04-02T17:14:19.496Z <MQTTController:6:MQTTController.js:801> MQTTController#mqtt echo publishing primary attribute topic reactor/mqtt/hass/sensor_active_power/value "167" [latest-22080]2022-04-02T17:14:19.497Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/67/EnergyMetering1/input_power, payload=[Buffer]197 [latest-22080]2022-04-02T17:14:19.497Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_input_power/value "197" [latest-22080]2022-04-02T17:14:19.497Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_active_power/state/value_sensor {"value":167,"units":"W"} [latest-22080]2022-04-02T17:14:19.497Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_active_power/state/string_sensor {"value":"167"} [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/67/EnergyMetering1/active_power, payload=[Buffer]0.167 [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/67/EnergyMetering1/Watts, payload=[Buffer]167 [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_active_power/value "167" [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:727> MQTTController#mqtt echo handling entity notification for Entity#hass>sensor_efficiency [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:732> MQTTController#mqtt echo publishing capabilities for entity Entity#hass>sensor_efficiency [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:775> MQTTController#mqtt echo cap x_hass rejected -- default reject extended x_hass [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_efficiency/state/value_sensor {"value":84.9,"units":"%"} [latest-22080]2022-04-02T17:14:19.498Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_efficiency/state/string_sensor {"value":"84.9"} [latest-22080]2022-04-02T17:14:19.499Z <MQTTController:6:MQTTController.js:801> MQTTController#mqtt echo publishing primary attribute topic reactor/mqtt/hass/sensor_efficiency/value "84.9" [latest-22080]2022-04-02T17:14:19.499Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_efficiency/state/value_sensor {"value":84.9,"units":"%"} [latest-22080]2022-04-02T17:14:19.499Z <MQTTController:6:MQTTController.js:727> MQTTController#mqtt echo handling entity notification for Entity#hass>sensor_pv_1_voltage [latest-22080]2022-04-02T17:14:19.499Z <MQTTController:6:MQTTController.js:732> MQTTController#mqtt echo publishing capabilities for entity Entity#hass>sensor_pv_1_voltage [latest-22080]2022-04-02T17:14:19.500Z <MQTTController:6:MQTTController.js:775> MQTTController#mqtt echo cap x_hass rejected -- default reject extended x_hass [latest-22080]2022-04-02T17:14:19.500Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_pv_1_voltage/state/value_sensor {"value":302.2,"units":"V"} [latest-22080]2022-04-02T17:14:19.500Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_pv_1_voltage/state/string_sensor {"value":"302.2"} [latest-22080]2022-04-02T17:14:19.500Z <MQTTController:6:MQTTController.js:801> MQTTController#mqtt echo publishing primary attribute topic reactor/mqtt/hass/sensor_pv_1_voltage/value "302.2" [latest-22080]2022-04-02T17:14:19.500Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_efficiency/state/string_sensor {"value":"84.9"} [latest-22080]2022-04-02T17:14:19.500Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/67/EnergyMetering1/efficiency, payload=[Buffer]84.9 [latest-22080]2022-04-02T17:14:19.501Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_efficiency/value "84.9" [latest-22080]2022-04-02T17:14:19.501Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_1_voltage/state/value_sensor {"value":302.2,"units":"V"} [latest-22080]2022-04-02T17:14:19.501Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_1_voltage/state/string_sensor {"value":"302.2"} [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/67/EnergyMetering1/pv_1_voltage, payload=[Buffer]302.2 [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_1_voltage/value "302.2" [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:727> MQTTController#mqtt echo handling entity notification for Entity#hass>sensor_pv_2_voltage [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:732> MQTTController#mqtt echo publishing capabilities for entity Entity#hass>sensor_pv_2_voltage [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:775> MQTTController#mqtt echo cap x_hass rejected -- default reject extended x_hass [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_pv_2_voltage/state/value_sensor {"value":302.2,"units":"V"} [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_pv_2_voltage/state/string_sensor {"value":"302.2"} [latest-22080]2022-04-02T17:14:19.502Z <MQTTController:6:MQTTController.js:801> MQTTController#mqtt echo publishing primary attribute topic reactor/mqtt/hass/sensor_pv_2_voltage/value "302.2" [latest-22080]2022-04-02T17:14:19.503Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_2_voltage/state/value_sensor {"value":302.2,"units":"V"} [latest-22080]2022-04-02T17:14:19.503Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_2_voltage/state/string_sensor {"value":"302.2"} [latest-22080]2022-04-02T17:14:19.503Z <MQTTController:6:MQTTController.js:727> MQTTController#mqtt echo handling entity notification for Entity#hass>sensor_pv_4_current [latest-22080]2022-04-02T17:14:19.503Z <MQTTController:6:MQTTController.js:732> MQTTController#mqtt echo publishing capabilities for entity Entity#hass>sensor_pv_4_current [latest-22080]2022-04-02T17:14:19.503Z <MQTTController:6:MQTTController.js:775> MQTTController#mqtt echo cap x_hass rejected -- default reject extended x_hass [latest-22080]2022-04-02T17:14:19.504Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_pv_4_current/state/value_sensor {"value":0.57,"units":"A"} [latest-22080]2022-04-02T17:14:19.504Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_pv_4_current/state/string_sensor {"value":"0.57"} [latest-22080]2022-04-02T17:14:19.504Z <MQTTController:6:MQTTController.js:801> MQTTController#mqtt echo publishing primary attribute topic reactor/mqtt/hass/sensor_pv_4_current/value "0.57" [latest-22080]2022-04-02T17:14:19.504Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/67/EnergyMetering1/pv_2_voltage, payload=[Buffer]302.2 [latest-22080]2022-04-02T17:14:19.504Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_2_voltage/value "302.2" [latest-22080]2022-04-02T17:14:19.504Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_4_current/state/value_sensor {"value":0.57,"units":"A"} [latest-22080]2022-04-02T17:14:19.504Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_4_current/state/string_sensor {"value":"0.57"} [latest-22080]2022-04-02T17:14:19.505Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/67/EnergyMetering1/pv_4_current, payload=[Buffer]0.57 [latest-22080]2022-04-02T17:14:19.505Z <MQTTController:6:MQTTController.js:856> MQTTController#mqtt handling incoming reactor/mqtt/hass/sensor_pv_4_current/value "0.57" [latest-22080]2022-04-02T17:14:20.716Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_active_import/state, payload=[Buffer]40140.484 [latest-22080]2022-04-02T17:14:20.752Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_active_export/state, payload=[Buffer]5946.984 [latest-22080]2022-04-02T17:14:20.753Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_reactive_import/state, payload=[Buffer]325.049 [latest-22080]2022-04-02T17:14:20.753Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_reactive_export/state, payload=[Buffer]3259.873 [latest-22080]2022-04-02T17:14:20.754Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import/state, payload=[Buffer]5.574 [latest-22080]2022-04-02T17:14:20.754Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_import, payload=[Buffer]5.574 [latest-22080]2022-04-02T17:14:20.754Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/Watts, payload=[Buffer]5574 [latest-22080]2022-04-02T17:14:20.754Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_use, payload=[Buffer]5.741 [latest-22080]2022-04-02T17:14:20.754Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_use_own, payload=[Buffer]0.167 [latest-22080]2022-04-02T17:14:20.754Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.755Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.755Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export/state, payload=[Buffer]0.749 [latest-22080]2022-04-02T17:14:20.756Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_export, payload=[Buffer]0.749 [latest-22080]2022-04-02T17:14:20.756Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import_phase_1/state, payload=[Buffer]0.525 [latest-22080]2022-04-02T17:14:20.756Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_import_phase_1, payload=[Buffer]0.525 [latest-22080]2022-04-02T17:14:20.756Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export_phase_1/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.757Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import_phase_2/state, payload=[Buffer]3.819 [latest-22080]2022-04-02T17:14:20.757Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export_phase_2/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.758Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import_phase_3/state, payload=[Buffer]1.218 [latest-22080]2022-04-02T17:14:20.758Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_import_phase_3, payload=[Buffer]1.218 [latest-22080]2022-04-02T17:14:20.758Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export_phase_3/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.758Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import_phase_1/state, payload=[Buffer]0.441 [latest-22080]2022-04-02T17:14:20.758Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_import_phase_1, payload=[Buffer]0.441 [latest-22080]2022-04-02T17:14:20.759Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export_phase_1/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.759Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import_phase_2/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.759Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export_phase_2/state, payload=[Buffer]0.528 [latest-22080]2022-04-02T17:14:20.760Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_export_phase_2, payload=[Buffer]0.528 [latest-22080]2022-04-02T17:14:20.760Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import_phase_3/state, payload=[Buffer]0.000 [latest-22080]2022-04-02T17:14:20.760Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export_phase_3/state, payload=[Buffer]0.654 [latest-22080]2022-04-02T17:14:20.760Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_export_phase_3, payload=[Buffer]0.654 [latest-22080]2022-04-02T17:14:20.761Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/voltage_phase_1/state, payload=[Buffer]235.500 [latest-22080]2022-04-02T17:14:20.761Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/voltage_phase_1, payload=[Buffer]235.5 [latest-22080]2022-04-02T17:14:20.761Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/voltage_phase_2/state, payload=[Buffer]232.900 [latest-22080]2022-04-02T17:14:20.761Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/voltage_phase_2, payload=[Buffer]232.9 [latest-22080]2022-04-02T17:14:20.761Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/voltage_phase_3/state, payload=[Buffer]235.600 [latest-22080]2022-04-02T17:14:20.761Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/voltage_phase_3, payload=[Buffer]235.6 [latest-22080]2022-04-02T17:14:20.762Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/current_phase_1/state, payload=[Buffer]2.900 [latest-22080]2022-04-02T17:14:20.762Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/current_phase_1, payload=[Buffer]2.9 [latest-22080]2022-04-02T17:14:20.762Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/current_phase_2/state, payload=[Buffer]16.600 [latest-22080]2022-04-02T17:14:20.762Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/current_phase_3/state, payload=[Buffer]5.800 [latest-22080]2022-04-02T17:14:20.762Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/current_phase_3, payload=[Buffer]5.8 [latest-22080]2022-04-02T17:14:21.909Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=tele/Pooltemp/STATE, payload=[Buffer]{"Time":"2022-04-02T19:14:21","Uptime":"54T18:23:25","UptimeSec":4731805,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":92,"POWER":"ON","Wifi":{"AP":1,"SSId":"Orion","BSSId":"E0:3F:49:06:F1:30","Channel":6,"Mode":"11n","RSSI":58,"Signal":-71,"LinkCount":4,"Downtime":"0T00:00:19"}} [latest-22080]2022-04-02T17:14:21.909Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/35/HaDevice1/LastUpdate, payload=[Buffer]1648919661 [latest-22080]2022-04-02T17:14:21.909Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/HaDevice1/LastUpdate, payload=[Buffer]1648919661 [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/tele, payload=[Buffer]{"Time":"2022-04-02T19:14:21","Uptime":"54T18:23:25","UptimeSec":4731805,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":92,"POWER":"ON","Wifi":{"AP":1,"SSId":"Orion","BSSId":"E0:3F:49:06:F1:30","Channel":6,"Mode":"11n","RSSI":58,"Signal":-71,"LinkCount":4,"Downtime":"0T00:00:19"}} [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/UptimeSec, payload=[Buffer]4731805 [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/Time, payload=[Buffer]2022-04-02T19:14:21 [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Wifi/RSSI, payload=[Buffer]58 [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Wifi/Signal, payload=[Buffer]-71 [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/Uptime, payload=[Buffer]54T18:23:25 [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=tele/Pooltemp/SENSOR, payload=[Buffer]{"Time":"2022-04-02T19:14:21","DS18B20":{"Id":"02049245CBF4","Temperature":3.4},"TempUnit":"C"} [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching tele/Pooltemp/SENSOR to pooltemp [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling tele/Pooltemp/SENSOR for pooltemp: {"Time":"2022-04-02T19:14:21","DS18B20":{"Id":"02049245CBF4","Temperature":3.4},"TempUnit":"C"} [latest-22080]2022-04-02T17:14:21.910Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>pooltemp: [Object]{ "temperature_sensor.value": { "json_payload": true, "if_expr": "! isnull( payload?[ source ?? \"Global\" ] )", "expr": "payload[ source ?? \"Global\" ]?.Temperature" }, "temperature_sensor.units": { "json_payload": true, "if_expr": "! isnull( payload?.TempUnit )", "expr": "payload.TempUnit" } } [latest-22080]2022-04-02T17:14:21.911Z <MQTTController:5:MQTTController.js:604> MQTTController#mqtt setting Entity#mqtt>pooltemp temperature_sensor.units=C [latest-22080]2022-04-02T17:14:21.911Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/tele, payload=[Buffer]{"Time":"2022-04-02T19:14:21","DS18B20":{"Id":"02049245CBF4","Temperature":3.4},"TempUnit":"C"} [latest-22080]2022-04-02T17:14:21.911Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=stat/Pooltemp/RESULT, payload=[Buffer]{"Var1":"3.4"} [latest-22080]2022-04-02T17:14:22.210Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=stat/Pooltemp/RESULT, payload=[Buffer]{"WebSend":"Done"} [latest-22080]2022-04-02T17:14:22.211Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/10086/TemperatureSensor1/CurrentTemperature, payload=[Buffer]3.4 [latest-22080]2022-04-02T17:14:22.211Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/5/VeraBridge1/LastUpdate, payload=[Buffer]1648919662 [latest-22080]2022-04-02T17:14:26.644Z <wsapi:INFO> client "192.168.1.238#1" closed, code=1001, reason= [latest-22080]2022-04-02T17:14:27.081Z <wsapi:INFO> wsapi: connection from "192.168.1.238"
-
@crille said in Issue with Tasmota sensors and MQTTController later than 22024:
I made custom templates because I never got the default to work and I wanted a init on restarts of MSR.
I have to confess that's a bit disappointing, because if nobody tells me something doesn't work, I may never know to fix it. I rely on everyone to be ears, eyes, and hands because even if I had every device and could test every thing, the chances of me using things in the same ways, and in all of the possible ways, that people can and do are slim to non-existent. You're saying versions before 22024 are working for you, and today is 22092, 68 days later. That's a bummer.
But back to the technical side, you don't need to make your own template just to have an init. You can just add your init to your entity configuration. All that
uses_template
does is merge the referenced template into the entity config, with priority given to config (that is, if you haveinit
in your config and there's aninit
in the template, your config will prevail). I will make this more clear in the docs.And, that init really shouldn't be necessary if your Tasmota has the retain flag set for those messages -- MQTTController would get the message with last state when it subscribes after it connects. At least, that would be the case for a compliant broker (I have no idea what you're using as a broker).
Log snippets are helpful. I think I spotted an issue. Let me set up a test case and run your messages through statically, and see if I'm right, and if I am, what I can do about it. Stay tuned!
-
Yes, sorry for not being persistent with my issue on this, we kind of touched it before here but obviously it worked for you and no one else had issues so I made it work for me.
I first noticed my current issue in 22029 (mentioned in MantisBT #0000303, not related to this, as “other issues”) and haven’t had the time to mess with a stable setup to report the errors since. My apologies!
Better late than never I’m doing my part now when life allows the time for fun stuff like this
I believe openLuup MQTT broker supports the retain flag now and will configure my devices to apply it, if not I will move them to my Mosquitto broker when I have the time.
Thank you for your patience and support!
-
@crille I'm sorry you've had to live with it this long. Let's get it straightened out.
New build 22092 of MQTTController is available for download/install. Let's see if that gets things rolling (your template or the included one, either way, but it will require
json_payload: true
where JSON is used). -
OK, new tests done.
This is done with 22092 with log level 6.
reactor.yaml
"pooltemp": name: "Pooltemp" topic: "Pooltemp" source: "DS18B20" uses_template: tasmota_sensor_temperature
as you can see it's using included default template
tasmota_sensor_temperature: type: ValueSensor capabilities: [temperature_sensor] primary_attribute: temperature_sensor.value events: "tele/%topic%/SENSOR": "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?[ source ?? "Global" ] )' expr: 'payload[ source ?? "Global" ]?.Temperature' "temperature_sensor.units": json_payload: true if_expr: '! isnull( payload?.TempUnit )' expr: payload.TempUnit
I've set
SensorRetain 1
in Tasmota and the value is now retained in openLuup
log after restart of MSR
[latest-22080]2022-04-03T13:06:19.815Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/current_phase_3/state, payload=[Buffer]5.800 [latest-22080]2022-04-03T13:06:27.251Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=tele/Växthuset/SENSOR, payload=[Buffer]{"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} [latest-22080]2022-04-03T13:06:27.251Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching tele/Växthuset/SENSOR to esp32 [latest-22080]2022-04-03T13:06:27.251Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling tele/Växthuset/SENSOR for esp32: {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} [latest-22080]2022-04-03T13:06:27.251Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>esp32: [Object]{ "temperature_sensor.value": { "json_payload": true, "if_expr": "! isnull( payload?[ source ?? \"Global\" ] )", "expr": "payload[ source ?? \"Global\" ]?.Temperature" }, "temperature_sensor.units": { "json_payload": true, "if_expr": "! isnull( payload?.TempUnit )", "expr": "payload.TempUnit" } } [latest-22080]2022-04-03T13:06:27.251Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching tele/Växthuset/SENSOR to flora1 [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling tele/Växthuset/SENSOR for flora1: {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>flora1: [Object]{ "temperature_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Temperature" }, "temperature_sensor.units": "C", "humidity_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Moisture" }, "humidity_sensor.units": "%", "light_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Illuminance" }, "light_sensor.units": "lux", "value_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Fertility" }, "value_sensor.units": "µS/cm" } [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:ERR> MQTTController#mqtt event handler failed for tele/Växthuset/SENSOR on flora1: [ReferenceError]ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:CRIT> ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} at _run (/home/homebridge/reactor/common/lexp.js:1431:31) at /home/homebridge/reactor/common/lexp.js:1512:33 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1511:28) at _run (/home/homebridge/reactor/common/lexp.js:1414:33) at /home/homebridge/reactor/common/lexp.js:1265:29 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1264:28) at Object.run (/home/homebridge/reactor/common/lexp.js:1645:22) at MQTTController.handle_event (/home/homebridge/reactor/ext/MQTTController/MQTTController.js:567:44) [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching tele/Växthuset/SENSOR to flora2 [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling tele/Växthuset/SENSOR for flora2: {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>flora2: [Object]{ "temperature_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Temperature" }, "temperature_sensor.units": "C", "humidity_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Moisture" }, "humidity_sensor.units": "%", "light_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Illuminance" }, "light_sensor.units": "lux", "value_sensor.value": { "if_expr": "! isnull( payload?[ source ] )", "expr": "payload?[source]?.Fertility" }, "value_sensor.units": "µS/cm" } [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:ERR> MQTTController#mqtt event handler failed for tele/Växthuset/SENSOR on flora2: [ReferenceError]ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} [latest-22080]2022-04-03T13:06:27.252Z <MQTTController:CRIT> ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} ReferenceError: Invalid reference to member [object Object] of {"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} at _run (/home/homebridge/reactor/common/lexp.js:1431:31) at /home/homebridge/reactor/common/lexp.js:1512:33 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1511:28) at _run (/home/homebridge/reactor/common/lexp.js:1414:33) at /home/homebridge/reactor/common/lexp.js:1265:29 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1264:28) at Object.run (/home/homebridge/reactor/common/lexp.js:1645:22) at MQTTController.handle_event (/home/homebridge/reactor/ext/MQTTController/MQTTController.js:567:44) [latest-22080]2022-04-03T13:06:27.253Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/35/HaDevice1/LastUpdate, payload=[Buffer]1648991187 [latest-22080]2022-04-03T13:06:27.253Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30005/HaDevice1/LastUpdate, payload=[Buffer]1648991187 [latest-22080]2022-04-03T13:06:27.253Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30005/Växthuset/tele, payload=[Buffer]{"Time":"2022-04-03T15:06:27","Flora6cab88":{"mac":"c47c8d6cab88","Temperature":10.5,"Illuminance":547,"Moisture":0,"Fertility":0,"RSSI":-97}} [latest-22080]2022-04-03T13:06:27.253Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30005/Växthuset/Time, payload=[Buffer]2022-04-03T15:06:27 [latest-22080]2022-04-03T13:06:27.253Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30005/Flora6cab88/Illuminance, payload=[Buffer]547 [latest-22080]2022-04-03T13:06:27.253Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30005/Flora6cab88/RSSI, payload=[Buffer]-97 [latest-22080]2022-04-03T13:06:27.254Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30005/Flora6cab88/Temperature, payload=[Buffer]10.5 [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=tele/Pooltemp/STATE, payload=[Buffer]{"Time":"2022-04-03T15:06:27","Uptime":"55T14:15:31","UptimeSec":4803331,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":93,"POWER":"OFF","Wifi":{"AP":1,"SSId":"Orion","BSSId":"E0:3F:49:06:F1:30","Channel":6,"Mode":"11n","RSSI":46,"Signal":-77,"LinkCount":4,"Downtime":"0T00:00:19"}} [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/35/HaDevice1/LastUpdate, payload=[Buffer]1648991188 [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/HaDevice1/LastUpdate, payload=[Buffer]1648991188 [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/tele, payload=[Buffer]{"Time":"2022-04-03T15:06:27","Uptime":"55T14:15:31","UptimeSec":4803331,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":93,"POWER":"OFF","Wifi":{"AP":1,"SSId":"Orion","BSSId":"E0:3F:49:06:F1:30","Channel":6,"Mode":"11n","RSSI":46,"Signal":-77,"LinkCount":4,"Downtime":"0T00:00:19"}} [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/UptimeSec, payload=[Buffer]4803331 [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/Time, payload=[Buffer]2022-04-03T15:06:27 [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/Uptime, payload=[Buffer]55T14:15:31 [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=tele/Pooltemp/SENSOR, payload=[Buffer]{"Time":"2022-04-03T15:06:28","DS18B20":{"Id":"02049245CBF4","Temperature":8.8},"TempUnit":"C"} [latest-22080]2022-04-03T13:06:28.452Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching tele/Pooltemp/SENSOR to pooltemp [latest-22080]2022-04-03T13:06:28.453Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling tele/Pooltemp/SENSOR for pooltemp: {"Time":"2022-04-03T15:06:28","DS18B20":{"Id":"02049245CBF4","Temperature":8.8},"TempUnit":"C"} [latest-22080]2022-04-03T13:06:28.453Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>pooltemp: [Object]{ "temperature_sensor.value": { "json_payload": true, "if_expr": "! isnull( payload?[ source ?? \"Global\" ] )", "expr": "payload[ source ?? \"Global\" ]?.Temperature" }, "temperature_sensor.units": { "json_payload": true, "if_expr": "! isnull( payload?.TempUnit )", "expr": "payload.TempUnit" } } [latest-22080]2022-04-03T13:06:28.453Z <MQTTController:5:MQTTController.js:604> MQTTController#mqtt setting Entity#mqtt>pooltemp temperature_sensor.units=C [latest-22080]2022-04-03T13:06:28.453Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/tele, payload=[Buffer]{"Time":"2022-04-03T15:06:28","DS18B20":{"Id":"02049245CBF4","Temperature":8.8},"TempUnit":"C"} [latest-22080]2022-04-03T13:06:28.453Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/DS18B20/Temperature, payload=[Buffer]8.8 [latest-22080]2022-04-03T13:06:28.453Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/30003/Pooltemp/Time, payload=[Buffer]2022-04-03T15:06:28 [latest-22080]2022-04-03T13:06:28.458Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=stat/Pooltemp/RESULT, payload=[Buffer]{"Var1":"8.8"} [latest-22080]2022-04-03T13:06:28.458Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching stat/Pooltemp/RESULT to dräneringspump [latest-22080]2022-04-03T13:06:28.458Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling stat/Pooltemp/RESULT for dräneringspump: {"Var1":"8.8"} [latest-22080]2022-04-03T13:06:28.458Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>dräneringspump: [Object]{ "power_switch.state": { "if_expr": "! isnull( payload[ \"POWER\" + str(unit) ] )", "expr": "upper( payload[ \"POWER\" + str(unit) ] ) == \"ON\"" } } [latest-22080]2022-04-03T13:06:28.458Z <MQTTController:ERR> MQTTController#mqtt event handler failed for stat/Pooltemp/RESULT on dräneringspump: [ReferenceError]ReferenceError: Invalid reference to member [object Object] of {"Var1":"8.8"} [latest-22080]2022-04-03T13:06:28.458Z <MQTTController:CRIT> ReferenceError: Invalid reference to member [object Object] of {"Var1":"8.8"} ReferenceError: Invalid reference to member [object Object] of {"Var1":"8.8"} at _run (/home/homebridge/reactor/common/lexp.js:1431:31) at /home/homebridge/reactor/common/lexp.js:1512:33 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1511:28) at _run (/home/homebridge/reactor/common/lexp.js:1414:33) at /home/homebridge/reactor/common/lexp.js:1265:29 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1264:28) at Object.run (/home/homebridge/reactor/common/lexp.js:1645:22) at MQTTController.handle_event (/home/homebridge/reactor/ext/MQTTController/MQTTController.js:567:44) [latest-22080]2022-04-03T13:06:28.733Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/10086/TemperatureSensor1/CurrentTemperature, payload=[Buffer]8.6 [latest-22080]2022-04-03T13:06:28.733Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/5/VeraBridge1/LastUpdate, payload=[Buffer]1648991188 [latest-22080]2022-04-03T13:06:28.774Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=stat/Pooltemp/RESULT, payload=[Buffer]{"WebSend":"Done"} [latest-22080]2022-04-03T13:06:28.774Z <MQTTController:6:MQTTController.js:278> MQTTController#mqtt dispatching stat/Pooltemp/RESULT to dräneringspump [latest-22080]2022-04-03T13:06:28.774Z <MQTTController:5:MQTTController.js:508> MQTTController#mqtt handling stat/Pooltemp/RESULT for dräneringspump: {"WebSend":"Done"} [latest-22080]2022-04-03T13:06:28.774Z <MQTTController:6:MQTTController.js:532> MQTTController#mqtt events for Entity#mqtt>dräneringspump: [Object]{ "power_switch.state": { "if_expr": "! isnull( payload[ \"POWER\" + str(unit) ] )", "expr": "upper( payload[ \"POWER\" + str(unit) ] ) == \"ON\"" } } [latest-22080]2022-04-03T13:06:28.774Z <MQTTController:ERR> MQTTController#mqtt event handler failed for stat/Pooltemp/RESULT on dräneringspump: [ReferenceError]ReferenceError: Invalid reference to member [object Object] of {"WebSend":"Done"} [latest-22080]2022-04-03T13:06:28.774Z <MQTTController:CRIT> ReferenceError: Invalid reference to member [object Object] of {"WebSend":"Done"} ReferenceError: Invalid reference to member [object Object] of {"WebSend":"Done"} at _run (/home/homebridge/reactor/common/lexp.js:1431:31) at /home/homebridge/reactor/common/lexp.js:1512:33 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1511:28) at _run (/home/homebridge/reactor/common/lexp.js:1414:33) at /home/homebridge/reactor/common/lexp.js:1265:29 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1264:28) at Object.run (/home/homebridge/reactor/common/lexp.js:1645:22) at MQTTController.handle_event (/home/homebridge/reactor/ext/MQTTController/MQTTController.js:567:44) [latest-22080]2022-04-03T13:06:29.774Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_active_import/state, payload=[Buffer]40196.133 [latest-22080]2022-04-03T13:06:29.804Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_active_export/state, payload=[Buffer]5955.417 [latest-22080]2022-04-03T13:06:29.804Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_reactive_import/state, payload=[Buffer]325.054 [latest-22080]2022-04-03T13:06:29.805Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/cumulative_reactive_export/state, payload=[Buffer]3266.027 [latest-22080]2022-04-03T13:06:29.805Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import/state, payload=[Buffer]4.250 [latest-22080]2022-04-03T13:06:29.805Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_import, payload=[Buffer]4.250 [latest-22080]2022-04-03T13:06:29.805Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/Watts, payload=[Buffer]4250 [latest-22080]2022-04-03T13:06:29.806Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_use, payload=[Buffer]7.933 [latest-22080]2022-04-03T13:06:29.806Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.807Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.807Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export/state, payload=[Buffer]0.589 [latest-22080]2022-04-03T13:06:29.807Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_export, payload=[Buffer]0.589 [latest-22080]2022-04-03T13:06:29.807Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import_phase_1/state, payload=[Buffer]0.652 [latest-22080]2022-04-03T13:06:29.808Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_import_phase_1, payload=[Buffer]0.652 [latest-22080]2022-04-03T13:06:29.808Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export_phase_1/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.808Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import_phase_2/state, payload=[Buffer]2.673 [latest-22080]2022-04-03T13:06:29.808Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_import_phase_2, payload=[Buffer]2.673 [latest-22080]2022-04-03T13:06:29.810Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export_phase_2/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.810Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_import_phase_3/state, payload=[Buffer]0.844 [latest-22080]2022-04-03T13:06:29.810Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_active_import_phase_3, payload=[Buffer]0.844 [latest-22080]2022-04-03T13:06:29.810Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_active_export_phase_3/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.810Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import_phase_1/state, payload=[Buffer]0.954 [latest-22080]2022-04-03T13:06:29.810Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_import_phase_1, payload=[Buffer]0.954 [latest-22080]2022-04-03T13:06:29.810Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export_phase_1/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.811Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import_phase_2/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.811Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export_phase_2/state, payload=[Buffer]0.432 [latest-22080]2022-04-03T13:06:29.811Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_export_phase_2, payload=[Buffer]0.432 [latest-22080]2022-04-03T13:06:29.811Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_import_phase_3/state, payload=[Buffer]0.000 [latest-22080]2022-04-03T13:06:29.812Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/momentary_reactive_export_phase_3/state, payload=[Buffer]1.118 [latest-22080]2022-04-03T13:06:29.812Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/momentary_reactive_export_phase_3, payload=[Buffer]1.118 [latest-22080]2022-04-03T13:06:29.812Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/voltage_phase_1/state, payload=[Buffer]232.900 [latest-22080]2022-04-03T13:06:29.812Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/voltage_phase_1, payload=[Buffer]232.9 [latest-22080]2022-04-03T13:06:29.812Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/voltage_phase_2/state, payload=[Buffer]231.200 [latest-22080]2022-04-03T13:06:29.813Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/voltage_phase_2, payload=[Buffer]231.2 [latest-22080]2022-04-03T13:06:29.813Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/voltage_phase_3/state, payload=[Buffer]233.800 [latest-22080]2022-04-03T13:06:29.813Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/voltage_phase_3, payload=[Buffer]233.8 [latest-22080]2022-04-03T13:06:29.813Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/current_phase_1/state, payload=[Buffer]4.900 [latest-22080]2022-04-03T13:06:29.813Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/current_phase_1, payload=[Buffer]4.9 [latest-22080]2022-04-03T13:06:29.814Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/current_phase_2/state, payload=[Buffer]11.700 [latest-22080]2022-04-03T13:06:29.814Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/current_phase_2, payload=[Buffer]11.7 [latest-22080]2022-04-03T13:06:29.814Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=smartreader/sensor/current_phase_3/state, payload=[Buffer]5.900 [latest-22080]2022-04-03T13:06:29.814Z <MQTTController:6:MQTTController.js:250> MQTTController#mqtt message topic=openLuup/update/56/EnergyMetering1/current_phase_3, payload=[Buffer]5.9 [latest-22080]2022-04-03T13:06:30.477Z <MQTTController:6:MQTTController.js:727> MQTTController#mqtt echo handling entity notification for Entity#hass>sensor_input_power [latest-22080]2022-04-03T13:06:30.477Z <MQTTController:6:MQTTController.js:732> MQTTController#mqtt echo publishing capabilities for entity Entity#hass>sensor_input_power [latest-22080]2022-04-03T13:06:30.477Z <MQTTController:6:MQTTController.js:775> MQTTController#mqtt echo cap x_hass rejected -- default reject extended x_hass [latest-22080]2022-04-03T13:06:30.477Z <MQTTController:6:MQTTController.js:793> MQTTController#mqtt echo publishing reactor/mqtt/hass/sensor_input_power/state/value_sensor {"value":3647,"units":"W"}
-
Can you confirm in the startup messages that MQTTController is version 22092? The messages are not consistent with what should be seen in the new version.
-
This is from 22024
[latest-22080]2022-04-03T14:52:25.150Z <SystemController:null> Module SystemController v22080 [latest-22080]2022-04-03T14:52:25.151Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-22080]2022-04-03T14:52:25.152Z <MQTTController:null> Module MQTTController v22009 [latest-22080]2022-04-03T14:52:25.191Z <MQTTController:INFO> instance topic ident is mqtt
and this is from 22092
[latest-22080]2022-04-03T14:56:46.397Z <SystemController:null> Module SystemController v22080 [latest-22080]2022-04-03T14:56:46.398Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-22080]2022-04-03T14:56:46.400Z <MQTTController:null> Module MQTTController v22029 [latest-22080]2022-04-03T14:56:46.437Z <MQTTController:INFO> instance topic ident is mqtt
-
Line 3 from 22092 says... 22029... dyslexia in version! That's a build error, and a strange coincidence at that.
I just rebuilt the package. Re-download it and run the install again, then try. It should say 22092 at startup.
-
Yup, now I can confirm it's version 22092
[latest-22080]2022-04-03T15:24:40.904Z <SystemController:null> Module SystemController v22080 [latest-22080]2022-04-03T15:24:40.905Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-22080]2022-04-03T15:24:40.906Z <MQTTController:null> Module MQTTController v22092 [latest-22080]2022-04-03T15:24:40.943Z <MQTTController:INFO> instance topic ident is mqtt
AND I now get the value for temperature on the next tele, but not the retained value at startup...?
My custom template using init is also working when JSON payload is declared.Tell me what you need next.
-
OK. I can see on my Tasmota devices that it doesn't send the retain flag
on
... and I can't find that in Tasmota configuration... seems like a big hole, actually. I assumed that would be somewhere, and I'm disappointed that I'm apparently wrong.So, init will be required. However, your
init
should work with the included template (no need to copy the template to your local config, just put yourinit
afteruses_template
). If that's not working, I'd like to know.EDIT: I found it... it's obscure. In the Tasmota console (it's not in the GUI), you need to type each of:
PowerRetain on SensorRetain on StateRetain on SwitchRetain on
For your temperature sensor,
SensorRetain
may be sufficient, but I don't see why you would not use it for other types as well. -
@crille said in Issue with Tasmota sensors and MQTTController later than 22024:
I've set SensorRetain 1 in Tasmota and the value is now retained in openLuup
Yes, I've done that but the value does not get set when I restart MSR for some reason.
-
I had to restart my Tasmota device to get it to work, and of course, force state/value changes on the device to get it to send a first message with that flag set.
-
Here's what my log looks like with Mosquitto broker and the Tasmota device disconnected from power (so unable to publish -- anything Tasmota is therefore retained and sent from the broker):
[###BUILDVERSION###]2022-04-03T17:37:38.285Z <MQTTController:null> Module MQTTController v22092 [###BUILDVERSION###]2022-04-03T17:37:38.323Z <MQTTController:5:Controller.js:90> [MQTTController:constructor] created controller mqtt [###BUILDVERSION###]2022-04-03T17:37:38.323Z <MQTTController:INFO> instance topic ident is mqtt [###BUILDVERSION###]2022-04-03T17:37:38.376Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity blueiris_cam6_motion [###BUILDVERSION###]2022-04-03T17:37:38.376Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity blueiris_cam13_motion [###BUILDVERSION###]2022-04-03T17:37:38.376Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity "75e505_1" [###BUILDVERSION###]2022-04-03T17:37:38.377Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity "75e505_2" [###BUILDVERSION###]2022-04-03T17:37:38.377Z <MQTTController:NOTICE> Connecting to broker mqtt://192.168.0.66:1883/ [###BUILDVERSION###]2022-04-03T17:37:38.377Z <MQTTController:5:MQTTController.js:241> MQTTController#mqtt connecting to mqtt://192.168.0.66:1883/ with options [Object]{ "reconnectPeriod": 15000, "clientId": "reactor_drupal_mqtt", "connectTimeout": 10000, "resubscribe": false, "will": { "topic": "reactor/mqtt/LWT", "payload": "offline", "qos": 1, "retain": true, "properties": { "willDelayInterval": 30 } } } [###BUILDVERSION###]2022-04-03T17:37:38.474Z <MQTTController:INFO> connected; opening subscriptions [###BUILDVERSION###]2022-04-03T17:37:38.477Z <MQTTController:INFO> Sending inits and going online! [###BUILDVERSION###]2022-04-03T17:37:38.478Z <MQTTController:NOTICE> Controller MQTTController#mqtt is now online. [###BUILDVERSION###]2022-04-03T17:37:38.488Z <MQTTController:5:MQTTController.js:521> MQTTController#mqtt handling tele/tasmota_75E505/STATE for "75e505_1": {"Time":"2022-04-03T18:32:34","Uptime":"0T00:10:10","UptimeSec":610,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"ON","POWER2":"ON","Wifi":{"AP":1,"SSId":"SupremeGarden","BSSId":"44:D9:E7:03:C7:3A","Channel":6,"Mode":"11n","RSSI":54,"Signal":-73,"LinkCount":1,"Downtime":"0T00:00:04"}} [###BUILDVERSION###]2022-04-03T17:37:38.489Z <MQTTController:5:MQTTController.js:626> MQTTController#mqtt setting Entity#mqtt>75e505_1 power_switch.state=true [###BUILDVERSION###]2022-04-03T17:37:38.489Z <MQTTController:5:MQTTController.js:521> MQTTController#mqtt handling tele/tasmota_75E505/STATE for "75e505_2": {"Time":"2022-04-03T18:32:34","Uptime":"0T00:10:10","UptimeSec":610,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"ON","POWER2":"ON","Wifi":{"AP":1,"SSId":"SupremeGarden","BSSId":"44:D9:E7:03:C7:3A","Channel":6,"Mode":"11n","RSSI":54,"Signal":-73,"LinkCount":1,"Downtime":"0T00:00:04"}} [###BUILDVERSION###]2022-04-03T17:37:38.489Z <MQTTController:5:MQTTController.js:626> MQTTController#mqtt setting Entity#mqtt>75e505_2 power_switch.state=true [###BUILDVERSION###]2022-04-03T17:37:38.494Z <MQTTController:5:MQTTController.js:521> MQTTController#mqtt handling stat/tasmota_75E505/POWER1 for "75e505_1": ON [###BUILDVERSION###]2022-04-03T17:37:38.494Z <MQTTController:5:MQTTController.js:626> MQTTController#mqtt setting Entity#mqtt>75e505_1 power_switch.state=true
You can see on line 10, it says
connected; opening subscriptions
, and then immediately thereafter it gets the retained messages from the broker. You should be able to confirm similar behavior at log level 5. Given that retain is a new feature for openLuup, I would suggest you confirm it's actually sending the messages; clearly it knows it should, but that doesn't prove it does. -
Yup, that's it. I moved the Tasmota device to Mosquitto and can replicate your log. So with openLuup I have to use
init
as it does not seem to respond with the retained messages at MSR startup.
I will consider moving all my devices to Mosquitto in the future, except for those I need to do Luup calculations and variable sets on virtual devices.Oddly the rebuild seems to resolved most of my problems and I'm now up to date with the MQTTController, which was the main issue. Thank you very much for that!
-
No worries!
Paging @akbooer.... see the last couple of messages above. Apparently @Crille has some retained messages (they show as retained in the openLuup UI) that are not being sent by openLuup's broker when Reactor subscribes. FYI, Reactor uses a "catch-all" subscription (complete wildcard, i.e.
#
is the entire subscription request). -
Thanks for the heads up. Clearly something missing here that needs to be investigated.