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. [RESOLVED] Telegram notification broke with latest update
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
MFA
T
Topic thumbnail image
Multi-System Reactor
Login protections
tunnusT
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
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
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

[RESOLVED] Telegram notification broke with latest update

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

    Running MSR "latest-26174-bd90c17c" via a docker within unRAID. With this latest docker update a day or two ago, Telegram stopped working. In looking at the logs, the ultimate error is that the chat_id is missing. I verified that my chat ID is still noted within the notifications YAML, but the reactor log still shows it failing. If I manually paste the chat ID into the notification field in the GUI, MSR will send the telegram message. It appears to be ignoring the "If left blank, the profile's default_chat_id value will be used."

    Error log

    [latest-26174]2026-06-26T18:04:45.814Z <Engine:INFO> Enqueueing "rule-2ajie2fd<SET>" (rule-2ajie2fd:S)
[latest-26174]2026-06-26T18:04:45.815Z <Engine:NOTICE> Starting reaction rule-2ajie2fd<SET> (rule-2ajie2fd:S)
[latest-26174]2026-06-26T18:04:45.815Z <Engine:INFO> rule-2ajie2fd<SET> all actions completed.
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:ERR> NotifyTelegram failure response from endpoint: 400 Bad Request
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:INFO> NotifyTelegram request URL: https://api.telegram.org/bot[[REDACTED]]:[[REDACTED]]/sendMessage
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:INFO> NotifyTelegram request body: {"text":"Test message","chat_id":""}
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:INFO> NotifyTelegram request headers: { "content-type": "application/json", "content-length": (undefined) }
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:ERR> NotifyTelegram request to https://api.telegram.org/bot[[REDACTED]]:[[REDACTED]]/sendMessage message Test message
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/opt/reactor/server/lib/NotifyTelegram.js:300:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/opt/reactor/server/lib/Notifier.js:189:137)
[latest-26174]2026-06-26T18:04:45.983Z <Engine:ERR> Engine#1 reaction rule-2ajie2fd:S step 1 notification (Telegram) failed: [Error] NotifyTelegram request failed [-]
[latest-26174]2026-06-26T18:04:45.983Z <Engine:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/opt/reactor/server/lib/NotifyTelegram.js:300:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/opt/reactor/server/lib/Notifier.js:189:137)
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat_id is empty"}

    Snippet of the notification yaml with all the description text removed:

      # Telegram
  Telegram:
    profiles:
      default:
        description: Default Profile
        api_url: https://api.telegram.org
        bot_token: "[[REDACTED]]:[[REDACTED]]"
        default_chat_id: "[[REDACTED]]"

    529e0b3a-16a5-461b-9cd0-1971b8706666-image.png

    1 Reply Last reply
    0
    • wmarcolinW Offline
      wmarcolinW Offline
      wmarcolin
      wrote on last edited by
      #2

      If it might help with the investigation, here is the error message I'm getting when I run the query.

      systemctl status reactor
      ● reactor.service - Multi System Reactor
      Loaded: loaded (/etc/systemd/system/reactor.service; enabled; preset: enabled)
      Drop-In: /etc/systemd/system/reactor.service.d
      └─override.conf
      Active: active (running) since Fri 2026-06-26 14:48:22 EST; 38min ago
      Main PID: 6370 (MainThread)
      Tasks: 11 (limit: 4599)
      Memory: 112.8M (peak: 157.1M)
      CPU: 28.239s
      CGroup: /system.slice/reactor.service
      └─6370 /usr/bin/node app -p

      Jun 26 15:06:23 reactor node[6370]: at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:189:137)
      Jun 26 15:06:23 reactor node[6370]: [latest-26174]2026-06-26T20:06:23.394Z Engine:CRIT Error: NotifyTelegram request failed [-]
      Jun 26 15:06:23 reactor node[6370]: Error: NotifyTelegram request failed
      Jun 26 15:06:23 reactor node[6370]: at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:300:23)
      Jun 26 15:06:23 reactor node[6370]: at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
      Jun 26 15:06:23 reactor node[6370]: at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:189:137)
      Jun 26 15:11:10 reactor node[6370]: [latest-26174]2026-06-26T20:11:10.209Z Engine:CRIT Error: terminated [preempted by rule state change]
      Jun 26 15:11:10 reactor node[6370]: Error: terminated
      Jun 26 15:11:10 reactor node[6370]: at Engine._process_reaction_queue (/home/wilson/reactor/server/lib/Engine.js:2091:47)
      Jun 26 15:11:10 reactor node[6370]: at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
      root@reactor:/home/wilson/reactor/logs#

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

        OK. Fix coming soon...

        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
        • 3 Offline
          3 Offline
          3rdStng
          wrote on last edited by
          #4

          I upgraded the docker to version latest-26177-be756a68. Unfortunately I am still not getting my Telegram alerts unless I put the Chat ID in the GUI. I don't know if it matters, but my chat_id starts with a "-". I think I have another chat ID that does not start/show as a negative ID. I can't test with that ID though.

          1 Reply Last reply
          0
          • 3 Offline
            3 Offline
            3rdStng
            wrote on last edited by
            #5

            Thank you @toggledbits. The latest-26177-3f86f4af build resolved the issue.

            1 Reply Last reply
            1
            • wmarcolinW Offline
              wmarcolinW Offline
              wmarcolin
              wrote on last edited by
              #6

              I think my situation with Telegram is a little different. Version 26177 has actually partially resolved the sending issue.

              I have two profiles set up, with two token and two ChatID, as you can see below (change the token and ChatID). For the first profile, I can send a message without entering the Chat ID in “Set Reaction.” For the second profile, if I leave it blank, it doesn’t send the message—it doesn’t use the settings I’ve configured. If I enter the Chat ID for the second profile, then the message sends perfectly.

                # Telegram
  Telegram:
    profiles:
      default:
        # description - A friendly description of this profile (for menus)
        description: Default Familia
        #
        # api_url - NOTIFICATION Access URL for Telegram API. Default is https://api.telegram.org/
        api_url: https://api.telegram.org
        #
        # bot_token - (required) Bot Token, from Telegram. See: https://core.telegram.org/bots
        bot_token: "xxxxxxxxxx:AAEOr9ZY4LxxxxxxxKPYJBSBxxxxxxxxxx"
        #
        # default_chat_id - (required) Default chat ID to use if not specified in message. See
        #                   this link for how to get chat ID:
        #                   https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id
        default_chat_id: "-1234567890"
        #
        # default_disable_notification - Default notification flag, may be either "true"
        #                                or "false". The system default is "false"
        #                                (false == notification enabled/not disabled).
        default_disable_notification: "false"
        #
        # default_parse_mode - Default message format/parse mode. The system default is
        #                      blank, for plain text. Other options: MarkdownV2, HTML
        #                      See: https://core.telegram.org/bots/api#formatting-options
        default_parse_mode: "HTML"
      wilson:
        # description - INFORMATION A friendly description of this profile (for menus)
        description: Default Wilson
        #
        # api_url - Access URL for Telegram API. Default is https://api.telegram.org/
        api_url: https://api.telegram.org
        #
        # bot_token - (required) Bot Token, from Telegram. See: https://core.telegram.org/bots
        bot_token: "xxxxxxxxxx:AAEFPoERxxxxxxxxkKFdEHc3txxxxxxxxxx"
        #
        # default_chat_id - (required) Default chat ID to use if not specified in message. See
        #                   this link for how to get chat ID:
        #                   https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id
        # 6272 default_chat_id: "1544809334"
        default_chat_id: "-1234567890"
        #
        # default_disable_notification - Default notification flag, may be either "true"
        #                                or "false". The system default is "false"
        #                                (false == notification enabled/not disabled).
        default_disable_notification: "false"
        #
        # default_parse_mode - Default message format/parse mode. The system default is
        #                      blank, for plain text. Other options: MarkdownV2, HTML
        #                      See: https://core.telegram.org/bots/api#formatting-options
        default_parse_mode: "HTML"
              1 Reply Last reply
              0
              • wmarcolinW Offline
                wmarcolinW Offline
                wmarcolin
                wrote on last edited by
                #7

                @toggledbits I ran tests after upgrading Node.js, and the scenario is as described above; for the second profile, it only works if you enter the Chat ID.

                1 Reply Last reply
                0
                • wmarcolinW Offline
                  wmarcolinW Offline
                  wmarcolin
                  wrote on last edited by
                  #8

                  Now that the log file has fewer errors (Node.js), I can see this log message appear—I'm not sure if it helps.

                  [latest-26177]2026-06-28T23:20:20.829Z <NotifyTelegram:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:304:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:188:145)
