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. Native support for Philips Hue
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
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
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

Native support for Philips Hue

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 4 Posters 298 Views 4 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
    #1

    Any plans to add native support for the Philips Hue Bridge / API to control Hue lights / Zigbee 3.0 devices.

    I'm currently using the Alt Hue plugin on Vera but that might not be the case forever.

    And I know it's EOL but support for the Harmony hubs would be handy also. Starting / stopping Harmony actives and being able to send commands to IR devices like with Renee's Harmony plugin for Vera and the http API it creates.

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

      This jibes with my response to your recent reply on the Vera/eZLO forums. I'm not a Hue or Harmony user, but there is nothing to prevent someone who is from writing and supporting the interface for MSR. It's probably not appropriate for me to do it, because I'm not a user of these devices, so I would not only face the expense of sourcing the hub and what could be a significant mix of common devices, but also the learning curve that others have already overcome. Someone who is an enthusiastic user of these devices that also has the necessary programming skill is probably already out there, and is really the right choice, and that model pervades all of the platforms we work on (the plugins on Vera, the components in Hass, the device drivers and apps in Hubitat).

      Also remember that a big reason MSR exists is to give you the flexibility to choose the best platform for the device you want to use. If the Vera support is a little clumsy or thin for a device, it may be that Hass or Hubitat is better (all my Zigbee stuff is on Hubitat at the moment, for example). Sure, it would be ideal to have a direct interface, and that's definitely part of the plan, but the shortcut for today may simply be to move your Hue or Harmony support to Hass or Hubitat and let MSR access it there.

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

      cw-kidC therealdbT 2 Replies Last reply
      0
      • wmarcolinW Offline
        wmarcolinW Offline
        wmarcolin
        wrote on last edited by
        #3

        As I commented on the other forum, and after having already bought several lights and none worked with Vera due to Zigbee incompatibility, I followed what @cw-kid recommended, and bought the Hue hub, to finally have lights that can be controlled. As soon as it arrives I will install it, and then use the Vera plugin, but I am one step away from buying a Hubitat, because the recurrent problems of Zigbee having many devices available and nothing talking to Vera, and recently every new z-wave device that has the S2 security protocol is a huge headache to work with Vera, I am thinking of really going for a new hub. And of course, I will not make the mistake of being an ezlo.

        1 Reply Last reply
        0
        • toggledbitsT toggledbits

          This jibes with my response to your recent reply on the Vera/eZLO forums. I'm not a Hue or Harmony user, but there is nothing to prevent someone who is from writing and supporting the interface for MSR. It's probably not appropriate for me to do it, because I'm not a user of these devices, so I would not only face the expense of sourcing the hub and what could be a significant mix of common devices, but also the learning curve that others have already overcome. Someone who is an enthusiastic user of these devices that also has the necessary programming skill is probably already out there, and is really the right choice, and that model pervades all of the platforms we work on (the plugins on Vera, the components in Hass, the device drivers and apps in Hubitat).

          Also remember that a big reason MSR exists is to give you the flexibility to choose the best platform for the device you want to use. If the Vera support is a little clumsy or thin for a device, it may be that Hass or Hubitat is better (all my Zigbee stuff is on Hubitat at the moment, for example). Sure, it would be ideal to have a direct interface, and that's definitely part of the plan, but the shortcut for today may simply be to move your Hue or Harmony support to Hass or Hubitat and let MSR access it there.

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

          @toggledbits

          If a user could give you remote access to a device such as the Hue hub, might that be of interest to you, to program against?

          1 Reply Last reply
          0
          • toggledbitsT toggledbits

            This jibes with my response to your recent reply on the Vera/eZLO forums. I'm not a Hue or Harmony user, but there is nothing to prevent someone who is from writing and supporting the interface for MSR. It's probably not appropriate for me to do it, because I'm not a user of these devices, so I would not only face the expense of sourcing the hub and what could be a significant mix of common devices, but also the learning curve that others have already overcome. Someone who is an enthusiastic user of these devices that also has the necessary programming skill is probably already out there, and is really the right choice, and that model pervades all of the platforms we work on (the plugins on Vera, the components in Hass, the device drivers and apps in Hubitat).

            Also remember that a big reason MSR exists is to give you the flexibility to choose the best platform for the device you want to use. If the Vera support is a little clumsy or thin for a device, it may be that Hass or Hubitat is better (all my Zigbee stuff is on Hubitat at the moment, for example). Sure, it would be ideal to have a direct interface, and that's definitely part of the plan, but the shortcut for today may simply be to move your Hue or Harmony support to Hass or Hubitat and let MSR access it there.

            therealdbT Offline
            therealdbT Offline
            therealdb
            wrote on last edited by
            #5

            @toggledbits as I’ve already said, I think mqtt could be a better investment than ezlo hubs support (used by 100 people). There are plenty of libraries doing something-to-mqtt, so this could let people add more things very easily.

            --
            On a mission to automate everything.

            My MS Reactor contrib
            My Luup Plug-ins

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

              MQTT work is already under way, as is ZWaveJS. Since those are "drop-in" features, they are not version-dependent, so I don't have any urgency around getting them done in time for the 1.0 release, but MQTT will probably make an appearance in preview form (at least) in late Summer or early Autumn.

              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
              3
              • toggledbitsT toggledbits locked this topic on
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              Recent Topics

              • Gradually turn on lights.
                G
                gwp1
                0
                4
                132

              • Stop the MSR by an external switch on Hubitat.
                wmarcolinW
                wmarcolin
                0
                1
                31

              • Error After Upgrade
                G
                gwp1
                0
                4
                103

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

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

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

              • Links to MSR from HA
                Tom_DT
                Tom_D
                0
                1
                90

              • Set Reaction > Script Action
                wmarcolinW
                wmarcolin
                0
                11
                433

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

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

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

              • Advice reqeusted to migrate MSR from Bare Metal to Container
                T
                tamorgen
                0
                5
                260
              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