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
Condition for trend
T
Topic thumbnail image
Multi-System Reactor
Set reaction triggering wrong z-wave device
T
Topic thumbnail image
Multi-System Reactor
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
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
[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
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor

Need advice building templates for MQTTController

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 3 Posters 1.3k 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

                    • Condition for trend
                      T
                      tamorgen
                      0
                      4
                      10

                    • Set reaction triggering wrong z-wave device
                      T
                      tamorgen
                      0
                      19
                      213

                    • Can you run MSR on Home Assistant OS ?
                      CatmanV2C
                      CatmanV2
                      0
                      12
                      219

                    • RPi Alternative: Orange Pi 4 LTS (3GB RAM/16GB eMMC)
                      toggledbitsT
                      toggledbits
                      0
                      2
                      1.7k

                    • RPi Alternative: Orange Pi Zero 2 (1GB)
                      toggledbitsT
                      toggledbits
                      2
                      3
                      3.5k

                    • RPi Alternative: Libre Computer AML-S905X-CC "Le Potato" (2GB RAM)
                      toggledbitsT
                      toggledbits
                      5
                      6
                      3.1k

                    • HA and AI
                      therealdbT
                      therealdb
                      0
                      4
                      154

                    • How to upgrade from an old version of MSR?
                      CatmanV2C
                      CatmanV2
                      0
                      26
                      480

                    • This trigger no longer working - complaining about the operator needing changing
                      toggledbitsT
                      toggledbits
                      0
                      18
                      238

                    • Self test
                      CatmanV2C
                      CatmanV2
                      0
                      3
                      123

                    • Access control - allowing anonymous user to dashboard
                      toggledbitsT
                      toggledbits
                      0
                      2
                      135

                    • VEC Virtual Switch Auto Off
                      S
                      SweetGenius
                      1
                      1
                      95
                    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