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?
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
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor

Should MSR import this device type from an Ezlo controller?

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

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

          *Prod MSR in docker/portainer
          MSR: latest-26011-c621bbc7
          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

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

                • VEC Virtual Switch Auto Off
                  S
                  SweetGenius
                  1
                  1
                  34

                • Upcoming Storage Change -- Got Back-ups?
                  toggledbitsT
                  toggledbits
                  2
                  1
                  30

                • Oddness in Copy/Move of Reactions
                  G
                  gwp1
                  0
                  1
                  63

                • [Solved] function isRuleEnabled() issue
                  CrilleC
                  Crille
                  0
                  4
                  92

                • [Reactor] Problem with Global Reactions and groups
                  therealdbT
                  therealdb
                  0
                  3
                  106

                • Possible feature request 2?
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  78

                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  133
                  80.1k

                • Genuinely impressed with Zigbee and HA / Reactor
                  CatmanV2C
                  CatmanV2
                  1
                  9
                  392

                • Copying a global reaction
                  toggledbitsT
                  toggledbits
                  0
                  3
                  117

                • [HowTo] Using HABridge with Reactor
                  CatmanV2C
                  CatmanV2
                  0
                  9
                  453

                • [Reactor] Bug when sending MQTT boolean payloads
                  toggledbitsT
                  toggledbits
                  0
                  4
                  173
                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