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. Should MSR import this device type from an Ezlo controller?
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor

Should MSR import this device type from an Ezlo controller?

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 5 Posters 493 Views 5 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 on last edited by cw-kid
    #1

    Hi

    I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

    They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

    This is how that device looks in the Ezlo API.

    Devices Info:

    _id: "10696001"
    deviceTypeId: "ezlopi"
    parentDeviceId: "10696000"
    category: "level_sensor"
    subcategory: ""
    gatewayId: "457a5069"
    batteryPowered: false
    name: "Gas Sensor Digital"
    type: "sensor"
    reachable: true
    persistent: true
    serviceNotification: false
    armed: false
    roomId: ""
    security: "no"
    ready: true
    status: "idle"
    parentRoom: true
    protectConfig: "default"
    

    Items Info:

    _id: "20696001"
    deviceId: "10696001"
    hasGetter: true
    hasSetter: false
    name: "smoke_density"
    show: true
    valueType: "substance_amount"
    scale: "parts_per_million"
    value: 2.7472610473632812
    valueFormatted: "2.75"
    status: "idle"
    

    There is also an Analog Gas sensor that one did import in to MSR OK.

    68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png

    Devices Info:

    _id: "10696000"
    deviceTypeId: "ezlopi"
    parentDeviceId: "10696000"
    category: "security_sensor"
    subcategory: "gas"
    gatewayId: "457a5069"
    batteryPowered: false
    name: "Gas Sensor Analog"
    type: "sensor"
    reachable: true
    persistent: true
    serviceNotification: false
    armed: false
    roomId: ""
    security: "no"
    ready: true
    status: "idle"
    parentRoom: true
    protectConfig: "default"
    

    Items Info:

    _id: "20696000"
    deviceId: "10696000"
    hasGetter: true
    hasSetter: false
    name: "gas_alarm"
    show: true
    valueType: "token"
    enum:
    0: "no_gas"
    1: "combustible_gas_detected"
    2: "toxic_gas_detected"
    3: "unknown"
    valueFormatted: "no_gas"
    value: "no_gas"
    status: "idle"
    

    And this is how this MQ2 Gas Sensor looks like on their dashboard:

    Digital
    cb77dfa3-4af5-4d06-9635-89207a716a89-image.png

    Analog
    4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png

    They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

    And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

    THANKS.

    toggledbitsT 1 Reply Last reply
    0
    • therealdbT Offline
      therealdbT Offline
      therealdb
      wrote on last edited by
      #2

      While I appreciate your faith, I'm genuinely wondering why ezlopi instead of tasmota or esphome. They're both more mature and easier to find help for, so my question.

      Back in track, it's probably missing a mapping somewhere and @toggledbits needs to collect all the attributes of the device from reactor in order to support it.

      --
      On a mission to automate everything.

      My MS Reactor contrib
      My Luup Plug-ins

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

        Hi

        I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

        They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

        This is how that device looks in the Ezlo API.

        Devices Info:

        _id: "10696001"
        deviceTypeId: "ezlopi"
        parentDeviceId: "10696000"
        category: "level_sensor"
        subcategory: ""
        gatewayId: "457a5069"
        batteryPowered: false
        name: "Gas Sensor Digital"
        type: "sensor"
        reachable: true
        persistent: true
        serviceNotification: false
        armed: false
        roomId: ""
        security: "no"
        ready: true
        status: "idle"
        parentRoom: true
        protectConfig: "default"
        

        Items Info:

        _id: "20696001"
        deviceId: "10696001"
        hasGetter: true
        hasSetter: false
        name: "smoke_density"
        show: true
        valueType: "substance_amount"
        scale: "parts_per_million"
        value: 2.7472610473632812
        valueFormatted: "2.75"
        status: "idle"
        

        There is also an Analog Gas sensor that one did import in to MSR OK.

        68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png

        Devices Info:

        _id: "10696000"
        deviceTypeId: "ezlopi"
        parentDeviceId: "10696000"
        category: "security_sensor"
        subcategory: "gas"
        gatewayId: "457a5069"
        batteryPowered: false
        name: "Gas Sensor Analog"
        type: "sensor"
        reachable: true
        persistent: true
        serviceNotification: false
        armed: false
        roomId: ""
        security: "no"
        ready: true
        status: "idle"
        parentRoom: true
        protectConfig: "default"
        

        Items Info:

        _id: "20696000"
        deviceId: "10696000"
        hasGetter: true
        hasSetter: false
        name: "gas_alarm"
        show: true
        valueType: "token"
        enum:
        0: "no_gas"
        1: "combustible_gas_detected"
        2: "toxic_gas_detected"
        3: "unknown"
        valueFormatted: "no_gas"
        value: "no_gas"
        status: "idle"
        

        And this is how this MQ2 Gas Sensor looks like on their dashboard:

        Digital
        cb77dfa3-4af5-4d06-9635-89207a716a89-image.png

        Analog
        4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png

        They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

        And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

        THANKS.

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

        @cw-kid said in Should MSR import this device type from an Ezlo controller?:

        They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

        According to their own API documentation, there's a reasonable value for subcategory that should be assigned here, but it's blank. Not sure if that's an error on their part, or just garden-variety laziness, but as we say here, not my circus, not my monkeys. I'm not working around their inability to follow their own specs. Make them fix their own bug.

        @therealdb said in Should MSR import this device type from an Ezlo controller?:

        While I appreciate your faith, I'm genuinely wondering why ezlopi instead of tasmota or esphome. They're both more mature and easier to find help for, so my question.

        So right, mate. Why get bogged down and more committed to their bloated cloud-dependency when great, lightweight solutions have existed for years, with far better support?

        @cw-kid, you do realize it's been over six years since the acquisition, right? I think it's safe to say, if they haven't muscled the core product up to well beyond Vera's capabilities at this point, they're not likely to ever get there. The Pi thing is a distraction. Or worse, in my view, it's a slap in the face to people like you who have been trying to help and waiting for the core product to come of age. I salute your dedication, but I'm not sure whatever reward you're seeking at the end is forthcoming.

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

        G cw-kidC 2 Replies Last reply
        0
        • toggledbitsT toggledbits

          @cw-kid said in Should MSR import this device type from an Ezlo controller?:

          They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

          According to their own API documentation, there's a reasonable value for subcategory that should be assigned here, but it's blank. Not sure if that's an error on their part, or just garden-variety laziness, but as we say here, not my circus, not my monkeys. I'm not working around their inability to follow their own specs. Make them fix their own bug.

          @therealdb said in Should MSR import this device type from an Ezlo controller?:

          While I appreciate your faith, I'm genuinely wondering why ezlopi instead of tasmota or esphome. They're both more mature and easier to find help for, so my question.

          So right, mate. Why get bogged down and more committed to their bloated cloud-dependency when great, lightweight solutions have existed for years, with far better support?

          @cw-kid, you do realize it's been over six years since the acquisition, right? I think it's safe to say, if they haven't muscled the core product up to well beyond Vera's capabilities at this point, they're not likely to ever get there. The Pi thing is a distraction. Or worse, in my view, it's a slap in the face to people like you who have been trying to help and waiting for the core product to come of age. I salute your dedication, but I'm not sure whatever reward you're seeking at the end is forthcoming.

          G Offline
          G Offline
          gwp1
          wrote on last edited by
          #4

          @toggledbits six years? Damn. I had two years in the office pool.... how they've managed to last six is unbelievable.

          *Hubitat C-7 2.4.1.177
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.6.0
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25139-fbd67abc
          MQTTController: 25139
          ZWave Controller: 25139

          1 Reply Last reply
          1
          • CatmanV2C Offline
            CatmanV2C Offline
            CatmanV2
            wrote on last edited by
            #5

            Utterly amazing. He must be burning money!

            C

            The Ex-Vera abuser know as CatmanV2.....

            1 Reply Last reply
            0
            • toggledbitsT toggledbits

              @cw-kid said in Should MSR import this device type from an Ezlo controller?:

              They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

              According to their own API documentation, there's a reasonable value for subcategory that should be assigned here, but it's blank. Not sure if that's an error on their part, or just garden-variety laziness, but as we say here, not my circus, not my monkeys. I'm not working around their inability to follow their own specs. Make them fix their own bug.

              @therealdb said in Should MSR import this device type from an Ezlo controller?:

              While I appreciate your faith, I'm genuinely wondering why ezlopi instead of tasmota or esphome. They're both more mature and easier to find help for, so my question.

              So right, mate. Why get bogged down and more committed to their bloated cloud-dependency when great, lightweight solutions have existed for years, with far better support?

              @cw-kid, you do realize it's been over six years since the acquisition, right? I think it's safe to say, if they haven't muscled the core product up to well beyond Vera's capabilities at this point, they're not likely to ever get there. The Pi thing is a distraction. Or worse, in my view, it's a slap in the face to people like you who have been trying to help and waiting for the core product to come of age. I salute your dedication, but I'm not sure whatever reward you're seeking at the end is forthcoming.

              cw-kidC Offline
              cw-kidC Offline
              cw-kid
              wrote on last edited by
              #6

              @toggledbits said in Should MSR import this device type from an Ezlo controller?:

              value for subcategory that should be assigned

              Thanks, I didn't notice that. I will tell them to fix it.

              Cheers.

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

                As for your other comments Gentlemen, I don't disagree with them..

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


                Recent Topics

                • Gradually turn on lights.
                  toggledbitsT
                  toggledbits
                  0
                  2
                  34

                • Error After Upgrade
                  G
                  gwp1
                  0
                  4
                  42

                • Reset attribute value of entity in event handler
                  R
                  RHCPNG
                  0
                  5
                  113

                • Need help figuring out how to delay a reset on reaction
                  G
                  gwp1
                  0
                  22
                  353

                • Way to search for rules (rule state) in other rules
                  T
                  tamorgen
                  0
                  3
                  60

                • Links to MSR from HA
                  Tom_DT
                  Tom_D
                  0
                  1
                  58

                • Set Reaction > Script Action
                  wmarcolinW
                  wmarcolin
                  0
                  11
                  348

                • Wiring Samotech SM308-S into light fitting
                  akbooerA
                  akbooer
                  0
                  2
                  111

                • Errors after updating to MQTTController build 25139
                  toggledbitsT
                  toggledbits
                  0
                  6
                  205

                • 🎉 My very first MSR controller: OpenSprinkler
                  therealdbT
                  therealdb
                  5
                  13
                  825

                • Advice reqeusted to migrate MSR from Bare Metal to Container
                  T
                  tamorgen
                  0
                  5
                  212

                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  122
                  48.7k
                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