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. Struggling to setup my first Tasmota device and MQTT
Struggling to setup my first Tasmota device and MQTT
cw-kidC
Topic thumbnail image
Multi-System Reactor
Existing Rule stopped working HTTP command fetching IP address from website
cw-kidC
Topic thumbnail image
Multi-System Reactor
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

Struggling to setup my first Tasmota device and MQTT

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 2 Posters 19 Views 2 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.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote last edited by cw-kid
    #1

    Hi

    Trying to create my first Tasmota device on an ESP board. I flashed it OK setup the GPIO pins and pointed it to an new MQTT broker running on the same Linux Debian box as MSR. I followed these instructions here to install a MQTT Controller in MSR, which I can now see under Entities. My topic on the Tasmota setup I called "fan_controller" I don't see any new device coming into MSR however.

    My ESP has an DHT22 Temp sensor attached and a Single Channel Relay to control a Fan and I also have a local touch button connected to the ESP board.

    If I run this command in terminal on the Debian box I do see some data from the ESP / Tasmota device.

     mosquitto_sub -h localhost -t "#" -v
    
    
    tele/fan_controller/LWT Online
    tasmota/discovery/7C87CE2F4CE0/config {"ip":"192.168.0.46","dn":"Tasmota","fn":["Tasmota",null,null,null,null,null,null,null],"hn":"fan-controller-3296","mac":"7C87CE2F4CE0","md":"ESP32-DevKit","ty":0,"if":0,"cam":0,"ofln":"Offline","onln":"Online","state":["OFF","ON","TOGGLE","HOLD"],"sw":"15.2.0","t":"fan_controller","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"bat":0,"dslp":0,"sho":[],"sht":[],"ver":1}
    tasmota/discovery/7C87CE2F4CE0/sensors {"sn":{"Time":"2026-02-14T17:25:50","AM2301":{"Temperature":14.2,"Humidity":56.7,"DewPoint":5.7},"TempUnit":"C"},"ver":1}
    reactor/mqtt/LWT online
    
    

    In my Reactor.yaml file I added this:

    - id: mqtt
      name: MQTT
      enabled: true
      implementation: MQTTController
      config:
        source: "mqtt://127.0.0.1:1883"
        tasmota_discovery: true
    
    

    a620c21e-3b50-46f8-b4c3-dde243b818f7-image.png

    192.168.0.4 is the MSR / MQTT Broker Debian box.

    08643248-73cf-47b2-a8ba-dc0d4d8a6873-image.png

    Probably a bad idea but I then asked A.I. what the problem might be and it was telling me I needed to change my reactor.yaml file and change implementation: MQTTController to class: MQTTController and it also told me to add these two lines at the top of the reactor.yaml file

    system:
      extension_path: /home/stuart/reactor/ext
    

    I don't know if it made that up or read it somewhere, I could not see any reference to it. Anyway MSR didn't want to load the MQTT Controller into Entities when I changed it to "class" instead of "implementation".

    In my file system it looks like this:

    70845621-9546-462c-a66f-d82ee7c63305-image.png

    I am not sure what I am missing?

    Thanks.

    EDIT: The A.I. also told me to run a command to change the IP from 127.0.0.1 to 0.0.0.0 perhaps that was a mistake.

    Here is what IP and port it seems to be listening on:

     sudo ss -tlnp | grep mosquitto
    LISTEN 0      100          0.0.0.0:1883      0.0.0.0:*    users:(("mosquitto",pid=23713,fd=5))
    
    

    Here is what the A.I. said when I asked it why we changed it from 127.0.0.1 to 0.0.0.0

    "1. The Broker (Mosquitto) at 0.0.0.0
    Think of 0.0.0.0 as "Listen to everyone."

    Because Mosquitto is set to 0.0.0.0, it is listening for messages from both the internal system (the HP Thin Client itself) and external devices (your ESP32 fan controller).

    If it were set to 127.0.0.1, it would be "deaf" to your ESP32.

    1. Reactor at 127.0.0.1
      Think of 127.0.0.1 as "Talking to myself."

    Since Multi-System Reactor and Mosquitto are both living on the same HP Thin Client, Reactor doesn't need to go out onto the Wi-Fi to find the broker. It just looks internally.

    Using 127.0.0.1 (localhost) is faster and more secure because that traffic never even leaves the computer's CPU.

    So, no, it is not a problem! Reactor talks to the broker internally (127.0.0.1), and the ESP32 talks to the broker externally (192.168.0.4). They meet in the middle inside the Mosquitto database.""

    toggledbitsT 1 Reply Last reply
    0
    • cw-kidC cw-kid

      Hi

      Trying to create my first Tasmota device on an ESP board. I flashed it OK setup the GPIO pins and pointed it to an new MQTT broker running on the same Linux Debian box as MSR. I followed these instructions here to install a MQTT Controller in MSR, which I can now see under Entities. My topic on the Tasmota setup I called "fan_controller" I don't see any new device coming into MSR however.

      My ESP has an DHT22 Temp sensor attached and a Single Channel Relay to control a Fan and I also have a local touch button connected to the ESP board.

      If I run this command in terminal on the Debian box I do see some data from the ESP / Tasmota device.

       mosquitto_sub -h localhost -t "#" -v
      
      
      tele/fan_controller/LWT Online
      tasmota/discovery/7C87CE2F4CE0/config {"ip":"192.168.0.46","dn":"Tasmota","fn":["Tasmota",null,null,null,null,null,null,null],"hn":"fan-controller-3296","mac":"7C87CE2F4CE0","md":"ESP32-DevKit","ty":0,"if":0,"cam":0,"ofln":"Offline","onln":"Online","state":["OFF","ON","TOGGLE","HOLD"],"sw":"15.2.0","t":"fan_controller","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"bat":0,"dslp":0,"sho":[],"sht":[],"ver":1}
      tasmota/discovery/7C87CE2F4CE0/sensors {"sn":{"Time":"2026-02-14T17:25:50","AM2301":{"Temperature":14.2,"Humidity":56.7,"DewPoint":5.7},"TempUnit":"C"},"ver":1}
      reactor/mqtt/LWT online
      
      

      In my Reactor.yaml file I added this:

      - id: mqtt
        name: MQTT
        enabled: true
        implementation: MQTTController
        config:
          source: "mqtt://127.0.0.1:1883"
          tasmota_discovery: true
      
      

      a620c21e-3b50-46f8-b4c3-dde243b818f7-image.png

      192.168.0.4 is the MSR / MQTT Broker Debian box.

      08643248-73cf-47b2-a8ba-dc0d4d8a6873-image.png

      Probably a bad idea but I then asked A.I. what the problem might be and it was telling me I needed to change my reactor.yaml file and change implementation: MQTTController to class: MQTTController and it also told me to add these two lines at the top of the reactor.yaml file

      system:
        extension_path: /home/stuart/reactor/ext
      

      I don't know if it made that up or read it somewhere, I could not see any reference to it. Anyway MSR didn't want to load the MQTT Controller into Entities when I changed it to "class" instead of "implementation".

      In my file system it looks like this:

      70845621-9546-462c-a66f-d82ee7c63305-image.png

      I am not sure what I am missing?

      Thanks.

      EDIT: The A.I. also told me to run a command to change the IP from 127.0.0.1 to 0.0.0.0 perhaps that was a mistake.

      Here is what IP and port it seems to be listening on:

       sudo ss -tlnp | grep mosquitto
      LISTEN 0      100          0.0.0.0:1883      0.0.0.0:*    users:(("mosquitto",pid=23713,fd=5))
      
      

      Here is what the A.I. said when I asked it why we changed it from 127.0.0.1 to 0.0.0.0

      "1. The Broker (Mosquitto) at 0.0.0.0
      Think of 0.0.0.0 as "Listen to everyone."

      Because Mosquitto is set to 0.0.0.0, it is listening for messages from both the internal system (the HP Thin Client itself) and external devices (your ESP32 fan controller).

      If it were set to 127.0.0.1, it would be "deaf" to your ESP32.

      1. Reactor at 127.0.0.1
        Think of 127.0.0.1 as "Talking to myself."

      Since Multi-System Reactor and Mosquitto are both living on the same HP Thin Client, Reactor doesn't need to go out onto the Wi-Fi to find the broker. It just looks internally.

      Using 127.0.0.1 (localhost) is faster and more secure because that traffic never even leaves the computer's CPU.

      So, no, it is not a problem! Reactor talks to the broker internally (127.0.0.1), and the ESP32 talks to the broker externally (192.168.0.4). They meet in the middle inside the Mosquitto database.""

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

      @cw-kid By the numbers:

      1. tasmota_discovery is not a thing in Reactor, so that won't work.
      2. The AI-recommended use of 0.0.0.0 for the host IP address of your MQTT broker (mosquitto) is correct and recommended.
      3. implementation: MQTTController is the correct usage (class is deprecated).
      4. You should use the 127.0.0.1 (aka loopback) address for the MQTTController's source configuration in reactor.yaml whenever the MQTT broker (i.e. mosquitto) is running on the same host as Reactor; otherwise, use the LAN interface address (192.168.0.4 in your case).
      5. system: and extension_path are also not a thing in Reactor configuration (another AI fantasy fact).
      6. All ESP32s and other MQTT clients should use the LAN address for the MQTT host (192.168.0.4 as shown in your image; that's correct).

      You need to use one of the available templates for Tasmota described in the MQTTController documentation or create a configuration of your own. The latter may be necessary for your configuration, but we need more info. Please show more of the Tasmota device configuration (screen shots), so we can help you with that.

      Until then, just choose the simple included switch/relay configuration template to get things working (i.e. so you can see that Reactor sees the device and may be able to control it).

        # In the controllers section of reactor.yaml:
        - id: mqtt
          enabled: true
          implementation: MQTTController
          name: Mosquitto
          config:
            source: mqtt://127.0.0.1:1883/
            log_topics: ['tele','stat','tasmota']  # only for testing, disable when not in use (makes big log file)
            entities:
              tasmota_fan_controller:
                name: "Tasmota Fan Controller"
                topic: fan_controller  # matches topic configured in Tasmota
                unit: 0  # relay number on the device
                include:
                  - tasmota_generic_relay
                  - tasmota_sensor_temperature_humidity
      

      This may be all you need. Try it and see what happens. Don't forget to look at the logs when things aren't working as expected. And look at the mqtt-topics.log file to see what data you are getting (post a nice snippet of it here, along with everything else requested, if the device isn't working in Reactor).

      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
      0
      • cw-kidC Offline
        cw-kidC Offline
        cw-kid
        wrote last edited by
        #3

        Knew A.I. just dreams some things up out of thin air! I have removed the stuff it suggested to add to the reactor.yaml file.

        I have this now as my MQTT Controller section:

        - id: mqtt
          enabled: true
          interface: MQTTController
          name: Mosquitto
          config:
            source: 'mqtt://127.0.0.1:1883'
            log_topics: ['tele','stat','tasmota']  # only for testing, disable when not in use (makes big log file)
            entities:
              tasmota_fan_controller:
                name: "Tasmota Fan Controller"
                topic: fan_controller  # matches topic configured in Tasmota
                unit: 0  # relay number on the device
                include: tasmota_generic_relay
                include: tasmota_sensor_temperature_humidity
        
        

        However MSR is not loading it now, it says "The Reactor configuration in "/home/stuart/reactor/config/reactor.yaml" could not be read; the system has started with an empty configuration." I guess there is something wrong with the formatting somewhere. Seems very picky if it loads the config file or not after I have edited it etc.

        I have used "interface: MQTTController" and not "implementation: MQTTController" correct ?

        @toggledbits said in Struggling to setup my first Tasmota device and MQTT:

        Please show more of the Tasmota device configuration (screen shots), so we can help you with that.

        Some more details:

        Hardware:
        ESP32-WROOM-32
        Chip Information -
        XX5R69
        Silabs CP2102
        DCL00X
        2108+

        Computer Fan is 12V with external DC power supply
        Relay (SRD-05VDC-SL-C) (Single Channel)
        TTP223B Touch Sensor
        DHT22 Temperature Humidity Sensor

        I used one of these expansion boards what the ESP32 board sits into, as it gives you more pins to connect multiple sensor etc. Like it gives you more pins for the 3.3V and 5V for example.

        Pinout:
        TTP223B Touch Sensor (Signal Wire) -> GPIO_IN:4 (Input)
        Relay (SRD-05VDC-SL-C) (Signal Wire) -> GPIO_OUT:27 (Output)
        DHT22 Temperature Humidity Sensor (Signal Wire) -> GPIO:5

        There is an "Information" button in the Tasmota device webpage that also shows a lot of device info if you want that also?

        Thanks.

        1 Reply Last reply
        0
        • cw-kidC Offline
          cw-kidC Offline
          cw-kid
          wrote last edited by
          #4

          image.png

          1 Reply Last reply
          0
          • cw-kidC Offline
            cw-kidC Offline
            cw-kid
            wrote last edited by cw-kid
            #5

            The formatting in the reator.yaml file looks OK ? I am using notepad ++

            But anytime I try to add the new MQTT Controller section and restart MSR it doesn't load the config. if I remove that new section. save and restart MSR then it does load the config as I see my other Vera controllers then in Entities.

            e3c239e3-a9b7-43bd-b1e3-4621aaf17967-image.png

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

              Sorry, my bad, change the include section to look like this (I'll fix the example above as well):

                      include: 
                        - tasmota_generic_relay
                        - tasmota_sensor_temperature_humidity
              

              Also, you can use yamllint.com to sanity-check your entire config file.

              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
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              Recent Topics

              • Struggling to setup my first Tasmota device and MQTT
                toggledbitsT
                toggledbits
                0
                6
                19

              • Existing Rule stopped working HTTP command fetching IP address from website
                toggledbitsT
                toggledbits
                0
                12
                214

              • Raspberry Pi 4 dual RAM variant introduced to mitigate RAM price increases
                toggledbitsT
                toggledbits
                0
                1
                124

              • Condition for trend
                T
                tamorgen
                0
                4
                146

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

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

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

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

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

              • HA and AI
                therealdbT
                therealdb
                0
                4
                209

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

              • This trigger no longer working - complaining about the operator needing changing
                toggledbitsT
                toggledbits
                0
                18
                488
              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