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.0I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.
For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.
Good morning,
I'm going through my ruleset this morning, trying to get away from haas>blahblablah entries and completely migrate them all to zwavejs>xx-0 entries where possible.
I have 3 Aeon MultiSensor 6 devices in my home, all USB powered.
When using Haas entries, I see an entry for hass>binary_sensor_guest_bedroom_multisensor_home_security_motion_detection, and motion_sensor.state (primary)
Screenshot 2024-07-25 at 8.25.53 AM.png
Under ZwaveJS, this entry appears to be missing.
Screenshot 2024-07-25 at 8.26.51 AM.png
From the Entities page:
battery_power.level=1
battery_power.since=1721910337433
binary_sensor.state=false
humidity_sensor.units="%"
humidity_sensor.value=46
light_sensor.units="Lux"
light_sensor.value=5
tamper.state=false
temperature_sensor.units="°F"
temperature_sensor.value=73.8
x_debug.dt={}
x_zwave_values.Basic_currentValue=0
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Binary_Sensor_Any=false
x_zwave_values.Configuration_Automatic_Report_Group_1_Battery_1=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Humidity_64=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Luminance_128=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Temperature_32=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Ultraviolet_16=1
x_zwave_values.Configuration_Automatic_Report_Group_2_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_1=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_2=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_3=3600
x_zwave_values.Configuration_Automatic_Temperature_Reporting_Unit=2
x_zwave_values.Configuration_Battery_Level_Threshold=10
x_zwave_values.Configuration_Current_Power_Mode_65280=0
x_zwave_values.Configuration_Humidity_Above_Lower_Limit_32=0
x_zwave_values.Configuration_Humidity_Below_Lower_Limit_2=0
x_zwave_values.Configuration_Humidity_Change_Threshold=10
x_zwave_values.Configuration_Humidity_Recover_Limit=5
x_zwave_values.Configuration_Humidity_Sensor_Calibration=0
x_zwave_values.Configuration_LED_Blinking=0
x_zwave_values.Configuration_Lighting_Recover_Limit=10
x_zwave_values.Configuration_Lock_Configuration=0
x_zwave_values.Configuration_Low_Battery_Threshold=20
x_zwave_values.Configuration_Low_Temperature_Alarm_15_C=0
x_zwave_values.Configuration_Lower_Humidity_Limit=50
x_zwave_values.Configuration_Lower_Lighting_Limit=100
x_zwave_values.Configuration_Lower_Temperature_Limit_4294901760=320
x_zwave_values.Configuration_Lower_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Lower_Ultraviolet_Limit=4
x_zwave_values.Configuration_Luminance_Above_Lower_Limit_64=0
x_zwave_values.Configuration_Luminance_Below_Lower_Limit_4=0
x_zwave_values.Configuration_Luminance_Change_Threshold=100
x_zwave_values.Configuration_Luminance_Sensor_Calibration=0
x_zwave_values.Configuration_Motion_Sensor_Report_Type_to_Send=2
x_zwave_values.Configuration_PIR_Sensitivity=3
x_zwave_values.Configuration_PIR_Sensor_Timeout=20
x_zwave_values.Configuration_Recover_Limit_Temperature_Unit_255=2
x_zwave_values.Configuration_Report_Above_Humidity_Threshold_32=0
x_zwave_values.Configuration_Report_Above_Luminance_Threshold_64=0
x_zwave_values.Configuration_Report_Above_Temperature_Threshold_16=0
x_zwave_values.Configuration_Report_Above_Ultraviolet_Threshold_128=0
x_zwave_values.Configuration_Report_Below_Humidity_Threshold_2=0
x_zwave_values.Configuration_Report_Below_Luminance_Threshold_4=0
x_zwave_values.Configuration_Report_Below_Temperature_Threshold_1=0
x_zwave_values.Configuration_Report_Below_Ultraviolet_Threshold_8=0
x_zwave_values.Configuration_Reset_Parameters_101_103_to_Default_Values=null
x_zwave_values.Configuration_Reset_Parameters_111_113_to_Default_Values=null
x_zwave_values.Configuration_Reset_to_Factory_Default_Setting=null
x_zwave_values.Configuration_Selective_Reporting=0
x_zwave_values.Configuration_Sleep_State_255=2
x_zwave_values.Configuration_Temperature_Above_Lower_Limit_16=0
x_zwave_values.Configuration_Temperature_Below_Lower_Limit_1=0
x_zwave_values.Configuration_Temperature_Calibration_Offset_65280=0
x_zwave_values.Configuration_Temperature_Calibration_Unit_255=2
x_zwave_values.Configuration_Temperature_Change_Threshold_4294901760=20
x_zwave_values.Configuration_Temperature_Recover_Limit_65280=20
x_zwave_values.Configuration_Temperature_Threshold_Unit_3840=2
x_zwave_values.Configuration_Ultraviolet_Above_Lower_Limit_128=0
x_zwave_values.Configuration_Ultraviolet_Below_Lower_Limit_8=0
x_zwave_values.Configuration_Ultraviolet_Change_Threshold=2
x_zwave_values.Configuration_Ultraviolet_Recover_Limit=2
x_zwave_values.Configuration_Ultraviolet_Sensor_Calibration=0
x_zwave_values.Configuration_Upper_Humidity_Limit=60
x_zwave_values.Configuration_Upper_Lighting_Limit=1000
x_zwave_values.Configuration_Upper_Temperature_Limit_4294901760=824
x_zwave_values.Configuration_Upper_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Upper_Ultraviolet_Limit=8
x_zwave_values.Configuration_Wake_Device_for_10_minutes_After_Power_On=1
x_zwave_values.Configuration_Wake_Up_Timeout=15
x_zwave_values.Manufacturer_Specific_manufacturerId=134
x_zwave_values.Manufacturer_Specific_productId=100
x_zwave_values.Manufacturer_Specific_productType=258
x_zwave_values.Multilevel_Sensor_Air_temperature=73.8
x_zwave_values.Multilevel_Sensor_Humidity=46
x_zwave_values.Multilevel_Sensor_Illuminance=5
x_zwave_values.Multilevel_Sensor_Ultraviolet=0
x_zwave_values.Notification_Home_Security_Cover_status=0
x_zwave_values.Notification_Home_Security_Motion_sensor_status=0
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Version_firmwareVersions=["1.17"]
x_zwave_values.Version_hardwareVersion=100
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="4.54"
x_zwave_values.Wake_Up_controllerNodeId=1
x_zwave_values.Wake_Up_wakeUpInterval=3600
zwave_device.capabilities=[32,48,49,112,113,114,128,132,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Sensor"
zwave_device.impl_sig="23326:1:22315:1"
zwave_device.is_beaming=false
zwave_device.is_listening=true
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[134,258,100]
zwave_device.max_data_rate=null
zwave_device.node_id=53
zwave_device.specific_class="Routing Multilevel Sensor"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"1.17"]
zwave_device.wakeup_interval=3600
I'm running:
Reactor latest-24190-bd310acc, Bare-metal on Fedora
WaveJSController [0.1.23326]
Home Assistant: 2024.7.0
I'm fetching certain data five past every hour, but I would like to do it closer to the hour, e.g. 1 or 2 past (but not at the hour).
I experimented with the following rule that almost works (triggers also at the hour which is not the intention). Any advice for a solution?
It would be nice to have an ability to bookmark a direct link to a dashboard item. In my case I would use this feature to access a virtual switch directly.
Hi @toggledbits
Would you please consider adding an extra sublevel in the rulesets?
I have grouped my rules in rooms/ areas. This works great for me, but I would also like to group rules for the same functionality (in a room). This would make the rules easier to find and name.
Please let me know if this is an option. Thanks!
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits,
I have this device attached to my system, but use a DSC panel. If you need testers to move forward, I'm happy to help.
I'm curious what your thinking the use case is for this. I currently have it integrated into HomeAssistant, and it works fine for the most part. The one thing I can't do is bypass zones, which I would like to have the ability to do.
Are you looking at more direct control for the panel, as opposed to having to jump through HA (or another system) first?
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.I have the following ruleset which I though had been working well until this morning when I noticed it's not.
I've put four weather conditions in an in array and one of them is the current weather condition - but the rule is not true. Now the cloud cover percentage is not yet met but this is an or rule so as long as the "Current Conditions" are met then it should go true.
What's the obvious thing I'm missing here? (I've tried spaces/no spaces in the in and no difference.)
Hi,
Running the latest MSR latest-24152-3455578a with the latest HA 2024.6.1. When trying to call a service I get the following in the MSR logs. Is this a version mismatch? I am not seeing anything in the HA logs.
[latest-24152]2024-06-11T10:29:56.162Z <Rule:INFO> rule-Monitor-DHW (rule-lsvq5k3x in Central Heating) started [latest-24152]2024-06-11T10:29:58.625Z <HassController:WARN> HassController#hass unknown service opentherm_gw.set_hot_water_setpoint in x_hass.call_service action on Thermostat#hass>climate_living_room_otgw [latest-24152]2024-06-11T10:29:58.626Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Thermostat#hass>climate_living_room_otgw action: [Object]{ "type": "call_service", "service_data": { "gateway_id": "living_room_otgw", "temperature": 65 }, "domain": "opentherm_gw", "service": "set_hot_water_setpoint", "target": { "entity_id": "climate.living_room_otgw" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:ERR> HassController#hass request 1718101798626<6/11/2024, 12:29:58 PM> (call_service) failed: [Object]{ "id": 1718101798626, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "extra keys not allowed @ data['entity_id']" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:WARN> HassController#hass action x_hass.call_service([Object]{ "service": "opentherm_gw.set_hot_water_setpoint", "data": "{ \"gateway_id\": \"living_room_otgw\", \"temperature\": 65 }" }) on Thermostat#hass>climate_living_room_otgw failed!Cheers Rene
Some background
I'm trying to integrate a Zigbee device into the MSR using zigbee2mqtt bridge and MQTTController. The device in question is a cheap mood light that has following properties that I'd like to control:
I'v already managed to get the switch part working and can toggle the light on/off. Also the brightness value is mapped back to MSR. In zigbee2mqtt it has a value range from 0 to 254, so this the reason for the expression:
expr: 'payload.brightness / 254'Here's the entity definition (don't know whether the type should be something else than the Switch)
zigbee-lidl-mood-light: name: 'Lidl Mood Light' friendly_name: 'Mood Light' type: Switch uses_template: lidl-moodlightAnd the corresponding template (NOTE: rgb_color has not been defined in this example):
lidl-moodlight: init: "zigbee2mqtt/%friendly_name%/get/state" query: "zigbee2mqtt/%friendly_name%/get/state" capabilities: - power_switch - toggle - dimming primary_attribute: power_switch.state events: "zigbee2mqtt/%friendly_name%": "power_switch.state": json_payload: true expr: 'upper(payload.state) == "ON"' "dimming.level": json_payload: true expr: 'payload.brightness / 254' actions: power_switch: "on": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'ON' "off": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'OFF' set: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: expr: "parameters.state ? 'ON' : 'OFF'" type: raw toggle: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'TOGGLE'The problem
In order to control the brightness or the RGB color values, I would have send a JSON payload in corresponding actions. But I have no idea how to define it in the template. The reason why the switch part is working is that the zigbee2mqtt accepts also plain ON / OFF / TOGGLE string payloads in that case.
But the brightness should be controlled with the following payload:
{"brightness": 196}And the RGB color like:
{"color":{"rgb":"46,102,150"}}Here's the link for the documentation (the Exposes part defines the messages).
So how should I define the JSON payload for example for the dimming action? It definitely should be some sort of expressions since I have to map the MSR real value (0...1) to (0...254) for the zigbee2mqtt.
actions: dimming: set: topic: "zigbee2mqtt/%friendly_name%/set" payload: expr: ????? type: jsonAnother problem is the RGB value. I could use the rgb_color capability for the setting but the problem is that the zigbee2mqtt only reports the current color in hue/saturation or xy coordinates.
Here's an example of published message after setting the color:
Topic: zigbee2mqtt/Mood Light QoS: 0 { "brightness":254, "color":{ "hue":240, "saturation":100, "x":0.1355, "y":0.0399 }, "color_mode":"xy", "color_temp":574, "linkquality":96, "state":"ON" }I would have to map those values back to RGB, but is it even possible with existing constructs in MQTTController's templates?
Help would be appreciated @toggledbits
br,
mgvra
That's probably more appropriate to post on Mantis for @toggledbits, but since I know there's at least @Crille publishing templates, my intent with this post is to open a broader discussion.
Long story short: I'm starting to slowly add new template for Shelly Plus and I noticed I'll end up with a dozen more templates, all similar but simply different in trivial details, all sharing a large amount of code and all needing special cares when fixing bugs/adding features (as the latest wifi_status addition).
So, I'm wondering if it's time to start thinking of some sort of inheritance in templates, where I could just create a generic shelly_gen1 and use it as a base for shelly_relay, and this be used as the base for shelly_relay_power and so on.
I could probably achieve this with some sort of scripting on my side to generate templates via code, but maybe there's a better way of doing this, or it's already on the radar.
I need a handful of victims volunteers to help test previews of the next build of Reactor. A long-standing request was for "a simple login mechanism," but in practice, adding user authentication and competent access control turned out to be a pretty big project with a lot of big changes on both server and client sides. It's a bit more than I'm comfortable testing myself and springing out to everyone at once, so I'd like to work with a small group to put it through "sea trials."
Major changes/features include:
User authentication with hashed password storage; User group configuration with application restriction (admin, dashboard, API); Detailed control over API access, with user- and token-based authentication/authorization; Improvements to the HTTPS service; Improvements to UI coordination with the core for Rules and Reactions.If this sounds like something you'd like to help with, drop me a reply here in this thread or privately.
[Solution: Reactor 24115 is not compatible with MQTTController > 24120]
Reactor latest-24115 bare metal.
All MQTT entities stop working after updating MQTTController to 24142, downgrade to 24120 and they are back. Templates and configured entities has not been changed between versions.
I'm not sure if uses_template should be replaced by ìnclude in entity configuration in reactor.yaml but I guess not, I've tried it and it did not do any difference.
I have not tried to update Reactor to userauth version.
Example entity in reactor.yaml that uses MQTTController included template:
entities: "takflakt_kallare": name: "Takfläkt källare" topic: "Källartemp" unit: "" uses_template: tasmota_generic_relay init: "cmnd/%topic%/POWER%unit%"Any hints? Do you need more info, please let me know.
Log from startup:
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
![](https://github.com/fluidicon.png)
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Is the following config correct?
- id: time_series name: "Out temp" capabilities: temperature_sensor: attributes: value: model: time series entity: "hass>sensor_outdoor_temperature" attribute: "temperature_sensor.value" interval: 5 # minutes retention: 20 # minutes aggregate: wma primary_attribute: temperature_sensor.value type: ValueSensorSpecifically, is "depth" directive needed/mandatory here? Reason I'm asking is that I'm not getting a "final" value in MSR, only debug values are shown:
temperature_sensor.units=null temperature_sensor.value=null x_virtualentity.last_request_time=null x_virtualentity.request_failures=null x_virtualentity.template=null x_virtualentity.timeseries_debug=[{"time":1716537360000,"value":22.1},{"time":1716537660000,"value":22},{"time":1716537960000,"value":22},{"time":1716538260000,"value":21.9},{"time":1716538560000,"value":22}]Good morning,
I apologize if this subject has been covered. I did try the search, but I'm not coming up with any topics on my issue.
I'm running userauth-24137-57b41335, bare metal installation on Fedora 39 Server.
I have a rule set up to turn the Eco mode off on my Nest Thermostat when the thermostat is set to Away (Rule State: Away Mode), the user (Driver) presence in my car changes to true, and the destination is set to home.
93804f7c-62d6-42c0-ae04-ff602011a6fd-image.png
This works fine for most days, where I'm headed home from work (commute is about 45 minutes). What I don't want it to do is set change it to Eco mode if my ETA is more than an hour.
There is a sensor/entity for Time to Arrival when the Destination is set. What it appears to provide is the Time OF arrival/ETA, not time until arrival. If it was Time until Arrival, and it was a numeric value, I could simply test if the value is less than 60 and be done with it.
I pulled up the history through Home Assistant for my morning commute and this appears to be what it is providing.
c2a32739-c84f-4a05-95d9-73793ed818f5-image.png
So what I need to do is to do a calculation of the the ETA from the sensor value and subtract the current time, and get a value in minutes that I can determine if it's less than 60.
I believe I can do this with the local expression, but I don't see anything for the system time, or local time. Also, do the local expressions update themselves if the sensors do?
Good morning,
I'm running userauth-24137-57b41335 on Fedora 39, bare metal installation.
ZWaveJSController 0.1.23254
Home Assistant:
Core, 2024.5.3 Supervisor, 2024.05.1 Operating System, 12.3 Frontend, 20240501.1I'm trying to troubleshoot a Dynamic Group Controller and notification alert that I've set up for low battery level.
In my Reactor.config, I have the following lines:
name: "Dynamic Group Controller" implementation: DynamicGroupController config: groups: "zwavejs_dead": select: - include_group: "zwavejs" filter_expression: "entity?.attributes?.zwave_device?.status == 3" group_actions: true "low_battery": select: - include_capability: battery_power filter_expression: > entity.attributes.battery_power.level < 0.35The idea here is that I should only have members of this group that have a battery level below 35%. When I go into Entities, I show a whole slew of devices, none of which have a battery level below the threshold.
a77e445b-ab78-4752-a624-3c4117f34f90-image.png
I also tried setting up a rule to generate a push notification once a day, but with all of the group members, I've had to disable the rule. I believe I have it set up correctly, but I'm not 100% sure. I want the notification to tell me the battery level for that device as well.
289b4f68-03ba-49c0-8275-f0f197d13a3a-image.png
ce24a76e-6865-40bd-bd85-632e54d315a8-image.png dc837424-deb5-4ef7-8f0d-3676f1769535-image.png
Can anyone point to me what I may have misconfigured to get these results?
I should also note I'm only interested in ZWaveJS devices. It's showing me battery status for my iPad and car as well, which I don't need it to send me.
[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.