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
    1. Home
    2. Crille
    • MSR No longer Setting Reactions

      T

      Hello Everyone -

      I have a peculiar situation that I'm hoping to get some help with.

      Running Vera which is still handling my Zwave, MySensors, Zigbee, and still a balance of my Reactors.

      However, I've also been running MSR for several months in preparation for an eventual move off of Vera.

      Vera had one of its meltdowns this morning related to my Opensprinkler plug in.

      After getting that straightened out, I added the OpenSprinkler plugin to HAAS and that's when I started having issues.

      My existing MSR reactors (even simple ones) don't seem to fire their reactions. I can see the conditions go "true". If I manually fire the Reaction, it works fine.

      I do see this a lot in the logs:

      [1.0.2-21350]2022-05-16T19:02:44.518Z <Rule:INFO> Rule#rule-460 evaluation in progress; waiting for completion

      (Various rules - 460 is just an example)

      Is there anything I can do to further troubleshoot?

      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
    • MSR Telegram Messages Stopped Working

      T

      My MSR has been working flawlessly until a couple of days ago when it stopped sending Telegram Messages (or should I say they stopped getting through!). I have updated to MSR version 22004. The reactor.log is updating and is showing no errors:

      [latest-22004]2022-05-15T17:52:31.417Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.417Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:31.704Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.735Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.736Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:32.007Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:32.035Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:32.036Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:41.324Z Engine:INFO Enqueueing "Variable Telegram Test" (re-kvnm57c3)

      If I use the following in my web browser the telegram message gets through:

      https://api.telegram.org/botxxxxx......./sendMessage?chat_id=xxxxx......&text=Test Message HTTPS

      I am running MSR on my QNAP network attached storage. Any assistance would be appreciated.

      Just another question...... I would like to post in the HOME HARDWARE VERA section of Smarthome, but I do not have the option to set up a new post. Do I need to request access for this?

      Multi-System Reactor
    • Lovelace initial setup

      PerH

      I've just started to look at HASS UI, and have seen enough to see that it has an infinite number of ways to show enitites and devices in all forms and shapes.. But for starters i'd like to have something familiar, so how do i go about getting a sidebar for rooms like in openluup?

      I know i can put them in the actual left sidebar, but i'd prefer to keep that for configuration pages..

      on each room page i'd like to sort the lights, the heaters, the sensors together, and i saw somewhere that HASS will do that for you if you play your cards (pun) right.. can't find it again now..

      Any pointers to a beginner?

      Home Assistant
    • SSL Certificate for Multi System Reactor via LetsEncrypt

      W

      Details of runtime environment:

      Reactor (Multi-hub) stable-22055-9b40e12 Running as a service on Windows Server 2022 Std 21H2 Connecting to HASS (HASSOS) Is a migration WIP from OpenLuup/Reactor

      A complete description of your objective:

      Using LetsEncrypt, application "certifyTheWeb", retrieve and apply SSL certificate to Multi System Reactor

      A description of your approach/solution/implementation so far:

      Reviewed Config files, can't seen mention of certificate files in there

      Actual Question:

      How do I apply a certificate to whatever web server Reactor uses? I'm familiar with managing certificates on IIS and Apache but Reactor doesn't use either of these and I have not been able to locat ethe config file that Reactor uses for this. Which config file needs editing to apply a certificate? Does it use the computer certificate store or it's own store (e.g. pem files)

      The reason I want to achieve this, other than the general goodness of having everything I can in TLS is that I have Reactor as an IFRAME in my HASS console and as HASS is HTTPS and Reactor is HTTP then the iframe refuses to open.

      Search for "certificate" or "ssl" did not reveal anything relevant in this forum.

      Multi-System Reactor
    • MSR ZEN32 weird behavior

      R

      @toggledbits
      Hi Patrick,
      Running HASS 2022.5.3
      MSR zwavejs-22126-834c3e9

      Seeing weird behavior in MSR with regards to my Zen32's. Not sure how to capture info that might be relevent but will describe what I am seeing.
      In the example below I pressed scene 001 4 times. It flashed and changed the primary value to "4". The remaining buttons were previously showing the PV as "double" I pushed each button one time and they flashed and displayed the PV as 4.
      zen32.JPG

      In the zwavejs2mqtt debug screen that sequence looks like this.

      2022-05-10 09:38:44.078 INFO ZWAVE: Node 45: value notification: 91-0-scene-001 5 2022-05-10T16:38:44.081Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x898501" } 2022-05-10 09:38:45.982 INFO ZWAVE: Node 45: value notification: 91-0-scene-002 0 2022-05-10T16:38:45.984Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8a8002" } 2022-05-10 09:38:47.807 INFO ZWAVE: Node 45: value notification: 91-0-scene-003 0 2022-05-10T16:38:47.810Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8b8003" } 2022-05-10 09:38:48.858 INFO ZWAVE: Node 45: value notification: 91-0-scene-004 0 2022-05-10T16:38:48.861Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8c8004" }

      Let me know what other info you would like me to supply.
      I have played around with a bunch of other key stroke combo's and it looks like buttons 2-5 display what ever button 1 is set to.
      Have tested this on 4 different ZEN32's and it is same on all.

      Multi-System Reactor
    • HASS 2022.5 issue with ZwaveJS in MSR

      R

      Running zwavejs-22118-baab576 in MSR, HASSOS 2022.5.1

      Due to an unreported issue in HASS, when I upgraded the 2022.5 yesterday, it dropped ZwaveJS2MQTT from my HASSOS build. Finally got it reinstalled and it appears to be working the way it was previously.
      MSR is now showing zwavejs down and in entities, nothing is updating.

      Seeing this in the logs:
      ZWaveJSController#zwavejs ws_open caught [Error]Error: connect ECONNREFUSED 192.168.0.16:3000

      Are there additional steps needed that are not mentioned in the manual?
      At a loss to figure out what is causing issue.

      Multi-System Reactor
    • Syncing of updates...

      CatmanV2

      ....but not what you think, probably.

      I doubt there's an answer here to this, and it's about Iphone locator (sorry!)

      Hopefully the question is, at least, slightly interesting.

      Polling on the phone is currently set to 5 minutes and IPhone locator appears to update every 5 minutes as I also get an update in the OpenLuup log every 5 minutes.

      The 'problem' is that the Iphone locator (and therefore any conditions based upon a change in value) are happening 4 minutes and some seconds after the phone polls and updates its position. So effectively the phone is moving for nearly 10 minutes before any notification takes place. Which is a bit slow for my desired application.

      As an example:

      2022-05-05 17:27:08.244 luup.variable_set:: 55.urn:upnp-org:serviceId:IPhoneLocator1.MsgText2 was: 28.35 Km @ 0.00 Km/h on 2022-05-05 17:17 now: 28.35 Km @ 0.00 Km/h on 2022-05-05 17:22 #hooks:0 2022-05-05 17:32:12.340 luup.variable_set:: 55.urn:upnp-org:serviceId:IPhoneLocator1.MsgText2 was: 28.35 Km @ 0.00 Km/h on 2022-05-05 17:22 now: 27.77 Km @ 6.92 Km/h on 2022-05-05 17:27 #hooks:0

      Where you can see that the phone must have updated its location between 17:27:08.244 and 17:28:00.000

      Anyone got an bright ideas how I can reduce the discrepency?

      Cheers!

      C

      Software
    • Global Expression – Reference Error

      wmarcolin

      Hi!

      After several tests, restarting the computer where the MSR is, and the MSR itself by Tools > Restart, I have a persistent error in the logs.

      32d45bc3-51f8-4718-a113-3381e9d7edf2-image.png

      Looking at the global expression (screen below), I see that it is highlighted as an error, however, if I look at two other expressions above that have the same structure, they do not present an error, so I do not think the problem is with the expression's code.

      ca8a7867-4ac7-4f9a-9913-15a80da18f05-image.png

      This expression uses a group, which validates 4 devices of type door sensor, whether the status is true or false, door open or closed.

      "dgc_entrance_open": name: DGC Entrance Open select: - include_entity: - "hubitat>37" - "hubitat>38" - "hubitat>99" - "hubitat>130" filter_expression: > entity.attributes?.door_sensor?.state == true

      I also compared it with other groups, the structure is identical.

      Looking at the 4 devices in this group, I see that all are active in the MSR, have similar variables, are used in other groups and rules that do not present a problem.

      52b099f4-b9c4-46cb-ad3d-c873b09b7e13-image.png

      Looking at the log, I understand that it refers to some object that would be null, at which point I am lost on what to actually look at.

      [latest-22118]2022-05-02T22:33:11.711Z <Engine:INFO> Reaction Engine starting [latest-22118]2022-05-02T22:33:11.719Z <Engine:INFO> Checking rule sets... [latest-22118]2022-05-02T22:33:11.746Z <Engine:INFO> Checking rules... [latest-22118]2022-05-02T22:33:11.748Z <Engine:INFO> Data check complete; no corrections. [latest-22118]2022-05-02T22:33:11.892Z <Engine:ERR> [Engine]Engine#1: error evaluating expression EntranceOPEN: [ReferenceError]ReferenceError: Invalid scope in reference to member attributes of (object)null [latest-22118]2022-05-02T22:33:11.893Z <Engine:ERR> [Engine]Engine#1: expression: sort(each id in ( getEntity('groups>dgc_entrance_open').attributes.sys_group.members ): getEntity(id).name) [latest-22118]2022-05-02T22:33:11.894Z <Engine:CRIT> ReferenceError: Invalid scope in reference to member attributes of (object)null ReferenceError: Invalid scope in reference to member attributes of (object)null at _run (C:\MSR\reactor\common\lexp.js:1449:31) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1536:38) at _run (C:\MSR\reactor\common\lexp.js:1480:33) at C:\MSR\reactor\common\lexp.js:1283:29 at Array.forEach (<anonymous>) at _run (C:\MSR\reactor\common\lexp.js:1282:28) at run (C:\MSR\reactor\common\lexp.js:1663:22) at Object.evaluate (C:\MSR\reactor\common\lexp.js:1699:20) [latest-22118]2022-05-02T22:33:12.232Z <Engine:NOTICE> Reaction Engine running! [latest-22118]2022-05-02T22:33:12.233Z <Rule:INFO> Rule#rule-kxjp2el2 (Mode DAY) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjp7kc8 (Mode EVENING) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjparz7 (Mode NIGHT) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjpd0d6 (Mode AWAY ∆) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqrcr9 (Mode PARTY) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqyhnu (Mode VACATION ∆) started

      Finally, if I return the expression and press the Try This Expression button, it is executed and the error disappears.

      102e5013-b9aa-4c26-98f5-1ae545f8897f-image.png

      This situation started to occur on the latest version of Reactor 22118, on a Windows 10 Bare Metal installation. Does anyone have a similar scenario?

      Sorry for the long post, I tried to document as best as possible to try to identify the problem.

      Thanks.

      Multi-System Reactor
    • Cheapest platform on which to run MSR

      T

      Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.

      Multi-System Reactor
    • Build 22118 - entity updates

      G

      I just noticed that the new hotness picked up the entities from when I added an integration temporarily to my Home Assistant and popped a lovely info notice into the Alerts pane.

      I know the info is new - but when did MSR suddenly become more real-time with devices being added to hubs? This is great!

      Multi-System Reactor
    • [Solved] Is there a cap or max number of devices a Global Reaction should not exceed?

      G

      Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.

      This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.

      "What changed?"

      No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSR

      I did do a z-wave "repair" last night and am waiting to see if this helps.

      Is there any maximum or cap on number of devices that should be included in a Global Reaction?

      *Marked as solved as the question asked was answered. The issue persists but the question was answered.

      Multi-System Reactor
    • [Solved] Which version of npm should we be running for reactor-latest-22118-0f0772c.tar.gz

      G

      I've borked my install of reactor-latest-22118-0f0772c.tar.gz for some reason and am retracing steps. Running npm i --no-save --omit dev prompted to update npm and I did (current version now 8.6.0). Currently, attempts to load via browser/s (Brave and Safari) result in "This site can’t be reached192.168.1.xxx refused to connect." I am still able to SSH into the RPi.

      I haven't panicked yet but did just pull my config and storage directories - I believe I read where that's enough for a back-up if a clean install ends up being needed.

      So the question of the day: which version of nmp should we be running on for the latest Reactor?

      Multi-System Reactor
    • Is a global timestamp expression possible ?

      B

      I’ve looked and can’t find the answer which concerns me that the answer is obvious and thats why I can't find the answer to this.

      I’m new to MSR and this is my first post, so please bare with me 🙂

      What I’m trying to do is have a global expression that contains the current time so I can use it in Global reactions as well as Rulesets as part of my syslog messages.

      Example of what I’m experiencing:
      In Expressions, create a global expression: gMyTOD = strftime("%T %D”)
      In Rulesets, in a rule, create a local expression: MyTOD = strftime("%T %D”)

      In that same rule create a Notify type of Syslog.
      Set syslog message to: gMyTOD time is ${{gMyTOD}} and MyTOD time is ${{MyTOD}}
      Trigger the rule.

      The result is that the local expression (MyTOD) contains the correct time but the global expression (gMyTOD) does not update and reflects the wrong time in the final syslog message.

      Is there a different approach I should be using?

      Thank you in advance for any insight.

      -bh

      Multi-System Reactor
    • Restart router when it's gone offline?

      F

      Hi!
      Once a month or so, my internet access is lost, and I have to cut the power to the router, to restart it. When I'm away this become a problem, so I thought that if I got a zigbee switch (in Home Assistant), problem is solved. But how do I (MSR) know if it's offline?

      What's the easiest and most effective way to make this work? Do I ping a few websites every ten minutes or so, or is there a better approch? If I'm going to ping, what URL is recommended?

      For information, I have a set up with Asus routers, Home Assistent with zigbee-, z-wave and wifi devices (a total of appr. 150) and every of my 60-70 automation is done by MSR.
      I run MSR ver. 22080-ae7212f (docker on my Home Assistant blue). HA ver 2022.4.6.
      Thanks in advance.
      Take care, you all!
      /Fanan

      Multi-System Reactor
    • Latest ALTUI version brakes Reactor

      M

      FYI.

      Recently a new ALTUI version got pushed out, release 2553. After the update Reactor is no longer showing any of the Control panels in a sensor. looking at the ALTUI changes they seem minimal so in J_ReactorSensor_UI7.js I upped the _MAX_ALTUI_VERSION to 2553 and all seems to be working again.

      Vera/openLuup plugins
    • MSR for Scene Controllers

      therealdb

      I still have some code running on my Vera that I want to port and it's related to scene controllers.

      I'm mostly using Fibaro's switch/roller shutter and on the Vera side I'm getting sl_CentralScene/sl_CentralSceneAttr, but it seems too fast to be intercepted by MSR.

      What's anyone using? Thanks.

      Multi-System Reactor
    • Best strategy to get the difference between pulses in MSR

      therealdb

      So, I have a rule set that it's triggered when a local variable changes. Since it's tied to my solar production, it could change very frequently, so I've just added a reset delay to calm it down, but it's not working as intended.

      What I really need is a way to, let's say, define a percentage and define a variable to understand if the new value has changed +/- 10% before going true.

      I've tried a couple of ways, but I'm posting here anyway, in case anyone has found a better way to tackle this. Thanks!

      Multi-System Reactor
    • Status of MSR in Home Assistant

      Matohl

      Perhaps a dumb question. Can I check from Home Assistant that MSR is up and running? I would like to see that in a status page in HA. I can of course ping the other Pi but it doesn't say anything about the MSR status.

      Skärmavbild 2022-04-23 kl. 18.23.03.png

      Multi-System Reactor
    • Notifications from Alerts

      Crille

      @toggledbits Is there a way to get Current Alerts as an entity so I could monitor those and send notifications if needed.
      My usecase is sometimes openLuup crashes and MSR picks that up pretty quick, sending a pushover notification to me would get my attention to restart it.
      Of course there are many ways to monitor connectivity but since MSR already is doing that it would be neat to take advantage of it.

      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
    • Profile
    • Following 0
    • Followers 0
    • Topics 19
    • Posts 215
    • Best 48
    • Groups 0

    Crille

    @Crille

    73
    Reputation
    80
    Profile views
    215
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Crille Unfollow Follow

    Best posts made by Crille

    • RE: Instant regret after clicking "Configure Node Right Now" on device

      @librasun I totally understand your philosophy and tried to stick with stock setups as well but who has the time and patient to wait for Ezlo to accomplish a fraction of what is available already today.
      That said, I'm so thrilled I started migrating to openLuup and MSR, best decision ever! Sure it's not going to be easy for anyone to take over this setup but the possibilities and stability is totally worth it.

      @akbooer and @toggledbits you guys rock!!

      Homebridge is the key for Apple devices regarding manual control for WAF.

      posted in Vera
      Crille
      Crille
    • Localization

      @toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
      I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
      If so, do you want feedback here or in mantis?

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: Vera account suspended for a 1000 years

      @akbooer I’m afraid you’re right. They read your pm.
      I’m not banned, just joining another, perhaps more interesting forum 🙂

      posted in Vera
      Crille
      Crille
    • RE: Vera account suspended for a 1000 years

      WTF me too!

      posted in Vera
      Crille
      Crille
    • RE: Vera firmware 7.32 beta

      @wmarcolin I haven’t decoupled my Vera but use Homebridge for all local and remote control.

      posted in Vera
      Crille
      Crille
    • RE: Unexpected stop of openLuup

      @akbooer I'm still having a lot of crashes but since I added an autorestart of the service it's not really a major problem anymore.
      Even though openLuup is rock solid for most people, may I suggest you add

      [Service]
      Restart=on-failure
      RestartSec=5s
      

      To the documentation for openLuup in the appendix for systemd?
      At least it helped me not coming home to a dead house 🙂

      posted in openLuup
      Crille
      Crille
    • RE: Moving to Docker

      @akbooer and @LibraSun I think mine had an update button in AltUi and I just pressed it. After that VeraBridge showed up as a device and I configured it.

      posted in Docker
      Crille
      Crille
    • RE: Can someone explain for me how to use Reset reaction in MSR without disturbing other rules.

      @toggledbits Yes, you are correct. My goal in my head was to make the Constraints condition FALSE to prevent the SET Reaction.

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: Instant regret after clicking "Configure Node Right Now" on device

      Without openLuup and the excellent Ezlo Bridge, my Ezlo Plus would just annoy me and make me want to go somewhere else, as they kind of hinted with the ban raid.
      Big thanks to @mrFarmer ! for making use of the very beta product they shipped.

      posted in Vera
      Crille
      Crille
    • RE: Apple Homepod mini

      I love the simplicity of raising my hand and say to my watch "Open right garage door" when I'm approaching my home in my car, and if I forget, Siri asks me if I want to open it since I'm entering my geofence 🙂

      posted in General Discussion
      Crille
      Crille

    Latest posts made by Crille

    • RE: MSR Telegram Messages Stopped Working

      @talisker I would also change the logging level for Telegram by adding this to your logging.yaml, while trobleshooting, and restart Reactor. Add it in the same section as Engine:

      NotifyTelegram:
        level: 7
      

      The logs should now tell you a bit more and when done you can change it back to level 4.

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: Any decent destination for a Vera Plus?

      @parkerc The old unmaintained one from damianxd is in fact working fine with openLuup but it's not very efficient as it polls very frequently. I'd go the MQTT path as well with Mqttthing.
      The only downside I see is that openLuup must be set to publish every variable update which for me causes a lot of unnecessary traffic.

      posted in Hardware
      Crille
      Crille
    • RE: Rule to detect failed devices on an Ezlo hub?

      @cw-kid The indentation of the groups controller was off in my post. I've corrected it. Please try again with correct indentation and your Reactor should start.
      The groups controller is in the right place in your config and include_controller should be the id of the Ezlo Plus controller.

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: [Solved] Issue with Tasmota sensors and MQTTController later than 22024

      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!

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: [Solved] Issue with Tasmota sensors and MQTTController later than 22024

      This is from openLuup retained messages:

      retained2.PNG

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: [Solved] Issue with Tasmota sensors and MQTTController later than 22024

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

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: [Solved] Issue with Tasmota sensors and MQTTController later than 22024

      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.

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: [Solved] Issue with Tasmota sensors and MQTTController later than 22024

      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
      
      posted in Multi-System Reactor
      Crille
      Crille
    • RE: [Solved] Issue with Tasmota sensors and MQTTController later than 22024

      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

      posted in Multi-System Reactor
      Crille
      Crille
    • RE: [Solved] Issue with Tasmota sensors and MQTTController later than 22024

      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!

      posted in Multi-System Reactor
      Crille
      Crille