[latest-26177]2026-06-28T23:20:20.830Z <Engine:ERR> Engine#1 reaction rule-mevuuj8w:S step 3 notification (Telegram) failed: [Error] NotifyTelegram request failed [-]
[latest-26177]2026-06-28T23:20:20.830Z <Engine:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:304:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:188:145)
[latest-26177]2026-06-28T23:20:20.831Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
                  1 Reply Last reply
                  0
                  • CatmanV2C Offline
                    CatmanV2C Offline
                    CatmanV2
                    wrote on last edited by
                    #9

                    I came here as I was seeing the same Telegram behaviour. I only have one profile. so am happy that the fix will resolve it for me

                    C

                    The Ex-Vera abuser know as CatmanV2.....

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

                      @CatmanV2 A subsequent (to the prior post) respin of build 26177 fixed multiple profiles as well, so you're good either 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
                      1
                      • CatmanV2C Offline
                        CatmanV2C Offline
                        CatmanV2
                        wrote on last edited by
                        #11

                        As ever, my thanks. Upgraded to 26177 and all is well!

                        C

                        The Ex-Vera abuser know as CatmanV2.....

                        1 Reply Last reply
                        1
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes

                        Recent Topics

                        • Grouped devices
                          G
                          gwp1
                          0
                          3
                          47
                        • Reverse proxy & API ACL
                          tunnusT
                          tunnus
                          0
                          3
                          45
                        • MFA
                          toggledbitsT
                          toggledbits
                          0
                          17
                          353
                        • Login protections
                          toggledbitsT
                          toggledbits
                          0
                          2
                          120
                        • Reactor (Multi-System/Multi-Hub) Announcements
                          toggledbitsT
                          toggledbits
                          5
                          152
                          151.3k
                        • Reactor Inspect - a small read-only helper panel for MSR
                          G
                          gwp1
                          2
                          6
                          364
                        • Reactor Build 26284 stuck at Loading Reactor UI
                          T
                          tamorgen
                          0
                          16
                          1.4k
                        • MSR with reverse proxy
                          tunnusT
                          tunnus
                          0
                          12
                          720
                        • Missing attribute after upgrade
                          3
                          3rdStng
                          0
                          3
                          417
                        • Use of Google Gemini as an MSR and Hubitat configuration aid
                          therealdbT
                          therealdb
                          0
                          2
                          239
                        • [MSR] Native fan capabilty
                          therealdbT
                          therealdb
                          1
                          3
                          242
                        • [MSR] Rule do not fire
                          therealdbT
                          therealdb
                          0
                          4
                          344
                        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