Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Need advice building templates for MQTTController
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

Need advice building templates for MQTTController

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 3 Posters 1.2k Views 3 Watching
  • 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.
  • CrilleC Offline
    CrilleC Offline
    Crille
    wrote on last edited by
    #1

    Two thoughts I'm struggling with:

    1. Regarding the lwt key "If this implementation isn't appropriate for your device, don't use the lwt key and handle the device's LWT topic and the x_mqtt_device.online attribute explicitly in your configuration."
      Could you elaborate on how I would do this?
      I've tried
    my_shelly_uni:
      capabilities: ['power_switch', 'toggle', "binary_sensor", "x_mqtt_device"]
      primary_attribute: power_switch.state
      requires: [topic, channel]
      events:
        "shellies/%topic%/relay/%channel%":
          "power_switch.state":
            expr: 'bool(payload)'
        "shellies/%topic%/adc/0":
          "binary_sensor.state":
            expr: 'int(payload) < "1"'
        "shellies/%topic%/online":
          "x_mqtt_device.online":
             expr: 'bool(payload)'
    

    for Shelly UNI which sends true/false in the online topic.

    1. Is there a way to group templates in one "brand" file in the mqtt_templates folder? For example a ìkea_tradfri.yaml that hold templates for control_outlet,light_bulb_e14,light_bulb_e27 etc.?

    Bare-metal install Reactor latest-22343, MQTTController-22340.

    toggledbitsT 1 Reply Last reply
    0
    • CrilleC Crille

      Two thoughts I'm struggling with:

      1. Regarding the lwt key "If this implementation isn't appropriate for your device, don't use the lwt key and handle the device's LWT topic and the x_mqtt_device.online attribute explicitly in your configuration."
        Could you elaborate on how I would do this?
        I've tried
      my_shelly_uni:
        capabilities: ['power_switch', 'toggle', "binary_sensor", "x_mqtt_device"]
        primary_attribute: power_switch.state
        requires: [topic, channel]
        events:
          "shellies/%topic%/relay/%channel%":
            "power_switch.state":
              expr: 'bool(payload)'
          "shellies/%topic%/adc/0":
            "binary_sensor.state":
              expr: 'int(payload) < "1"'
          "shellies/%topic%/online":
            "x_mqtt_device.online":
               expr: 'bool(payload)'
      

      for Shelly UNI which sends true/false in the online topic.

      1. Is there a way to group templates in one "brand" file in the mqtt_templates folder? For example a ìkea_tradfri.yaml that hold templates for control_outlet,light_bulb_e14,light_bulb_e27 etc.?

      Bare-metal install Reactor latest-22343, MQTTController-22340.

      toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by toggledbits
      #2

      @Crille said in Need advice building templates for MQTTController:

      I've tried

      Sigh. "I tried X"... and...? Config looks right. Not doing what you expect? What have you done to confirm that the topic is being sent by the device (e.g. visible in MQTTExplorer), and received by MQTTController (e.g. turn on topic logging for shellies/)? If it's being received by MQTTController (can be seen in the topic logs), what else is in the reactor.log file? If there's nothing standing out in the log, have you upped the log level for MQTTController to 5 to see in detail how the topic is being received and handled?

      @Crille said in Need advice building templates for MQTTController:

      Is there a way to group templates in one "brand" file in the mqtt_templates folder? For example a ìkea_tradfri.yaml that hold templates for control_outlet,light_bulb_e14,light_bulb_e27 etc.?

      Any file in mqtt_templates can have multiple templates defined in it. It simply uses the templates: top-level key and has the template IDs and specifications indented below that. The templates can also be packaged in a ZIP file for easy distribution as a set, if there are multiple files.

      But... your template names must include some kind of namespace identifier. Don't name your template control_output or light_bulb_e14, but rather (for example) tradfri_control_output and tradfri_light_bulb_e14 to prevent collisions with other (perhaps future) templates in the community.

      Documentation: https://reactor.toggledbits.com/docs/MQTTController/#publishing-templates-for-the-community

      @Crille said in Need advice building templates for MQTTController:

      expr: 'int(payload) < "1"'
      

      Comparing numbers to strings is at least bad style, and definitely a bad habit that will bite you some day.

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

      CrilleC 1 Reply Last reply
      0
      • therealdbT Offline
        therealdbT Offline
        therealdb
        wrote on last edited by
        #3

        @crille I have a wip for templates for Shelly uni, i3 and i4, among others. Great to hear you’re working on a template for the uni.

        --
        On a mission to automate everything.

        My MS Reactor contrib
        My Luup Plug-ins

        CrilleC 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @Crille said in Need advice building templates for MQTTController:

          I've tried

          Sigh. "I tried X"... and...? Config looks right. Not doing what you expect? What have you done to confirm that the topic is being sent by the device (e.g. visible in MQTTExplorer), and received by MQTTController (e.g. turn on topic logging for shellies/)? If it's being received by MQTTController (can be seen in the topic logs), what else is in the reactor.log file? If there's nothing standing out in the log, have you upped the log level for MQTTController to 5 to see in detail how the topic is being received and handled?

          @Crille said in Need advice building templates for MQTTController:

          Is there a way to group templates in one "brand" file in the mqtt_templates folder? For example a ìkea_tradfri.yaml that hold templates for control_outlet,light_bulb_e14,light_bulb_e27 etc.?

          Any file in mqtt_templates can have multiple templates defined in it. It simply uses the templates: top-level key and has the template IDs and specifications indented below that. The templates can also be packaged in a ZIP file for easy distribution as a set, if there are multiple files.

          But... your template names must include some kind of namespace identifier. Don't name your template control_output or light_bulb_e14, but rather (for example) tradfri_control_output and tradfri_light_bulb_e14 to prevent collisions with other (perhaps future) templates in the community.

          Documentation: https://reactor.toggledbits.com/docs/MQTTController/#publishing-templates-for-the-community

          @Crille said in Need advice building templates for MQTTController:

          expr: 'int(payload) < "1"'
          

          Comparing numbers to strings is at least bad style, and definitely a bad habit that will bite you some day.

          CrilleC Offline
          CrilleC Offline
          Crille
          wrote on last edited by
          #4

          @toggledbits said in Need advice building templates for MQTTController:

          Config looks right

          Thank you, wasn't sure about that.

          Sorry for posting in a hurry, here's the rest of "show your work":

          This is the entity in reactor config:

          entities:
            "poolvarmepump":
              name: "Poolvärmepump"
              topic: "shellyuni-C45BBE6C6DE8"
              channel: "1"
              uses_template: my_shelly_uni
          

          The actual device is disconnected from power so I used MQTT Explorer to manually publish in that topic

          explorer.PNG

          This is logged in the topic log

          2022-12-16T18:57:49.593Z "shellies/shellyuni-C45BBE6C6DE8/online" 0 false false
          

          This is log level 5

          [latest-22343]2022-12-16T19:09:47.346Z <MQTTController:5:MQTTController.js:834> MQTTController#mosquitto-mqtt handling shellies/shellyuni-C45BBE6C6DE8/online for poolvarmepump: false
          [latest-22343]2022-12-16T19:09:47.346Z <MQTTController:5:MQTTController.js:934> MQTTController#mosquitto-mqtt setting Entity#mosquitto-mqtt>poolvarmepump x_mqtt_device.online=false
          
          

          This is log level 7

          [latest-22343]2022-12-16T18:11:20.082Z <MQTTController:6:MQTTController.js:389> MQTTController#mqtt message packet=[Object]{ "cmd": "publish", "retain": false, "qos": 0, "dup": false, "length": 47, "topic": "smartreader/sensor/voltage_phase_3/state", "payload": 232.7 }
          [latest-22343]2022-12-16T18:11:20.098Z <MQTTController:6:MQTTController.js:389> MQTTController#mqtt message packet=[Object]{ "cmd": "publish", "retain": false, "qos": 0, "dup": false, "length": 45, "topic": "smartreader/sensor/current_phase_1/state", "payload": 6.8 }
          [latest-22343]2022-12-16T18:11:20.103Z <MQTTController:6:MQTTController.js:389> MQTTController#mqtt message packet=[Object]{ "cmd": "publish", "retain": false, "qos": 0, "dup": false, "length": 45, "topic": "smartreader/sensor/current_phase_2/state", "payload": 0.9 }
          [latest-22343]2022-12-16T18:11:20.109Z <MQTTController:6:MQTTController.js:389> MQTTController#mqtt message packet=[Object]{ "cmd": "publish", "retain": false, "qos": 0, "dup": false, "length": 45, "topic": "smartreader/sensor/current_phase_3/state", "payload": 4.0 }
          [latest-22343]2022-12-16T18:11:23.377Z <MQTTController:6:MQTTController.js:389> MQTTController#mosquitto-mqtt message packet=[Object]{ "cmd": "publish", "retain": false, "qos": 0, "dup": false, "length": 45, "topic": "shellies/shellyuni-C45BBE6C6DE8/online", "payload": false }
          [latest-22343]2022-12-16T18:11:23.377Z <MQTTController:6:MQTTController.js:422> MQTTController#mosquitto-mqtt dispatching shellies/shellyuni-C45BBE6C6DE8/online to poolvarmepump
          [latest-22343]2022-12-16T18:11:23.377Z <MQTTController:5:MQTTController.js:834> MQTTController#mosquitto-mqtt handling shellies/shellyuni-C45BBE6C6DE8/online for poolvarmepump: false
          [latest-22343]2022-12-16T18:11:23.377Z <MQTTController:6:MQTTController.js:854> MQTTController#mosquitto-mqtt template in context is [Object]{ "capabilities": [ "power_switch", "toggle", "binary_sensor", "x_mqtt_device" ], "primary_attribute": "power_switch.state", "requires": [ "topic" ], "events": { "shellies/%topic%/relay/%channel%": { "power_switch.state": { "expr": "bool(payload)", "attribute": "power_switch.state" } }, "shellies/%topic%/adc/0": { "binary_sensor.state": { "expr": "int(payload) < \"1\"", "attribute": "binary_sensor.state" } }, "shellies/%topic%/online": { "x_mqtt_device.online": { "expr": "bool(payload)", "attribute": "x_mqtt_device.online" } } }, "actions": { "power_switch": { "on": { "topic": "shellies/%topic%/relay/%channel%/command", "payload": "on" }, "off": { "topic": "shellies/%topic%/relay/%channel%/command", "payload": "off" }, "set": { "topic": "shellies/%topic%/relay/%channel%/command", "payload": { "expr": "parameters.state ? 'on' : 'off'", "type": "raw" } } } }, "__source": "/home/homebridge/reactor/config/mqtt_templates/my_shelly_uni.yaml", "name": "Poolvärmepump", "topic": "shellyuni-C45BBE6C6DE8", "channel": "1", "uses_template": "my_shelly_uni", "entity": { "id": "poolvarmepump", "canonical_id": "mosquitto-mqtt>poolvarmepump", "controller": "mosquitto-mqtt", "type": "Entity", "name": "Poolvärmepump", "lastchange": 1671214268458, "lastupdate": 1671214268458, "can_delete": true, "can_rename": true, "capabilities": { "x_mqtt_device": { "attributes": { "online": { "type": "boolean" } }, "actions": { "poll": {  } } }, "power_switch": { "attributes": { "state": { "type": "bool", "values": { "true": "on", "false": "off" } } }, "actions": { "on": {  }, "off": {  }, "set": { "arguments": { "state": { "type": &#8230;, "values": &#8230; } } } } }, "toggle": { "actions": { "toggle": {  } } }, "binary_sensor": { "attributes": { "state": { "type": "bool" } } } }, "attribute_meta": { "x_mqtt_device": { "online": { "type": "boolean", "last_modified": 1671214268458, "previous_value": false, "previous_last_modified": 1671214268458 } }, "power_switch": { "state": { "type": "bool", "values": { "true": "on", "false": "off" }, "last_modified": 1667398843973, "previous_value": --null--, "previous_last_modified": 1667398843486 } }, "toggle": {  }, "binary_sensor": { "state": { "type": "bool", "last_modified": 1667398843973, "previous_value": --null--, "previous_last_modified": 1667398843486 } } }, "attributes": { "x_mqtt_device": { "online": true }, "power_switch": { "state": false }, "toggle": {  }, "binary_sensor": { "state": false } }, "actions": [ "x_mqtt_device.poll", "power_switch.on", "power_switch.off", "power_switch.set", "toggle.toggle" ], "primary_attribute": "power_switch.state", "primary_value": false }, "system": { "id": "system", "canonical_id": "mosquitto-mqtt>system", "controller": "mosquitto-mqtt", "type": "System", "name": "Mosquitto MQTT", "lastchange": 1671214263406, "lastupdate": 1671214263406, "can_delete": false, "can_rename": true, "capabilities": { "sys_system": { "attributes": { "state": { "type": "bool" } }, "actions": { "restart": {  }, "purge_dead_entities": { "arguments": { "age": { "type": &#8230;, "min": &#8230;, "default": &#8230; } } }, "delete_entity": { "arguments": { "entity_id": { "type": &#8230; } } }, "rename_entity": { "arguments": { "entity_id": { "type": &#8230;, "sort": &#8230; }, "new_name": { "type": &#8230;, "sort": &#8230; } } } } }, "x_mqtt": { "attributes": {  }, "actions": { "publish": { "arguments": { "topic": { "type": &#8230;, "sort": &#8230; }, "payload": { "type": &#8230;, "bigtext": &#8230;, "uiclass": &#8230;, "optional": &#8230;, "sort": &#8230; }, "qos": { "type": &#8230;, "values": &#8230;, "default": &#8230;, "required": &#8230;, "sort": &#8230; }, "retain": { "type": &#8230;, "default": &#8230;, "required": &#8230;, "sort": &#8230; } } } } } }, "attribute_meta": { "sys_system": { "state": { "type": "bool", "last_modified": 1671214263406, "previous_value": false, "previous_last_modified": 1671214255282 } }, "x_mqtt": {  } }, "attributes": { "sys_system": { "state": true }, "x_mqtt": {  } }, "actions": [ "sys_system.restart", "sys_system.purge_dead_entities", "sys_system.delete_entity", "sys_system.rename_entity", "x_mqtt.publish" ], "primary_attribute": "sys_system.state", "primary_value": true }, "payload_raw": "false", "packet": [object Object], "payload": "false", "value": "4.12" }
          [latest-22343]2022-12-16T18:11:23.378Z <MQTTController:6:MQTTController.js:857> MQTTController#mosquitto-mqtt events for Entity#mosquitto-mqtt>poolvarmepump: [Array][ { "expr": "bool(payload)", "attribute": "x_mqtt_device.online" } ]
          [latest-22343]2022-12-16T18:11:23.378Z <MQTTController:7:MQTTController.js:861> MQTTController#mosquitto-mqtt entity poolvarmepump attribute x_mqtt_device.online source [Object]{ "expr": "bool(payload)", "attribute": "x_mqtt_device.online" }
          [latest-22343]2022-12-16T18:11:23.378Z <MQTTController:5:MQTTController.js:934> MQTTController#mosquitto-mqtt setting Entity#mosquitto-mqtt>poolvarmepump x_mqtt_device.online=false
          [latest-22343]2022-12-16T18:11:23.460Z <MQTTController:6:MQTTController.js:389> MQTTController#mosquitto-mqtt message packet=[Object]{ "cmd": "publish", "retain": false, "qos": 0, "dup": false, "length": 42, "topic": "shellies/shellyix3-98CDAC2F5883/input/0", "payload": 1 }
          [latest-22343]2022-12-16T18:11:23.460Z <MQTTController:6:MQTTController.js:422> MQTTController#mosquitto-mqtt dispatching shellies/shellyix3-98CDAC2F5883/input/0 to ljussensor
          [latest-22343]2022-12-16T18:11:23.460Z <MQTTController:5:MQTTController.js:834> MQTTController#mosquitto-mqtt handling shellies/shellyix3-98CDAC2F5883/input/0 for ljussensor: "1"
          [latest-22343]2022-12-16T18:11:23.460Z <MQTTController:6:MQTTController.js:854> MQTTController#mosquitto-mqtt template in context is [Object]{ "capabilities": [ "binary_sensor" ], "primary_attribute": "binary_sensor.state", "events": { "shellies/%topic%/input/%channel%": { "binary_sensor.state": { "expr": "bool(payload)", "attribute": "binary_sensor.state" } } }, "name": "Skymningsrelä", "topic": "shellyix3-98CDAC2F5883", "channel": "0", "uses_template": "my_shelly_sensor", "entity": { "id": "ljussensor", "canonical_id": "mosquitto-mqtt>ljussensor", "controller": "mosquitto-mqtt", "type": "Entity", "name": "Skymningsrelä", "lastchange": 1671214263452, "lastupdate": 1671214263452, "can_delete": true, "can_rename": true, "capabilities": { "x_mqtt_device": { "attributes": { "online": { "type": "boolean" } }, "actions": { "poll": {  } } }, "binary_sensor": { "attributes": { "state": { "type": "bool" } } } }, "attribute_meta": { "x_mqtt_device": { "online": { "type": "boolean", "last_modified": 1671214263452, "previous_value": false, "previous_last_modified": 1671214263009 } }, "binary_sensor": { "state": { "type": "bool", "last_modified": 1671201570383, "previous_value": false, "previous_last_modified": 1671176239276 } } }, "attributes": { "x_mqtt_device": { "online": true }, "binary_sensor": { "state": true } }, "actions": [ "x_mqtt_device.poll" ], "primary_attribute": "binary_sensor.state", "primary_value": true }, "system": { "id": "system", "canonical_id": "mosquitto-mqtt>system", "controller": "mosquitto-mqtt", "type": "System", "name": "Mosquitto MQTT", "lastchange": 1671214263406, "lastupdate": 1671214263406, "can_delete": false, "can_rename": true, "capabilities": { "sys_system": { "attributes": { "state": { "type": "bool" } }, "actions": { "restart": {  }, "purge_dead_entities": { "arguments": { "age": { "type": &#8230;, "min": &#8230;, "default": &#8230; } } }, "delete_entity": { "arguments": { "entity_id": { "type": &#8230; } } }, "rename_entity": { "arguments": { "entity_id": { "type": &#8230;, "sort": &#8230; }, "new_name": { "type": &#8230;, "sort": &#8230; } } } } }, "x_mqtt": { "attributes": {  }, "actions": { "publish": { "arguments": { "topic": { "type": &#8230;, "sort": &#8230; }, "payload": { "type": &#8230;, "bigtext": &#8230;, "uiclass": &#8230;, "optional": &#8230;, "sort": &#8230; }, "qos": { "type": &#8230;, "values": &#8230;, "default": &#8230;, "required": &#8230;, "sort": &#8230; }, "retain": { "type": &#8230;, "default": &#8230;, "required": &#8230;, "sort": &#8230; } } } } } }, "attribute_meta": { "sys_system": { "state": { "type": "bool", "last_modified": 1671214263406, "previous_value": false, "previous_last_modified": 1671214255282 } }, "x_mqtt": {  } }, "attributes": { "sys_system": { "state": true }, "x_mqtt": {  } }, "actions": [ "sys_system.restart", "sys_system.purge_dead_entities", "sys_system.delete_entity", "sys_system.rename_entity", "x_mqtt.publish" ], "primary_attribute": "sys_system.state", "primary_value": true }, "payload_raw": "1", "packet": [object Object], "payload": "1" }
          
          

          and this is a hard refreshed view of the entity

          pool_entity.PNG

          Totally missed the docs for publishing templates, my bad!

          Thank you for spotting my mistake, I've corrected the expr for the binary_sensor.

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #5

            OK. I just posted MQTTController 22350 that has a fix to keep from overriding your custom value (it will still try, but yours will prevail).

            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
            1
            • CrilleC Offline
              CrilleC Offline
              Crille
              wrote on last edited by Crille
              #6

              Thank you, I can confirm it is now doing what I expected.

              1 Reply Last reply
              1
              • therealdbT therealdb

                @crille I have a wip for templates for Shelly uni, i3 and i4, among others. Great to hear you’re working on a template for the uni.

                CrilleC Offline
                CrilleC Offline
                Crille
                wrote on last edited by Crille
                #7

                @therealdb My use case for the Shelly uni template is not very generic so I won't publish that to the community but I'm working on some other templates for IKEA Tradfri, Tuya smart plugs and Xioami sensors that might be published later on.

                But this fix would be a great addition to your existing templates for Shelly devices.

                therealdbT 1 Reply Last reply
                1
                • CrilleC Crille

                  @therealdb My use case for the Shelly uni template is not very generic so I won't publish that to the community but I'm working on some other templates for IKEA Tradfri, Tuya smart plugs and Xioami sensors that might be published later on.

                  But this fix would be a great addition to your existing templates for Shelly devices.

                  therealdbT Offline
                  therealdbT Offline
                  therealdb
                  wrote on last edited by
                  #8

                  @Crille yeah, I'm just writing some guidance for Shelly Uni, since it's just a dual input/output device and we have template for that. I have template for Shelly Button 1 already in my test environment, and I'll write something for i3 as well, probably using a scene controller as the base (it could be already mapped today as 3 separate devices).

                  Thanks for the contribution!

                  --
                  On a mission to automate everything.

                  My MS Reactor contrib
                  My Luup Plug-ins

                  1 Reply Last reply
                  0
                  • CrilleC Offline
                    CrilleC Offline
                    Crille
                    wrote on last edited by
                    #9

                    @toggledbits A few more thoughts:

                    1. I would like to parameterize primary_attribute: and temperature_sensor.units to give the user the oppurtunity to choose between for example temperature or humidity and C or F. Before I show you all my failures, is it supposed to be doable in current release? (I'm now doing it by having the same templates in one file but with different primary_attribute: and id's)

                    2. I'd like to suggest more aliases for value_sensor for example atmospheric_pressure and signal_strength both with .units. Is that something you would consider or is there another way to accomplish two value_sensor in one entity?

                    3. Before I show you all my failures, is it possible somehow to predefine values for light_effect?

                    Thank you for your patience and let me know if you need me to provide more info if the answer isn't just yes or no 🙂

                    1 Reply Last reply
                    0
                    • toggledbitsT toggledbits locked this topic on
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    Recent Topics

                    • [Reactor] Bug when sending MQTT boolean payloads
                      toggledbitsT
                      toggledbits
                      0
                      4
                      90

                    • Genuinely impressed with Zigbee and HA / Reactor
                      therealdbT
                      therealdb
                      1
                      8
                      241

                    • Difficulty defining repeating annual period
                      G
                      gwp1
                      0
                      5
                      45

                    • Need help with sequence
                      therealdbT
                      therealdb
                      0
                      3
                      30

                    • Possible feature request?
                      therealdbT
                      therealdb
                      0
                      5
                      140

                    • Copying a global reaction
                      tunnusT
                      tunnus
                      0
                      1
                      38

                    • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                      CatmanV2C
                      CatmanV2
                      0
                      11
                      296

                    • Time series documentation
                      tunnusT
                      tunnus
                      0
                      11
                      378

                    • Tuya Wifi to Tasmota flashing
                      CatmanV2C
                      CatmanV2
                      0
                      1
                      84

                    • MQTT templates for ZIgbee scene controller, or a better way?
                      CatmanV2C
                      CatmanV2
                      0
                      3
                      144

                    • Reset a delay
                      CatmanV2C
                      CatmanV2
                      0
                      8
                      204

                    • Zigbee2mqtt installed! sytemctl not happy :(
                      CatmanV2C
                      CatmanV2
                      0
                      4
                      175
                    Powered by NodeBB | Contributors
                    Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • Unsolved