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)?
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
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
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 957 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 toggledbits

    OK, as I suspected, there's no data there for anything other than the camera feed. You need to go into the integration, go to the device, and enable the sensor entities (probably marked hidden) for that device. You should then see binary sensors related to the camera in Lovelace. Once you have that, restart MSR and it should pick up those sensors as entities.

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

    @toggledbits the problem is that's it's not a entities, only a trigger. So it's not hidden. I have other cameras with hidden entities, so it's not that i don't know where our how to find it. I can only access it as a trigger when i do a automation within HA, as in the pic in my first post.

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

      The camera itself is a device. That's where you go. I assume you configured this integration through the UI, as it seems like a "first class" integration, not one of the components you configure directly in configuration.yaml or other. I don't have these devices, so I can't help you beyond that. But the typical way is to go to the parent device, and enable its children, in effect. At least, it works this way with every other integration I have, including other non-Nest cameras.

      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
      • K Offline
        K Offline
        kfxo
        wrote on last edited by
        #9

        It appears from the Nest- Home Assistant docs that the doorbell generates a nest_event (doorbell_chime). Unfortunately I do not believe there is any way for MSR to see these events. I have brought this up previously with respect to Emulated Roku. My work around is to use a native HA automation to detect the event and trigger a helper object that MSR can see, in my case I place the text of the event in a input_text helper which MSR can see.

        F 1 Reply Last reply
        1
        • K kfxo

          It appears from the Nest- Home Assistant docs that the doorbell generates a nest_event (doorbell_chime). Unfortunately I do not believe there is any way for MSR to see these events. I have brought this up previously with respect to Emulated Roku. My work around is to use a native HA automation to detect the event and trigger a helper object that MSR can see, in my case I place the text of the event in a input_text helper which MSR can see.

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

          @kfxo Thanks - I believe this is the way to go. I'll give it a try in a few days.
          /Fanan

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

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

                              • Reactor (Multi-System/Multi-Hub) Announcements
                                toggledbitsT
                                toggledbits
                                5
                                122
                                35.4k

                              • Z-Wave Future....
                                CatmanV2C
                                CatmanV2
                                0
                                5
                                131

                              • Can´t restart or upgrade/deploy MSR
                                toggledbitsT
                                toggledbits
                                0
                                4
                                86

                              • [Solved] Limit HA Entity in MSR
                                wmarcolinW
                                wmarcolin
                                0
                                7
                                191

                              • Disaster recovery and virtualisation
                                CatmanV2C
                                CatmanV2
                                0
                                5
                                661

                              • Remote access of Zwave stick from Z-wave server
                                CatmanV2C
                                CatmanV2
                                0
                                3
                                384

                              • Organizing/ structuring rule sets and rules
                                G
                                gwp1
                                0
                                5
                                374

                              • Moving MSR from a QNAP container to RP 5 - some issues
                                G
                                gwp1
                                0
                                5
                                346

                              • Widget deletion does not work and landing page (status) is empy
                                G
                                gwp1
                                0
                                4
                                338

                              • Need help reducing false positive notifications
                                T
                                tamorgen
                                0
                                7
                                520
                              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