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. Is it possible for MSR to act on Nest hello (doorbell pressed)?
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

Is it possible for MSR to act on Nest hello (doorbell pressed)?

Scheduled Pinned Locked Moved Solved Multi-System Reactor
20 Posts 5 Posters 1.2k 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #11

    @Fanan After a bit more research, it may be there's something I can do on the Reactor side. I can't trial or test anything, of course, because I don't have those devices or use that integration, so I'm hoping you'll be my hands and eyes, and it may take a couple of passes to get something working that way...

    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
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #12

      OK. There's a build 21314 now posted. It allows you to set log_events: true in the config section of your HassController (in reactor.yaml). This will produce a log of events to logs/hass_events.log. Add that config, restart MSR, trigger some events with your camera, and then set log_events: false and restart MSR. Then DM or email me the hass_events.log file.

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

      F 1 Reply Last reply
      1
      • toggledbitsT toggledbits

        OK. There's a build 21314 now posted. It allows you to set log_events: true in the config section of your HassController (in reactor.yaml). This will produce a log of events to logs/hass_events.log. Add that config, restart MSR, trigger some events with your camera, and then set log_events: false and restart MSR. Then DM or email me the hass_events.log file.

        F Offline
        F Offline
        Fanan
        wrote on last edited by Fanan
        #13

        @toggledbits Thanks! You just got an email!

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

          OK. I see the events. I think this can be handled. If I get time to look at this over the weekend, I certainly will, but expect Monday at the latest.

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

          F 1 Reply Last reply
          1
          • toggledbitsT toggledbits

            OK. I see the events. I think this can be handled. If I get time to look at this over the weekend, I certainly will, but expect Monday at the latest.

            F Offline
            F Offline
            Fanan
            wrote on last edited by
            #15

            @toggledbits No rush. Take care of your son and enjoy the weekend!

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

              OK. I think this is doable on the version you have, which already has some enhancements I carried in from the MQTTController side.

              First, turn off log_events in the config for now; I don't think we'll be needing it. Restart MSR and remove the hass_events.log file from the logs directory.

              Add the following in the config section of your HassController configuration (in reactor.yaml). The event_targets line should be indented to the same level as source and log_events; I've put a config line in to show that, but don't copy it, it's just for reference. I'll explain what all this does after:

                  config:
                    # ... your other config stuff is above this comment; append these lines:
                    event_targets:
                      "nest_hello_motion":
                        name: "Nest Hello Motion"
                        capabilities: 
                          - motion_sensor
                        events:
                        - event:
                            event_type: nest_event
                            data:
                              device_id: "148552cdf7eb1caeb5dad5f6a3874821"
                              type: "camera_motion"
                          response:
                            "motion_sensor.state": true
                            "motion_sensor.since":
                              expr: "time()"
                      "nest_hello_person":
                        capabilities: 
                          - binary_sensor
                        name: "Nest Hello Person"
                        events:
                        - event:
                            event_type: nest_event
                            data:
                              device_id: "148552cdf7eb1caeb5dad5f6a3874821"
                              type: "camera_person"
                          response:
                            "binary_sensor.state": true
                            "binary_sensor.since":
                              expr: "time()"
                     "nest_doorbell":
                        capabilities: 
                          - binary_sensor
                        name: "Nest Doorbell"
                        events:
                        - event:
                            event_type: nest_event
                            data:
                              device_id: "148552cdf7eb1caeb5dad5f6a3874821"
                              type: "doorbell_chime"
                          response:
                            "binary_sensor.state": true
                            "binary_sensor.since":
                              expr: "time()"
              

              This config is going to create three entities in Reactor, the first with ID nest_hello_motion the second with ID nest_hello_person, and third with ID "nest_doorbell". Each of them works about the same, but they look at different Nest events.

              The nest_hello_motion config sets the entity up with the motion_sensor capability (only). It watches for a Home Assistant event of type nest_event that contains in its data the device ID shown and the more specific type camera_motion. When Reactor gets a matching event, it will set the motion_sensor.state attribute on the Reactor entity to true, and update the timestamp in the since attribute for that capability.

              The nest_hello_person config works the same, but looks for Nest's camera_person event. And of course, the nest_doorbell config is looking at the same Home Assistant event type and device ID, but matching only the specific doorbell_chime event.

              Now for the tricky part (in case this hasn't been tricky enough). These events from Nest have no reset. That is, the Nest integration tells you when it detects motion, but not when it stops detecting motion. That means that the state attribute values can never be anything but true in the Reactor entity (there's no way to reset it to false). Therefore, to test if the motion (or person, or doorbell) event has occurred, then, you instead will have to test if since (an extension attribute for the capability) changes, which it will every time the event is received. This is a bit of a shame, because it requires special handling for Nest different from most other devices, but then, that's nothing new. My Amcrest and other cameras do not work this way — their events send true and false detection events so you can tell when the camera no longer detects motion. Alas, not with Nest. So, if at some point in future you need to know when motion is no longer detected, because Nest doesn't tell us you'll have to use condition options to infer it (e.g. test that since has not changed for a certain period). Should work fine, it's just not as easy as when the device/driver gives you an affirmative reset event.

              To generalize, this structure allows you to receive and respond to any Hass event:

                    event_targets:    # this section starts the event-receiving entities
                      "my_virtual_entity_id":     # Assign an ID to your entity; each entity must have a unique ID
                        name: "My Entity Name"   # This is optional but recommended, so you have a friendly name
                        capabilities:  # define an array of capabilities to be modified by the event
                        - capability_name    # first capability
                        - capability_name    # second, etc., as many as you need, but always at least ONE
                        events:  # define an array of events that modify capability attributes on the entity
                        - event:  # start of an event; each element of the events array begins this way
                            event_type: "type of HomeAssistant event"
                            data:  # optional section, if further matching to the event data is required
                              data_field: "data_value"    # data field to be checked/matched to data_value
                              data_field: "data_value"    # as many as you need, but each data_field must be unique
                          response:  # begin the (required) response section for handling the event
                            "capability.attribute":
                              expr: "expression"   # expression to get attribute value from event data
                            # repeat "capability.attribute" section for all attributes modified by the event
              

              This isn't complete for documentation, I'm writing it now. Definitely will be an advanced user feature.

              Also, just FYI, Hass seems to be modifying its person entities when detected by the camera as well, so that's a sneaky thing that's changing when the Nest integration is handling the event on its end. See Hass entity binary_sensor.person_vid_ytterdorren for example (and there should be a Reactor entity with a similar ID, just the dot replaced with underscore).

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

              K 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                OK. I think this is doable on the version you have, which already has some enhancements I carried in from the MQTTController side.

                First, turn off log_events in the config for now; I don't think we'll be needing it. Restart MSR and remove the hass_events.log file from the logs directory.

                Add the following in the config section of your HassController configuration (in reactor.yaml). The event_targets line should be indented to the same level as source and log_events; I've put a config line in to show that, but don't copy it, it's just for reference. I'll explain what all this does after:

                    config:
                      # ... your other config stuff is above this comment; append these lines:
                      event_targets:
                        "nest_hello_motion":
                          name: "Nest Hello Motion"
                          capabilities: 
                            - motion_sensor
                          events:
                          - event:
                              event_type: nest_event
                              data:
                                device_id: "148552cdf7eb1caeb5dad5f6a3874821"
                                type: "camera_motion"
                            response:
                              "motion_sensor.state": true
                              "motion_sensor.since":
                                expr: "time()"
                        "nest_hello_person":
                          capabilities: 
                            - binary_sensor
                          name: "Nest Hello Person"
                          events:
                          - event:
                              event_type: nest_event
                              data:
                                device_id: "148552cdf7eb1caeb5dad5f6a3874821"
                                type: "camera_person"
                            response:
                              "binary_sensor.state": true
                              "binary_sensor.since":
                                expr: "time()"
                       "nest_doorbell":
                          capabilities: 
                            - binary_sensor
                          name: "Nest Doorbell"
                          events:
                          - event:
                              event_type: nest_event
                              data:
                                device_id: "148552cdf7eb1caeb5dad5f6a3874821"
                                type: "doorbell_chime"
                            response:
                              "binary_sensor.state": true
                              "binary_sensor.since":
                                expr: "time()"
                

                This config is going to create three entities in Reactor, the first with ID nest_hello_motion the second with ID nest_hello_person, and third with ID "nest_doorbell". Each of them works about the same, but they look at different Nest events.

                The nest_hello_motion config sets the entity up with the motion_sensor capability (only). It watches for a Home Assistant event of type nest_event that contains in its data the device ID shown and the more specific type camera_motion. When Reactor gets a matching event, it will set the motion_sensor.state attribute on the Reactor entity to true, and update the timestamp in the since attribute for that capability.

                The nest_hello_person config works the same, but looks for Nest's camera_person event. And of course, the nest_doorbell config is looking at the same Home Assistant event type and device ID, but matching only the specific doorbell_chime event.

                Now for the tricky part (in case this hasn't been tricky enough). These events from Nest have no reset. That is, the Nest integration tells you when it detects motion, but not when it stops detecting motion. That means that the state attribute values can never be anything but true in the Reactor entity (there's no way to reset it to false). Therefore, to test if the motion (or person, or doorbell) event has occurred, then, you instead will have to test if since (an extension attribute for the capability) changes, which it will every time the event is received. This is a bit of a shame, because it requires special handling for Nest different from most other devices, but then, that's nothing new. My Amcrest and other cameras do not work this way — their events send true and false detection events so you can tell when the camera no longer detects motion. Alas, not with Nest. So, if at some point in future you need to know when motion is no longer detected, because Nest doesn't tell us you'll have to use condition options to infer it (e.g. test that since has not changed for a certain period). Should work fine, it's just not as easy as when the device/driver gives you an affirmative reset event.

                To generalize, this structure allows you to receive and respond to any Hass event:

                      event_targets:    # this section starts the event-receiving entities
                        "my_virtual_entity_id":     # Assign an ID to your entity; each entity must have a unique ID
                          name: "My Entity Name"   # This is optional but recommended, so you have a friendly name
                          capabilities:  # define an array of capabilities to be modified by the event
                          - capability_name    # first capability
                          - capability_name    # second, etc., as many as you need, but always at least ONE
                          events:  # define an array of events that modify capability attributes on the entity
                          - event:  # start of an event; each element of the events array begins this way
                              event_type: "type of HomeAssistant event"
                              data:  # optional section, if further matching to the event data is required
                                data_field: "data_value"    # data field to be checked/matched to data_value
                                data_field: "data_value"    # as many as you need, but each data_field must be unique
                            response:  # begin the (required) response section for handling the event
                              "capability.attribute":
                                expr: "expression"   # expression to get attribute value from event data
                              # repeat "capability.attribute" section for all attributes modified by the event
                

                This isn't complete for documentation, I'm writing it now. Definitely will be an advanced user feature.

                Also, just FYI, Hass seems to be modifying its person entities when detected by the camera as well, so that's a sneaky thing that's changing when the Nest integration is handling the event on its end. See Hass entity binary_sensor.person_vid_ytterdorren for example (and there should be a Reactor entity with a similar ID, just the dot replaced with underscore).

                K Offline
                K Offline
                kfxo
                wrote on last edited by kfxo
                #17

                I was messing around with this and I think there is an indentation issue starting at line 8. See below for what indentation worked for me.

                      event_targets:    # this section starts the event-receiving entities
                        "my_virtual_entity_id":     # Assign an ID to your entity; each entity must have a unique ID
                          name: "My Entity Name"   # This is optional but recommended, so you have a friendly name
                          capabilities:  # define an array of capabilities to be modified by the event
                            - capability_name    # first capability
                            - capability_name    # second, etc., as many as you need, but always at least ONE
                          events:  # define an array of events that modify capability attributes on the entity
                            - event:  # start of an event; each element of the events array begins this way
                                event_type: "type of HomeAssistant event"
                                data:  # optional section, if further matching to the event data is required
                                  data_field: "data_value"    # data field to be checked/matched to data_value
                                  data_field: "data_value"    # as many as you need, but each data_field must be unique
                              response:  # begin the (required) response section for handling the event
                                "capability.attribute":
                                  expr: "expression"   # expression to get attribute value from event data
                                  # repeat "capability.attribute" section for all attributes modified by the event
                
                1 Reply Last reply
                1
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #18

                  Yeah, there's some ambiguity/disagreement with respect to indenting of array elements, and yamllint and the library I'm using to parse YAML disagree. Bottom line, do what works, and what you've shown is typical for the way I indent such arrays. I'll make sure the docs reflect that.

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

                  K 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    Yeah, there's some ambiguity/disagreement with respect to indenting of array elements, and yamllint and the library I'm using to parse YAML disagree. Bottom line, do what works, and what you've shown is typical for the way I indent such arrays. I'll make sure the docs reflect that.

                    K Offline
                    K Offline
                    kfxo
                    wrote on last edited by
                    #19

                    This is off topic to the original post so maybe it should be moved but it is directed towards the Home Assistant event_targets discussed above.

                    I defined an event_target in my system for emulated roku that looks like this:

                        event_targets:
                          "LR_Emulated_Roku_Home_Keypress":
                            name: "LR Emulated Roku Home Keypress"
                            capabilities:
                              - button
                            events:
                              - event:
                                  event_type: "roku_command"
                                  data:
                                    source_name: "LR_Roku"
                                    type: "keypress"
                                    key: "Home"
                                response:
                                  "button.since":
                                    expr: "time()"
                                  "button.state": true
                    

                    This works great, detects the event and stores the time and True in the respective button entity attributes. However upon restarting MSR the values of the button entity attributes clear to null (e.g. button.since=null).

                    Is this expected behavior or should these values be maintained on restart?

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

                      This is expected behavior for the moment, but will be changing. MSR has never had a need to persist entities over restarts because the controllers have the current data. It's not even an issue for MQTT, because retained messages, when used properly, update state correctly on restart/reconnect.

                      But, I have been using a version of MSR in my own home that persists entities across restarts, for other reasons, and that will also serve to smooth out the bump for event handling here. I still have a few more wrinkles to smooth out... like how to detect when the user has changed their custom configuration for an entity, modified their own custom declaration of a capability, etc. These are rarely-used features, but I nonetheless want them to require less user intervention (e.g. manual forced purge of retention data, etc).

                      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
                      • F Fanan marked this topic as a question on
                      • F Fanan has marked this topic as solved 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

                      • Gradually turn on lights.
                        G
                        gwp1
                        0
                        4
                        114

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

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        96

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

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

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

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        81

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        431

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

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

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

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