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. NUTControlle with influxDB
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

NUTControlle with influxDB

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 2 Posters 353 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.
  • wmarcolinW Offline
    wmarcolinW Offline
    wmarcolin
    wrote on last edited by wmarcolin
    #1

    Hi Patrick,

    I have been using the integration of my UPS with MSR (NUTController-22283) for some months now, and it works very well.

    I would like to evolve a little bit the usage, and I have, at the moment a difficulty, to take the data to influxDB.

    I have also integrated influxDB 1.8 successfully with the MSR, I export the capabilities that I want to use, but the NUT data I have not succeeded, I made several attempts, and I can not send the data, below the configuration that I would like if possible.

            x_nut_ups:
              attributes:
                input_voltage:
                  include: true
                  type: number
                output_voltage:
                  include: true
                  type: number
                battery_charge:
                  include: true
                  type: number
    

    And I don't succeed, consulting influxDB doesn't show the information:

    > show measurements
    name: measurements
    name
    ----
    battery_power
    binary_sensor
    humidity_sensor
    motion_sensor
    temperature_sensor
    x_hubitat_extra_attributes
    

    Could you please give me some guidance on what I am doing wrong?

    I also want to comment if it should appear in the Controller Status widget panel when influxDB is activated.

    Thanks.

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

      There's not enough context in your example for me to definitively help you, but I can see that in all likelihood, your configuration for InfluxDB isn't as described in the documentation and required for InfluxDB to understand your intent.

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

      wmarcolinW 2 Replies Last reply
      0
      • toggledbitsT toggledbits

        There's not enough context in your example for me to definitively help you, but I can see that in all likelihood, your configuration for InfluxDB isn't as described in the documentation and required for InfluxDB to understand your intent.

        wmarcolinW Offline
        wmarcolinW Offline
        wmarcolin
        wrote on last edited by
        #3

        @toggledbits

        Ok, let me put the complete configuration.

        plugins:
          - id: influx
            implementation: InfluxFeed
            enabled: true
            name: InfluxDB Feed 1.8
            config:
              influx_url: http://192.168.50.8:8086
              influx_database: Reactor
              influx_username:
              influx_password:
              select_capabilities:
                power_switch: false
                dimming: false
                binary_sensor: true
                motion_sensor: true
                leak_detector: false
                temperature_sensor: true
                humidity_sensor: true
                light_sensor: true
                battery_power: true
                x_hubitat_extra_attributes: true
                x_nut_ups:
                  attributes:
                    input_voltage:
                      include: true
                      type: number
                    output_voltage:
                      include: true
                      type: number
                    battery_charge:
                      include: true
                      type: number
        

        As I mentioned before, the MSR is connecting without any errors with influxDB.

        root@main:/home/wilson/reactor/config# influx -precision rfc3339
        Connected to http://localhost:8086 version 1.8.10
        InfluxDB shell version: 1.8.10
        > use Reactor
        Using database Reactor
        > show measurements
        name: measurements
        name
        ----
        battery_power
        binary_sensor
        humidity_sensor
        light_sensor
        motion_sensor
        temperature_sensor
        x_hubitat_extra_attributes
        x_nut_ups
        >
        
        > select * from x_nut_ups
        name: x_nut_ups
        time                     battery_charge controller entity        input_voltage name      output_voltage
        ----                     -------------- ---------- ------        ------------- ----      --------------
        2022-10-13T00:04:17.939Z 100            nut        nut>TrippLite 122.3         TrippLite 122.9
        2022-10-13T00:04:47.984Z 100            nut        nut>TrippLite 122.3         TrippLite 122.9
        2022-10-13T00:05:38.176Z 100            nut        nut>TrippLite 121.4         TrippLite 122.9
        2022-10-13T00:05:38.177Z 100            nut        nut>TrippLite 121.4         TrippLite 122.9
        2022-10-13T00:06:18.263Z 100            nut        nut>TrippLite 122.3         TrippLite 122.9
        >
        
        

        Well, just because I was complaining to the Creator, now it worked without a problem.

        Well, sorry, case closed, but I can assure you that I did several tests. Now an important detail, today I updated the drive from version 22152 to 22283, and I think I had not tested yet with this update.

        1 Reply Last reply
        0
        • toggledbitsT toggledbits

          There's not enough context in your example for me to definitively help you, but I can see that in all likelihood, your configuration for InfluxDB isn't as described in the documentation and required for InfluxDB to understand your intent.

          wmarcolinW Offline
          wmarcolinW Offline
          wmarcolin
          wrote on last edited by
          #4

          @toggledbits

          @toggledbits

          Sorry, for an additional query, is it possible to stipulate a condition for saving the data to the database, either by time interval or by changing the attribute's content?

          And sorry if I did not make clear the suggestion that the Controller Status could not appear as the status of activated influxDB.

          8dac2051-5680-4c00-9c61-35fa6f89b8d5-image.png

          Thanks!

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

            The InfluxFeed plugin is not a Controller, so it won't appear on the Controller Status widget.

            It is possible to modify the value being sent to influxdb by adding an expr: key followed by a quoted string containing an expression (shown in the docs). The result of the expression is what will be logged. The current value is available in expression context as the value variable, so expr: "value * value" would send the measurement value as the square of the entity attribute value. However, I personally don't recommend using it. Having a long history with data logging and databases, it has become my preference to always put raw data into the database, as you got it from whatever source, and then use database queries to modify the data. influxdb is capable of doing any kind of transformation in the query from the raw data, and can also build a time series using a specified interval, interpolating as needed (you're probably already doing this by using the mean() function in your queries for graphs, which is an influxdb/grafana default). Also, the expression cannot be used to suppress a value (i.e. prevent it from being sent to influxdb).

            It is not possible to change the InfluxFeed time interval for sending data on the Reactor side, because there isn't one. InfluxFeed sends data whenever the entity is modified. It does not send data at regular timed intervals, and it's not possible to define an interval for sending data. Again, influxdb itself has mechanisms for dealing with this.

            Also, I note in your config that you are logging the entire x_hubitat_extra_attributes capability. This has the potential to send huge amounts of data, and I recommend you use the extended syntax to only log the specific attributes you want.

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

            wmarcolinW 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              The InfluxFeed plugin is not a Controller, so it won't appear on the Controller Status widget.

              It is possible to modify the value being sent to influxdb by adding an expr: key followed by a quoted string containing an expression (shown in the docs). The result of the expression is what will be logged. The current value is available in expression context as the value variable, so expr: "value * value" would send the measurement value as the square of the entity attribute value. However, I personally don't recommend using it. Having a long history with data logging and databases, it has become my preference to always put raw data into the database, as you got it from whatever source, and then use database queries to modify the data. influxdb is capable of doing any kind of transformation in the query from the raw data, and can also build a time series using a specified interval, interpolating as needed (you're probably already doing this by using the mean() function in your queries for graphs, which is an influxdb/grafana default). Also, the expression cannot be used to suppress a value (i.e. prevent it from being sent to influxdb).

              It is not possible to change the InfluxFeed time interval for sending data on the Reactor side, because there isn't one. InfluxFeed sends data whenever the entity is modified. It does not send data at regular timed intervals, and it's not possible to define an interval for sending data. Again, influxdb itself has mechanisms for dealing with this.

              Also, I note in your config that you are logging the entire x_hubitat_extra_attributes capability. This has the potential to send huge amounts of data, and I recommend you use the extended syntax to only log the specific attributes you want.

              wmarcolinW Offline
              wmarcolinW Offline
              wmarcolin
              wrote on last edited by
              #6

              @toggledbits

              Thanks boss for the master class!! I will change x_hubitat_extra_attributes, you are right, many information I will not use.

              Thanks.

              1 Reply Last reply
              1
              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
                26

              • Error After Upgrade
                G
                gwp1
                0
                4
                35

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

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

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

              • Links to MSR from HA
                Tom_DT
                Tom_D
                0
                1
                58

              • Set Reaction > Script Action
                wmarcolinW
                wmarcolin
                0
                11
                347

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

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

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

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

              • 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