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. Actionable notification question
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
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
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor
Cloning actions in reactions does not work
tunnusT
With build 26140 (on Docker) I'm not able to clone any actions in reactions. Using Chrome if it has any relevance.
Multi-System Reactor
Has ping command been removed?
tunnusT
Topic thumbnail image
Multi-System Reactor
ReferenceError with Home Assistant data & build 26140
tunnusT
Topic thumbnail image
Multi-System Reactor

Actionable notification question

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 4 Posters 2.0k 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.
  • T Offline
    T Offline
    tamorgen
    wrote on last edited by
    #1

    Good morning,
    I'm running Home Assistant with MSR, and I do my automation strictly within MSR. I have some basic notifications set up, for instance, when my dishwasher has completed it's cycle, it'll send my iPhone a push notification via the x_haas.system.call_service --> notify.mobile_iphone action.

    I saw in the Home Assistant documentation that you can push Actionable Notifications. The example they use if there is motion detection, but no one is home, you can sound an alarm or silence an alarm.

    Can this be done from MSR and not directly in Home Assistant? I'd like to do something more of an acknowledgement, like if a door or window is left open, to have a way to get notified, but acknowledge that it is open, and not send any more notifications. If not acknowledged, the notification will continue every 5 or 10 minutes until the door or window is closed, or the notification is acknowledged. This would be useful in situations where I may have a slider door open for some fresh air, so it was deliberate, versus an entry door that didn't latch when entering or leaving the house.

    1 Reply Last reply
    0
    • PablaP Offline
      PablaP Offline
      Pabla
      wrote on last edited by
      #2

      I haven't found a way to create actionable notifications in MSR because HA doesn't expose the mobile_app_notification_action event. The way I do it instead is create the actionable notification action in HA then have MSR trigger it.

      G toggledbitsT 2 Replies Last reply
      0
      • PablaP Pabla

        I haven't found a way to create actionable notifications in MSR because HA doesn't expose the mobile_app_notification_action event. The way I do it instead is create the actionable notification action in HA then have MSR trigger it.

        G Offline
        G Offline
        gwp1
        wrote on last edited by
        #3

        @Pabla I like this.

        I do something similar with my LIFX bulbs. For some yet-to-be-discovered reason two of them turn on during the day. My Hubitat integration were they live does not see it... but my HA integration does. So I created a ruleset in MSR that watches the HA version of the lights and fires an HA automation that turns them off.

        More than one way to get to the circus!

        *Hubitat C-7 2.5.1.142
        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

        *HAOS
        Core 2026.7.4
        w/ HA Connect ZWA-2
        FW: v1.1
        SDK: v7.23.1

        *Prod MSR in docker/portainer
        MSR: latest-26193-8dd8f854
        MQTTController: 25139
        ZWave Controller: 25139

        1 Reply Last reply
        0
        • PablaP Pabla

          I haven't found a way to create actionable notifications in MSR because HA doesn't expose the mobile_app_notification_action event. The way I do it instead is create the actionable notification action in HA then have MSR trigger it.

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

          @Pabla said in Actionable notification question:

          I haven't found a way to create actionable notifications in MSR because HA doesn't expose the mobile_app_notification_action event.

          I'm not exactly sure what you mean or intend here, but I just ran a quick test using the service call HA provides in their documentation for Actionable Notifications (linked in the head post), and Reactor does see the mobile_app_notification_action event when a button is pressed on the mobile app notification (Android tested). Here's the service call I made:

          service: notify.mobile_app_sm_g996u
          data:
            message: "Something happened at home!"
            data:
              actions:
                - action: "ALARM"
                  title: "Sound Alarm"
                  icon: "sfsymbols:bell"
                - action: "SILENCE"
                  title: "Silence Alarm"
                  icon: "sfsymbols:bell.slash"
          

          When the Sound Alarm button on the notifications is pressed, Reactor gets this event:

          {
              "type": "event",
              "event": {
                  "event_type": "mobile_app_notification_action",
                  "data": {
                      "action_2_title": "Silence Alarm",
                      "webhook_id": "2f7fba8991b3bfac3a5fb46ace19cd6d616becb829aecb5a8ae2a2ece759052f",
                      "message": "Something happened at home!",
                      "action_1_title": "Sound Alarm",
                      "action_1_key": "ALARM",
                      "action_2_key": "SILENCE",
                      "server_id": "1",
                      "action": "ALARM",
                      "device_id": "c8458cf66b182e07"
                  },
                  "origin": "REMOTE",
                  "time_fired": "2024-01-23T00:59:00.722438+00:00",
                  "context": {
                      "id": "01HMSX7RQJDJYFFQPJFWX8HEG8",
                      "parent_id": null,
                      "user_id": "459ddf6f84b14de98f4c65e2d2da2dc6"
                  }
              },
              "id": 1705971523928
          }
          

          So in Reactor, I can configure an event reaction (in reactor.yaml for a HassController instance):

            config:  # this line is for alignment only
              event_targets:
               notification_sound_alarm:
                  capabilities:
                  - binary_sensor
                  events:
                  - event:
                      event_type: mobile_app_notification_action
                      data:
                        device_id: "c8458cf66b182e07"
                        action: "ALARM"
                    response:
                      "binary_sensor.state":
                        expr: "! entity.attributes.binary_sensor.state"
          

          This trivial event handler just toggles the binary_sensor.state attribute in the associated virtual device it creates (having ID notification_sound_alarm), every time the event is received.

          Works a treat. Really cool actually. Actionable Notifications... TIL.

          Ref to docs for creating event handlers: https://reactor.toggledbits.com/docs/HassController/#handling-home-assistant-events

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

          PablaP T 2 Replies Last reply
          👏🏻
          3
          • toggledbitsT toggledbits

            @Pabla said in Actionable notification question:

            I haven't found a way to create actionable notifications in MSR because HA doesn't expose the mobile_app_notification_action event.

            I'm not exactly sure what you mean or intend here, but I just ran a quick test using the service call HA provides in their documentation for Actionable Notifications (linked in the head post), and Reactor does see the mobile_app_notification_action event when a button is pressed on the mobile app notification (Android tested). Here's the service call I made:

            service: notify.mobile_app_sm_g996u
            data:
              message: "Something happened at home!"
              data:
                actions:
                  - action: "ALARM"
                    title: "Sound Alarm"
                    icon: "sfsymbols:bell"
                  - action: "SILENCE"
                    title: "Silence Alarm"
                    icon: "sfsymbols:bell.slash"
            

            When the Sound Alarm button on the notifications is pressed, Reactor gets this event:

            {
                "type": "event",
                "event": {
                    "event_type": "mobile_app_notification_action",
                    "data": {
                        "action_2_title": "Silence Alarm",
                        "webhook_id": "2f7fba8991b3bfac3a5fb46ace19cd6d616becb829aecb5a8ae2a2ece759052f",
                        "message": "Something happened at home!",
                        "action_1_title": "Sound Alarm",
                        "action_1_key": "ALARM",
                        "action_2_key": "SILENCE",
                        "server_id": "1",
                        "action": "ALARM",
                        "device_id": "c8458cf66b182e07"
                    },
                    "origin": "REMOTE",
                    "time_fired": "2024-01-23T00:59:00.722438+00:00",
                    "context": {
                        "id": "01HMSX7RQJDJYFFQPJFWX8HEG8",
                        "parent_id": null,
                        "user_id": "459ddf6f84b14de98f4c65e2d2da2dc6"
                    }
                },
                "id": 1705971523928
            }
            

            So in Reactor, I can configure an event reaction (in reactor.yaml for a HassController instance):

              config:  # this line is for alignment only
                event_targets:
                 notification_sound_alarm:
                    capabilities:
                    - binary_sensor
                    events:
                    - event:
                        event_type: mobile_app_notification_action
                        data:
                          device_id: "c8458cf66b182e07"
                          action: "ALARM"
                      response:
                        "binary_sensor.state":
                          expr: "! entity.attributes.binary_sensor.state"
            

            This trivial event handler just toggles the binary_sensor.state attribute in the associated virtual device it creates (having ID notification_sound_alarm), every time the event is received.

            Works a treat. Really cool actually. Actionable Notifications... TIL.

            Ref to docs for creating event handlers: https://reactor.toggledbits.com/docs/HassController/#handling-home-assistant-events

            PablaP Offline
            PablaP Offline
            Pabla
            wrote on last edited by
            #5

            @toggledbits Every time I think I have Reactor figured out I always end up learning something new! Will defs be playing with this

            1 Reply Last reply
            1
            • toggledbitsT toggledbits

              @Pabla said in Actionable notification question:

              I haven't found a way to create actionable notifications in MSR because HA doesn't expose the mobile_app_notification_action event.

              I'm not exactly sure what you mean or intend here, but I just ran a quick test using the service call HA provides in their documentation for Actionable Notifications (linked in the head post), and Reactor does see the mobile_app_notification_action event when a button is pressed on the mobile app notification (Android tested). Here's the service call I made:

              service: notify.mobile_app_sm_g996u
              data:
                message: "Something happened at home!"
                data:
                  actions:
                    - action: "ALARM"
                      title: "Sound Alarm"
                      icon: "sfsymbols:bell"
                    - action: "SILENCE"
                      title: "Silence Alarm"
                      icon: "sfsymbols:bell.slash"
              

              When the Sound Alarm button on the notifications is pressed, Reactor gets this event:

              {
                  "type": "event",
                  "event": {
                      "event_type": "mobile_app_notification_action",
                      "data": {
                          "action_2_title": "Silence Alarm",
                          "webhook_id": "2f7fba8991b3bfac3a5fb46ace19cd6d616becb829aecb5a8ae2a2ece759052f",
                          "message": "Something happened at home!",
                          "action_1_title": "Sound Alarm",
                          "action_1_key": "ALARM",
                          "action_2_key": "SILENCE",
                          "server_id": "1",
                          "action": "ALARM",
                          "device_id": "c8458cf66b182e07"
                      },
                      "origin": "REMOTE",
                      "time_fired": "2024-01-23T00:59:00.722438+00:00",
                      "context": {
                          "id": "01HMSX7RQJDJYFFQPJFWX8HEG8",
                          "parent_id": null,
                          "user_id": "459ddf6f84b14de98f4c65e2d2da2dc6"
                      }
                  },
                  "id": 1705971523928
              }
              

              So in Reactor, I can configure an event reaction (in reactor.yaml for a HassController instance):

                config:  # this line is for alignment only
                  event_targets:
                   notification_sound_alarm:
                      capabilities:
                      - binary_sensor
                      events:
                      - event:
                          event_type: mobile_app_notification_action
                          data:
                            device_id: "c8458cf66b182e07"
                            action: "ALARM"
                        response:
                          "binary_sensor.state":
                            expr: "! entity.attributes.binary_sensor.state"
              

              This trivial event handler just toggles the binary_sensor.state attribute in the associated virtual device it creates (having ID notification_sound_alarm), every time the event is received.

              Works a treat. Really cool actually. Actionable Notifications... TIL.

              Ref to docs for creating event handlers: https://reactor.toggledbits.com/docs/HassController/#handling-home-assistant-events

              T Offline
              T Offline
              tamorgen
              wrote on last edited by
              #6

              @toggledbits, it's going to take soem time to wrap my head around everything you posted, but it's great to know it's possible!

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

                I realize the documentation on configuring event handlers isn't great. I've made some updates and will post them later today, but I still feel it needs work. Feel free to ask questions and make suggestions; then I'll know what holes to fill.

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


                Recent Topics

                • Upgrade Issues
                  T
                  tbully
                  0
                  9
                  102

                • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                  toggledbitsT
                  toggledbits
                  0
                  10
                  73

                • [SOLVED] Question regarding "in" vs "contains" vs contents of the string
                  G
                  gwp1
                  0
                  5
                  27

                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  147
                  127.3k

                • openLuup console disappeared - 500 - Internal Server Error
                  A
                  a-lurker
                  0
                  2
                  148

                • Logon screen timeout
                  G
                  gwp1
                  0
                  5
                  172

                • [MSR] Copy&past of actions and/or drag&drop between set/reset
                  toggledbitsT
                  toggledbits
                  0
                  9
                  322

                • Upgrade advice - upgrade from aarch64 to ARM64 image
                  toggledbitsT
                  toggledbits
                  0
                  4
                  186

                • Alexa for MSR, any interest?
                  CatmanV2C
                  CatmanV2
                  2
                  4
                  321

                • Ezlo Paid Subscription for Vera Cloud Services
                  therealdbT
                  therealdb
                  4
                  2
                  451

                • [RESOLVED] Telegram notification broke with latest update
                  CatmanV2C
                  CatmanV2
                  0
                  11
                  783
                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