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. Trying to setup InfluxDB breaks my MSR install
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
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
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[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
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

Trying to setup InfluxDB breaks my MSR install

Scheduled Pinned Locked Moved Multi-System Reactor
15 Posts 2 Posters 2.4k 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 on last edited by cw-kid
    #1

    Hi

    I've just done a clean install of Bullseye OS on my Raspberry Pi and I am trying to setup MSR with InfluxDB.

    I have managed to get the old VeraFlux plugin working OK with the new InfluxDB installation on the Pi, so think I have the InfluxDB installation correct and working.

    However ideally I'd like to use MSR instead. I created a "reactor" database and created a username and password.

    In the reactor config file I added this at the end of it

    plugins:
    - id: influx
      name: InfluxDB 1.x Feed
      enabled: true
      implementation: InfluxFeed
       config:
        influx_url: http://192.168.0.36:8086
        influx_database: reactor
        influx_username: myuser
        influx_password: "mypassword"  # note use of quotes
    

    However when I restart MSR it doesn't come back up again. If I comment out all of that plugins section in the config file and restart the box, then MSR loads OK again. So I must be doing something wrong?

    Influx running on the Pi is version 1.8.10.

    MSR is running on a different Linux Debian box.

    Not sure how to update to InfluxDB 2.0, maybe I should do that?

    I looked in the log file and searched for "Influx" but nothing was found.

    Thanks

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

      Check that you don't have tabs instead of spaces in your indenting. You can check /var/log/syslog for additional startup errors.

      Also did you run the install script?

      Edit: just noticed that config and all below are not correctly indented.

      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 on last edited by
        #3

        Thanks, I think I fixed the indents now but its still the same MSR web page doesn't load. I will have a look in the syslog then.

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

          @toggledbits

          Did I run the install script? No I haven't.

          Is it a separate install now for the InfluxDB plugin? And how do you do it?

          The help page just says

          "At the moment, InfluxFeed is included in all Reactor distributions. In a future release, it will be a separately-installed component"

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

            MSR is starting now, I think my reactor.yaml config file was a bit out of date. I just copied the whole plugins section from the dist-config reactor.yaml file version and pasted it in to mine and then edited it. Now MSR is starting up again OK.

            I've just connected Grafana to the "reactor" DB source on InfluxDB OK. But as yet no measurements are appearing yet for some reason. I'm not sure if MSR is actually outputting data or how to check it, other than trying to do a query in Grafana.

            a598cfa5-3e40-4267-a9ab-dba57faadae2-image.png

            Only thing I wasn't sure about was this:

            influx_org - Organization ID (required)
            influx_org: "<your-influx-organization>"

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

              Maybe the plugin isn't actually installed then. I see this in the MSR log:

              [latest-22004]2022-01-19T17:07:24.636Z <app:ERR> Trapped unhandled Promise rejection: [Error]Error: Cannot find module '@influxdata/influxdb-client'
              Require stack:
              - /home/stuart/reactor/server/lib/InfluxFeed.js
              [latest-22004]2022-01-19T17:07:24.637Z <app:ERR> Please refer to the console log for trace
              [latest-22004]2022-01-19T17:07:24.762Z <app:ERR> Trapped unhandled Promise rejection: [Error]Error: Cannot find module '@influxdata/influxdb-client'
              Require stack:
              - /home/stuart/reactor/server/lib/InfluxFeed.js
              [latest-22004]2022-01-19T17:07:24.762Z <app:ERR> Please refer to the console log for trace
              [latest-22004]2022-01-19T17:07:24.818Z <app:ERR> Trapped unhandled Promise rejection: [Error]Error: Cannot find module '@influxdata/influxdb-client'
              Require stack:
              - /home/stuart/reactor/server/lib/InfluxFeed.js
              [latest-22004]2022-01-19T17:07:24.818Z <app:ERR> Please refer to the console log for trace
              [latest-22004]2022-01-19T17:07:24.865Z <app:ERR> Trapped unhandled Promise rejection: [Error]Error: Cannot find module '@influxdata/influxdb-client'
              Require stack:
              - /home/stuart/reactor/server/lib/InfluxFeed.js
              [latest-22004]2022-01-19T17:07:24.867Z <app:ERR> Please refer to the console log for trace
              
              
              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by toggledbits
                #7

                I meant the Reactor install script for RPi. Missing packages are usually a failure to complete the install. See the docs.

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

                cw-kidC 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  I meant the Reactor install script for RPi. Missing packages are usually a failure to complete the install. See the docs.

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

                  @toggledbits said in Trying to setup InfluxDB breaks my MSR install:

                  I meant the Reactor install script for RPi

                  MSR isn't running on the Pi. Its running on a bare metal Linux Debian box, version is 22004-6d6c6b7.

                  InfluxDB is running on a Pi however.

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

                    OK, but the point is the same. The error message suggests that the install steps on the Debian side weren't done, and one step in particular, step 6. The dependencies for Reactor haven't been installed, or may be very out of date (there have been several releases where I've recommended running npm to update them).

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

                    cw-kidC 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      OK, but the point is the same. The error message suggests that the install steps on the Debian side weren't done, and one step in particular, step 6. The dependencies for Reactor haven't been installed, or may be very out of date (there have been several releases where I've recommended running npm to update them).

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

                      @toggledbits

                      Thank you, that was the bit I wasn't sure how to do.

                      It seems to be working now and populating stuff in Grafana from the "Reactor" DB.

                      731f08c8-626c-4993-81a4-38ad15e1b2d7-image.png

                      Is that all the device capabilities available in that screen shot? For example could we add a Light Level Sensor (LUX) in to a graph ? I tired binary_sensor but could not see any LUX sensors under "name" or under "entity" and looking for the Vera device ID number I wanted.

                      I able to do that using the old VeraFlux plugin earlier. But I want to ditch that plugin now and just use MSR ideally.

                      3ece62a6-0a7f-47e6-b311-550ee4ba3150-image.png

                      Thank you.

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

                        @toggledbits

                        Thank you, that was the bit I wasn't sure how to do.

                        It seems to be working now and populating stuff in Grafana from the "Reactor" DB.

                        731f08c8-626c-4993-81a4-38ad15e1b2d7-image.png

                        Is that all the device capabilities available in that screen shot? For example could we add a Light Level Sensor (LUX) in to a graph ? I tired binary_sensor but could not see any LUX sensors under "name" or under "entity" and looking for the Vera device ID number I wanted.

                        I able to do that using the old VeraFlux plugin earlier. But I want to ditch that plugin now and just use MSR ideally.

                        3ece62a6-0a7f-47e6-b311-550ee4ba3150-image.png

                        Thank you.

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

                        @cw-kid said in Trying to setup InfluxDB breaks my MSR install:

                        Is that all the device capabilities available in that screen shot? For example could we add a Light Level Sensor (LUX) in to a graph ?

                        The docs describe how to select capabilities for export. The section after also describes how to restrict which entities are exported, if that's an additional thing you may want to do.

                        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 on last edited by
                          #12

                          OK sorry I will read the help doc again. I just assumed it would export everything to the database out of the box.

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

                            No worries. I just don't want to rehash, and if the docs end up not being adequate, I want to know that, too. The abbreviated default list of capabilities is to avoid the "sipping from a firehose" effect... as I think you've seen on the Recently Changed Entities list on the Status page, device changes are many and frequent, especially from Vera hubs (much of it caused by polling and the resultant updating of polling state/control variables that most people don't care about).

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

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

                              OK that works these values are coming from MSR now via Vera Plus hub

                              9a25e296-f402-49c6-bb4c-dbb9ae272e01-image.png

                              I added this in to the reactor.yaml file

                              config:
                                    select_capabilities:
                                      light_sensor: true
                              

                              I will have a play about with it all, as I have forgotten how to use Grafana properly and its changed a bit since last time I used it.

                              1 Reply Last reply
                              1
                              • toggledbitsT Offline
                                toggledbitsT Offline
                                toggledbits
                                wrote on last edited by toggledbits
                                #15

                                FYI only/anecdotally: I am using both 1.8 with Grafana and 2.0 with it's native graphing. Grafana is subtly prettier, for sure, but I'm not sure it outweighs the convenience of having one less piece of software to install. The only thing I haven't verified for 2.0's graphing is that you can do equations/functions as additional traces. I do that on my temp+humidity graphs in Grafana to compute the dew point; it didn't jump out at me how to do it in 2.0's native graphing, so I owe that a few minutes at some point, but at the moment, I'm trying to button up a ton of work to roll out in a new (MSR) release.

                                9ee26b8a-88c4-4918-9eba-f60a04129b2a-image.png

                                64755938-b468-458f-80ac-adbf793d2659-image.png

                                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

                                • [MSR] Native fan capabilty
                                  toggledbitsT
                                  toggledbits
                                  1
                                  2
                                  84

                                • [MSR] Rule do not fire
                                  therealdbT
                                  therealdb
                                  0
                                  4
                                  125

                                • Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
                                  N
                                  noelab
                                  0
                                  8
                                  202

                                • DynamicGroupController and attributes
                                  toggledbitsT
                                  toggledbits
                                  1
                                  9
                                  305

                                • Reactor (Multi-System/Multi-Hub) Announcements
                                  toggledbitsT
                                  toggledbits
                                  5
                                  149
                                  139.0k

                                • Unofficial thread for compatibility
                                  tunnusT
                                  tunnus
                                  2
                                  2
                                  743

                                • Ooops - Deleted Reactor Ex Machina II
                                  toggledbitsT
                                  toggledbits
                                  0
                                  2
                                  91

                                • Bail out of failed reaction?
                                  T
                                  tamorgen
                                  0
                                  3
                                  156

                                • Arming Envisalink panel from MSR
                                  T
                                  tamorgen
                                  0
                                  7
                                  382

                                • [Solved] DynamicGroupController updating members issue
                                  CrilleC
                                  Crille
                                  0
                                  5
                                  273

                                • Upgrade Issues
                                  T
                                  tbully
                                  0
                                  9
                                  409

                                • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                                  toggledbitsT
                                  toggledbits
                                  0
                                  10
                                  531
                                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