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?
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor
Cloning actions in reactions does not work
tunnusT
With build 26140 (on Docker) I'm not able to clone any actions in reactions. Using Chrome if it has any relevance.
Multi-System Reactor
Has ping command been removed?
tunnusT
Topic thumbnail image
Multi-System Reactor
ReferenceError with Home Assistant data & build 26140
tunnusT
Topic thumbnail image
Multi-System Reactor

Should MSR import this device type from an Ezlo controller?

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 5 Posters 1.4k 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.5.1.142
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HAOS
          Core 2026.7.4
          w/ HA Connect ZWA-2
          FW: v1.1
          SDK: v7.23.1

          *Prod MSR in docker/portainer
          MSR: latest-26193-8dd8f854
          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

                • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                  toggledbitsT
                  toggledbits
                  0
                  10
                  51

                • [SOLVED] Question regarding "in" vs "contains" vs contents of the string
                  G
                  gwp1
                  0
                  5
                  21

                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  147
                  127.0k

                • Upgrade Issues
                  toggledbitsT
                  toggledbits
                  0
                  8
                  84

                • openLuup console disappeared - 500 - Internal Server Error
                  A
                  a-lurker
                  0
                  2
                  144

                • Logon screen timeout
                  G
                  gwp1
                  0
                  5
                  171

                • [MSR] Copy&past of actions and/or drag&drop between set/reset
                  toggledbitsT
                  toggledbits
                  0
                  9
                  317

                • Upgrade advice - upgrade from aarch64 to ARM64 image
                  toggledbitsT
                  toggledbits
                  0
                  4
                  185

                • Alexa for MSR, any interest?
                  CatmanV2C
                  CatmanV2
                  2
                  4
                  317

                • Ezlo Paid Subscription for Vera Cloud Services
                  therealdbT
                  therealdb
                  4
                  2
                  445

                • [RESOLVED] Telegram notification broke with latest update
                  CatmanV2C
                  CatmanV2
                  0
                  11
                  775
                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