Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: April 4, 2022)

    • How does MSR handle renamed entities?

      3

      Hubitat C7 = 2.3.2.141 AND 2.3.3.123
      MSR in a docker = latest-22264-93bf3814 and latest-22266-88868fc0

      I'm curious if this is a bug or expected behavior. Unfortunately I don't know exactly when this began either. I have renamed a few devices over the course of the last few MSR builds, but never really brought it up before. Plus I don't rename devices too often. But I have a motion sensor right now that I renamed in Hubitat from "Office Motion" to "Living Room Motion" over 2 weeks week ago. Probably closer to 3 or 4 weeks now. I have restarted MSR several times since the rename, hard refreshed the browser, tried a different machine and different browser, and even an updated version of MSR. MSR is still showing the old name within the Entities section. I know I could rename it within MSR, but I would prefer to only have to rename devices in one location. I don't recall how long ago I started noticing this, which I know does not help at all.

      5f97eb06-aa1d-4f25-ba08-1212aa28f4bb-image.png

      Multi-System Reactor

    • InfluxDB - is it possible to log expressions as well as entities?

      A

      The reason for my question is a rather long story involving a virtual thermostat on my Hubitat and using InfluxDB and Grafana to graph the state of the thermostat.

      The TL;DR version is that it would be helpful if I could send MSR expressions (variables) to InfluxDB. I don't currently see any way to do that, and if it isn't a current capability of MSR it might be useful as a future enhancement.

      Long version: I have a rule in MSR that runs every minute to pull the thermostat information from my thermostat's cloud API. I parse the response into global variables, and then update a Hubitat virtual thermostat when those global variables change. I added the x_hubitat_Thermostat entity, along with selected capabilities, to my reactor.yaml in the InfluxDB section, 'default_capabilities', so the changes to the virtual thermostat get logged into the db.

      It's working OK except when the API reports that the temperature has reached the setpoint but the system is still operating. For example, in the morning when the heat is turned up, the temp will climb until the setpoint == the temperature, but the system will continue heating for a while afterwards. It's a variable speed/heat system so it continues to run at very low output for quite a while after the temps match.

      The issue I'm having is that when the temperature matches the setpoint, the Hubitat virtual thermostat switches to idle mode on it's own, despite the fact that the API is still reporting heating mode. When the virtual device sees that the setpoint has been reached, it automatically changes to idle, which makes sense as that's how you'd want a real thermostat to work .

      I am working around this by having the rule that updates the temperature on the virtual device also update the operatingState. This fixes it, but for just a few milliseconds the virtual thermostat switches to idle before the rule sets it back to heat, and that state change shows up in Grafana.

      If I could just directly log changes to the expressions to InfluxDB I could avoid the issue and get the same data into the database. Also I can see other applications for something like this with other APIs where MSR and InfluxDB could be used to log data without having any virtual device entities involved.

      Multi-System Reactor

    • MSR Not Recognizing Old HASS on New VM

      Pabla

      Hey Patrick, had to switch over my HA VM from VirtualBox to VMware since VirtualBox stopped playing well. Anyways I updated the IP address to the new VM IP and deleted the Long Lived Access Token and created a new one just in case (copy pasted the new token into the config file). Tried rebooting both the HA machine and the MSR one too and MSR is still not connecting. The only thing I have not tried yet is creating another controller entry, but I am worried it may create all new entities for everything forcing me to redo all my logic. Here are some logs:

      [latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:17:24.749Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:09.753Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:24.761Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:01.083Z <VeraController:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-22258]2022-09-20T21:19:14.780Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:29.785Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:24.791Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:20:39.813Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:39.820Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:20:39.820Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
      Multi-System Reactor

    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      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.
      Multi-System Reactor

    • Is there a search function (maybe a feature request)

      T

      @toggledbits

      Patrick,
      I've just imported a large set of rules from Vera, and I had already played with creating rules in MSR that are mixed throughout the existing Vera rules. Is there any sort of way to "find/replace" in MSR, so I can find all matches to the old rules and replace them with the new ones?

      Multi-System Reactor

    • Migration of House Modes

      T

      @toggledbits

      Patrick,
      Yesterday I migrated a large luup Reactor group over from Vera to MSR, following the directions to importing it from Vera in the documentation. One of the odd things in the migration was the conditional rules for House Modes. Many of my rules had conditions such as "House Mode is any of Home, Night, or changes to Away.

      The way the import did it was changes from 1,3 to null. This importation did not seem to trigger rules correctly.

      I was able to fix all the instances by creating multiple triggers in a group:

      Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains home
      OR Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains night

      Is this what you are expecting in importation?

      Multi-System Reactor

    • Using Google Calendar data from HA in Reactor

      T

      Good morning all,
      This weekend I've been playing around with Home Assistant as a replacement (long term) for my aging Vera platform. I'm pretty amazed how much more capability it has. On the other hand, the sheer amount of variables it pulls in from devices is massive.

      In any case, I have added Google Calendar into Home Assistant for things like Federal Holidays and my daughter's school calendar. It connected to them without issue, which I had been having problems with in Vera an GCal3.

      I connected MSR to Home Assistant, so I can start using some of the systems I've integrated into Home Assistant in MSR, and continue migrating my luup Reactor rules over to MSR. Now I'm trying to create a rule based on if today is a Federal Holiday or not. Reactor sees the calendar just fine, however, for whatever reason, it's not pulling data for today, but the next event, which in this case is Columbus day, three weeks away. The attribute that is pulling this is x_haas_attr.message.

      I tested with my daughter's school calendar, and it did have an entry for today, and none of the other values seemed to be different, such as a "true" or something to tell me there is an entry.

      a8478a6e-d8eb-4572-ac84-c94ff012a1ec-image.png

      60632486-e80b-4f0f-aed9-dc67113689a4-image.png

      ab04cd0f-f849-4e14-be7d-f4c00735da77-image.png

      The only thing I've been able to come up with, is there is a start_time attribute, which shows the date as 2022-10-10 00:00:00

      1cbe4526-7f63-4329-a088-b331f1d03376-image.png

      The only thing I can think of is there might be a way to compare the current system date to that date, but I can't seem to figure that out in MSR.

      Has anybody done this? Any suggestions?

      Multi-System Reactor

    • [Solved] VirtualEntityController setup

      G

      I started kicking around the VEC last evening, was cut short, and dug in a bit more this morning.

      My reactor.yaml:

      d3df4d99-aa7f-4b8b-8fb9-5a6c615daad9-image.png

      I verified the yaml is good at https://yamlchecker.com/

      What I'm seeing in MSR:

      0f89ce8e-7abe-4779-baca-43123e030cf4-image.png

      87560ded-7dfa-4340-8585-8be58ff22852-image.png

      I believe I have followed all steps (standard disclaimers apply).

      Anyone else started to tinker with this newness and, if so, what were your results?

      Multi-System Reactor

    • Approach to Rulesets, a philosophic question

      G

      Having just embarrassed myself to @toggledbits by asserting that the latest release somehow had a bug when in reality it was surfacing underlying issues with my approach to building out my rulesets and automations I wanted to ask the collective for their feedback on how they've designed their rulesets.

      For me, I built out a list of Global Reactions that I commonly use. For instance, for mode changes I typically change the mode entity and write that mode to a variable for some future use. When building out a ruleset I just pull in that Global Reaction vs manually recreating the entity list as my ruleset Reaction. Example, for lighting:

      270bbe18-9680-491d-81d4-20308a9fe63c-image.png

      Each of these contains the appropriate group of lights to turn on/off, etc.

      I also have what I've dubbed my "Armed for..." rulesets. These are rulesets that can be referenced as true or false in other rulesets. Example, for my various lighting configurations in and out of the house I have these:

      0d9f55d4-5d5d-42e2-a83c-8afa95df08fb-image.png

      I think this is resulting in reactions stomping on other reactions creating race conditions that result in things looking like they're working when, in reality, they're one restart away from disaster.

      So how are you all designing your superstructure, if you will, at a high level?

      Multi-System Reactor

    • Entity action & controllers

      tunnus

      Maybe more of a cosmetic issue, but certain entities could be hidden from entity actions as you cannot set any meaningful action? See Vera as an example:

      Screenshot 2022-09-16 at 15.11.29.png

      vera>system is then obviously a different story and should be there

      Multi-System Reactor

    • [MSR] MQTT not echoing variables in latest update

      therealdb

      Hi @toggledbits,

      I have a bridge consuming Vera's variable using the MQTTController in MSR, and I've noticed that after I've updated to the latest version (22257), some variables are not echoed. I've already tried to reboot MSR, with no luck.

      These variables are under urn:smarthome-community:serverId:Vacuum

      0fe837ed-3a29-4d5d-a06c-445981d44e13-image.png

      A trace via MQTT explorer:
      cf919028-4f7b-4761-b99a-c3943945704a-image.png

      My config has just exclude_capabilities: [] and it was working OK before the latest build. Even /query command doesn't seem to retrieve all the attributes. The values are retrieved correctly from the Vera controller, and I could use them in MSR, they're just not echoed to the bridge. Thanks!

      Multi-System Reactor

    • MSR Reaction question - Support with iBlinds on Vera

      T

      Good morning all,
      I"m working on converting my luup Reactor scenes over to MSR, so I can eventually introduce an Ezlo plus into the mix and not loose all the work I've done with Reactor. If nothing else, this should free up some resources on my aging Vera Plus, and maybe speed up some functions. Maybe that's just wishful thinking.

      In any case, I'm moving move my first Reactor set, which is a set of rules to control the blilnds/window coverings in my home. I have two types of blinds:

      iBlinds retrofit motors (IB2.1-ZWx) version from late 2019.
      Bali roman shades with factory installed Somfy CSZ1 Z-wave motors.

      I'm setting up reactions for both types of window coverings. One of the problems I always had in Vera was with iBlinds, I had to do it by luup commands:

      luup.call_action("urn:upnp-org:serviceId:Dimming1","SetLoadLevelTarget",{ newLoadlevelTarget="50" },316)

      The reason for this, is that the open position was 100%, and the close position was 0%. In other words, the blinds were closed one way 100% an closed 100% the other way. I've been informed by iBlinds support that even in Ezlo, they still do it this way, which is different than most other Z-wave controller manufacturers. I'm not sure how the others do it, but some how "open" is right in the middle (50%).

      So, in MSR, i can still set the Dimming1.SetLoadLevelTarget to 50, but I also noticed some other commands I haven't seen before in Reactor

      3cdeeb89-5986-45bc-8a3b-79067050a22c-image.png

      Is there some way in MSR to set that middle value to 50% so I can use cover.open? The command cover.close works as expected, so I'm wondering how I might use that cover.set.

      Thanks for any advise.

      Multi-System Reactor

    • OpenWeatherMap not providing any data

      T

      I configured OWM Weather on MSR (latest-22257-dd9b9271), created an account with OWM, generated an API key, put the key in the yaml file, and I’ve waited over a day now. OWM Weather shows as up on the the Controller Status widget.

      I’ve tried to create a trigger or constraint to use the data, and nothing is really showing up.

      5B8611C1-33D0-4D3C-B507-7383CB81E25A.jpeg

      I only have a free subscription with OWM, but I was expecting some data.

      Is this expected behavior (i.e., still in development), or do I do more configuration other than the .yaml file?’

      I still am able to pull Weather data through Dark Sky in my Vera plus controller, however, I know that will no longer work at some point.

      Multi-System Reactor

    • How to close these new metadata windows?

      cw-kid

      Was just looking at the new metadata stuff in Entities for a lamp. I was on the dimming.level attritube and I then changed the dim level of the lamp several times and some how I got all these windows.

      I then selected a different attribute color_temperature.value and that window was then shown over the top of all the others.

      267e6d0d-7245-4816-ac93-ac83cfda509e-image.png

      I don't know how to close these windows down ?

      b09fd5f1-fffe-40c2-8ba6-8cffacd1e28b-image.png

      Thanks

      Multi-System Reactor

    • Add Ability to Limit Amount of Time a Condition Pulses

      Pabla

      Hey Patrick, similar to R4V it would be nice if we could set the max amount of time a condition pulses. Currently in MSR you can only set it to pulse once or repeat continually until the condition goes false.

      I currently have a rule that pings dead devices and occasionally the dead device needs a few pings for it to come back alive but I don't want it to keep pinging forever if the device is actually not functioning.

      Multi-System Reactor

    • MSR web UI stops connecting after a period of time

      cw-kid

      Hi

      Anyone else been having issues with the MSR web UI not connecting after a period of time? Or is it just me?

      If I reboot the Linux Debian box then MSR starts working again and I can open the web UI and it says connected.

      However after sometime I then cannot later connect to the web GUI. It just says connecting all the time.

      I also have Node-Red and HA Bridge running on the same box and I can connect to those two fine still.

      Thanks

      Multi-System Reactor

    • ZWaveJS new device alerts

      S

      Is is possible for MSR to show newly detected ZwaveJS devices in the current alerts windows like Hubitat and HA? New devices show in the Entities but there is not an alert.

      Multi-System Reactor

    • Where do the icons come from?

      R

      Hi Patrick,
      For as long as I can remember, I have red x's instead of icons in MSR.

      05f25684-b338-4f69-8d0a-8a482a9fe1a2-image.png

      I am running MSR in Docker and am on version 22252. If hosted in the cloud, they could be getting blocked by pihole.

      Thanks,
      Roger

      Multi-System Reactor

    • [SOLVED] "Action must be edited to update to the latest stored form"

      A

      TLDR: I'm getting an alert saying I have to edit and re-save a rule containing a HTTP POST request in order to update it, but following the instructions in the alert doesn't seem to fix the issue.

      I am receiving this message in the Current Alerts when sending a HTTP POST request.

      The action at step 1 of "Send Notification Reaction" (re-I7yq7e15) needs to be edited to update it to the latest stored form. The action will continue, but should be updated as soon as possible, before this form is deprecated and no longer functions. Just make a trivial edit to the "headers" argument and then save the reaction to update it.

      Details:

      I am using a self-hosted notification system - Gotify. Many of my rules use a HTTP POST action to send a notification through this system. The message contains a JSON body with the title, body, and message priority. It is posted to a URL on my LAN where the Gotify server resides.

      When I updated to latest-22252-65e94b36 I started to receive the above error. Since I had the http request in many rules I took the opportunity to simplify things by moving the http request to a Reaction in the Reactions section of MSR. I created two variables to pass the notification content to the Reaction and now send all notifications via the one Reaction. Each rule that needs to send a reaction sets the variable values and then runs the Reaction.

      For example, this rule runs if the Kitchen Main leak sensor detects a leak. It sets the variable "g_gotify_token" to a value (this is used as part of the URL when making the HTTP request) and sets "g_gotify"body" to a JSON formatted string. In this case that string is

      { "title":"Water Alert", "message": "Kitchen Main Leak Sensor Tripped", "priority": 8 }

      Finally, the rule runs the Reaction "Send Notification Reaction"

      79fd4034-c611-4173-b4e4-18cf5091b453-image.png

      That reaction contains the http request. It uses the variables in the URL and request body fields. The request headers field is static and is set to "Content-Type: application/json"

      d75d9305-a5ab-4401-9b75-ea72d08787fa-image.png

      I get the same error when I directly call the HTTP request from a rule without using any variables. Either way, the notification goes through successfully. The only issue is the alert being raised in MSR.

      I tried editing and re-saving the Reaction, and also tried creating an entirely new reaction. I get the same warning message either way.

      footnote: Because I use the same process to send a notification whenever there is an alert raised in MSR, this also created a loop (that thankfully got throttled pretty quickly) where the system was making the http request to send a notification that this alert had been raised, and the action of sending that notification raised the alert again... etc...

      Is this just a bug? Am I missing something about the request format that needs to be updated? I checked the manual and this forum for answers, but didn't find anything that looked relevant.

      Multi-System Reactor

    • Reactor not showing full vera device parameters

      T

      I use a number of multistring devices in my vera plus. My 'original' multistring devices work in Reactor i.e.:

      9c5203dd-1993-4b5b-aeee-44377c1ee1c5-image.png

      42b97524-9428-4222-a3fb-ce4e0009c00b-image.png

      However, the new ones I have added do not show the device data sets / parameters (not sure what the correct term is?):

      a54ddf29-ea32-47c9-906e-260a25dcb482-image.png

      3efa1d0a-5466-4220-93d3-0a67da42a5d0-image.png

      Is there something that I am doing wrong?

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

    [Solved] Issue with Tasmota sensors and MQTTController later than 22024

    Multi-System Reactor
    3
    22
    158
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Crille
      Crille last edited by Crille

      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? 🙂

      1 Reply Last reply Reply Quote 0
      • toggledbits
        toggledbits last edited by

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

        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

        1 Reply Last reply Reply Quote 0
        • Crille
          Crille last edited by Crille

          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 is temperature_sensor.units

          pooltemp.PNG

          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"
          toggledbits 1 Reply Last reply Reply Quote 0
          • toggledbits
            toggledbits @Crille last edited by

            @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 have init in your config and there's an init 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!

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            1 Reply Last reply Reply Quote 0
            • Crille
              Crille last edited by

              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!

              toggledbits 1 Reply Last reply Reply Quote 0
              • toggledbits
                toggledbits @Crille last edited by

                @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).

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                1 Reply Last reply Reply Quote 0
                • Crille
                  Crille last edited by

                  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
                  retained.PNG

                  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"}

                  Gui
                  pooltemp_default.PNG

                  Crille 1 Reply Last reply Reply Quote 0
                  • toggledbits
                    toggledbits last edited by

                    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.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    1 Reply Last reply Reply Quote 0
                    • Crille
                      Crille last edited by

                      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
                      1 Reply Last reply Reply Quote 0
                      • toggledbits
                        toggledbits last edited by

                        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.

                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                        1 Reply Last reply Reply Quote 0
                        • Crille
                          Crille last edited by

                          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.

                          1 Reply Last reply Reply Quote 0
                          • toggledbits
                            toggledbits last edited by toggledbits

                            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 your init after uses_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.

                            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                            1 Reply Last reply Reply Quote 0
                            • Crille
                              Crille @Crille last edited by

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

                              1 Reply Last reply Reply Quote 0
                              • toggledbits
                                toggledbits last edited by toggledbits

                                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.

                                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                1 Reply Last reply Reply Quote 0
                                • Crille
                                  Crille last edited by

                                  This is from openLuup retained messages:

                                  retained2.PNG

                                  1 Reply Last reply Reply Quote 0
                                  • toggledbits
                                    toggledbits last edited by toggledbits

                                    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.

                                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                    1 Reply Last reply Reply Quote 0
                                    • Crille
                                      Crille last edited by

                                      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!

                                      1 Reply Last reply Reply Quote 0
                                      • toggledbits
                                        toggledbits last edited by toggledbits

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

                                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                        akbooer 1 Reply Last reply Reply Quote 0
                                        • akbooer
                                          akbooer @toggledbits last edited by

                                          @toggledbits

                                          Thanks for the heads up. Clearly something missing here that needs to be investigated.

                                          1 Reply Last reply Reply Quote 0
                                          • akbooer
                                            akbooer last edited by

                                            @Crille

                                            What topic(s) are you subscribing to which isn't sent? I have found a possible error if it contains a wildcard, but just wanted to check. Thanks.

                                            toggledbits 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

                                            Powered by NodeBB | Contributors
                                            Hosted freely by PointPub Media Communications Inc. | Contact us