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 Telegram working?
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor

Is Telegram working?

Scheduled Pinned Locked Moved Multi-System Reactor
27 Posts 5 Posters 5.4k 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

    The chat ID in your HTTPS fetch has a minus sign at the front, while the chat ID in MSR does not. Check you configuration again.

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

    @toggledbits

    Well spotted I didn't even notice that.

    I added a minus sign also in the notification.yaml file and now its working from MSR.

    1 Reply Last reply
    1
    • toggledbitsT toggledbits

      The chat ID in your HTTPS fetch has a minus sign at the front, while the chat ID in MSR does not. Check you configuration again.

      wmarcolinW Offline
      wmarcolinW Offline
      wmarcolin
      wrote on last edited by
      #11

      @toggledbits minus is allowed, and is a message for a group. When it does not have a minus sign, it is for a single user.

      1 Reply Last reply
      0
      • cw-kidC cw-kid

        @toggledbits said in Is Telegram working?:

        Did you include it in the config?

        Yes and No.

        Seems I needed to restart Reactor engine.

        I now see the correct full bot ID string in the log file OK.

        Also I had to remove "bot" from the yaml file as MSR puts than in for you.

        However its still not working.

        I am still getting 404.

        This is what I see now in the log:

        2021-06-18T17:25:12.205Z <Engine:INFO> Enqueueing "Test Telegram" (re-kq29nxzw)
        2021-06-18T17:25:12.210Z <Engine:5:Engine.js:953> Engine#1 enqueued reaction re-kq29nxzw as 6
        2021-06-18T17:25:12.212Z <Engine:5:Engine.js:1108> _process_reaction_queue() wake-up!
        2021-06-18T17:25:12.215Z <Engine:5:Engine.js:1069> _process_reaction_queue() running task 6 { "tid": 6, "id": "re-kq29nxzw", "rule": --undef--, "__reaction": GlobalReaction#re-kq29nxzw, "next_step": 0, "status": 0, "ts": 1624037112207, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
        2021-06-18T17:25:12.216Z <Engine:NOTICE> Starting reaction Test Telegram (re-kq29nxzw)
        2021-06-18T17:25:12.217Z <Engine:5:Engine.js:1216> Engine#1 reaction re-kq29nxzw step 0 notify Telegram with { "message": "This is a TEST", "profile": "default" }
        2021-06-18T17:25:12.218Z <Engine:5:NotifyTelegram.js:159> NotifyTelegram sending profile default notification request: This is a TEST
        2021-06-18T17:25:12.222Z <Engine:INFO> Test Telegram all actions completed.
        2021-06-18T17:25:12.223Z <Engine:5:Engine.js:1073> _process_reaction_queue() task returned, new status -1; task 6
        2021-06-18T17:25:12.226Z <Engine:5:Engine.js:1108> _process_reaction_queue() ending with 1 in queue; waiting for 1 (next delayed task)
        2021-06-18T17:25:12.349Z <Engine:ERR> NotifyTelegram failure response from endpoint: 400 Bad Request
        2021-06-18T17:25:12.351Z <Engine:ERR> NotifyTelegram fres=[object Response]
        2021-06-18T17:25:12.352Z <Engine:INFO> NotifyTelegram request URL: https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage
        2021-06-18T17:25:12.352Z <Engine:INFO> NotifyTelegram request body: {"text":"This is a TEST","chat_id":"314603256"}
        2021-06-18T17:25:12.353Z <Engine:ERR> NotifyTelegram request to https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage failed: Error: NotifyTelegram request failed
        2021-06-18T17:25:12.354Z <Engine:ERR> Engine#1 reaction re-kq29nxzw step 0 notification (Telegram) failed: Error: NotifyTelegram request failed
        
        wmarcolinW Offline
        wmarcolinW Offline
        wmarcolin
        wrote on last edited by
        #12

        @cw-kid this comment about having the letters bot in front is already added by MSR, we have to be careful, because when we copy the ID when it is generated in Telegram it comes with these letters bot in front that has to be removed when configuring. I had the same problem until I identified this in the log appearing twice botbot.

        cw-kidC 1 Reply Last reply
        1
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #13

          Where are you seeing that? I can't screenshot the Android app because it won't let me (security policy--smart!), but the response to /newbot from BotFather does not contain the string "bot" in front of the key. Are you seeing it elsewhere? Maybe iOS?

          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
          • wmarcolinW wmarcolin

            @cw-kid this comment about having the letters bot in front is already added by MSR, we have to be careful, because when we copy the ID when it is generated in Telegram it comes with these letters bot in front that has to be removed when configuring. I had the same problem until I identified this in the log appearing twice botbot.

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

            @wmarcolin said in Is Telegram working?:

            I had the same problem until I identified this in the log appearing twice botbot.

            Yes indeed, that is what I was seeing in the log file also.

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

              Well first I don't remember how to get the ID, I don't remember when the number was generated 🙂 lol

              I think what may have created confusion, was that when using a direct call, as the example below is necessary to put the bot, but when configuring the MSR not, because the application already adds the information.

              https://api.telegram.org/bot177_____83:AAER___________________________GTGk/getUpdates

              I think the situation is closed, we just have to stay alert to some other user who mentions that Telegram is not working pass this orientation.

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

                The key/token in the response from BotFather when creating the bot will not have 'bot' prepended to it, so that makes sense.

                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
                • cw-kidC Offline
                  cw-kidC Offline
                  cw-kid
                  wrote on last edited by
                  #17

                  Yesterday I converted all my rules to use the now inbuilt notify for Telegram, rather than sending Http requests out as I was.

                  No further problems and everything seems to be working well.

                  Thanks for adding Telegram support, I had previously requested it, but at that time it sounded like it would not be added.

                  F 1 Reply Last reply
                  0
                  • cw-kidC cw-kid

                    Yesterday I converted all my rules to use the now inbuilt notify for Telegram, rather than sending Http requests out as I was.

                    No further problems and everything seems to be working well.

                    Thanks for adding Telegram support, I had previously requested it, but at that time it sounded like it would not be added.

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

                    Hi!
                    I've been trying to get Telegram to work, but I think it's something I'm doing wrong in the notification.yaml. It's working from within Home Assistent, but not with MSR. This is from my Notification.yaml:

                      Telegram:
                        profiles:
                          default:
                            # description - A friendly description of this profile (for menus)
                            description: Telegram
                            #
                            # 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: "2091____________(blanked for security reason)____________wH2Z0"
                            #
                            # 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: "77________07"
                            #
                            # 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: ""
                    

                    I have tried both with and without qoutes " " around chat_id and bot_token. Am I missing something? I'm on MSR ver 21337. Thanks in advance.
                    /Fanan

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

                      Telegram is working fine for me. Any chance you've looked at your logs?

                      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
                      0
                      • toggledbitsT toggledbits

                        Telegram is working fine for me. Any chance you've looked at your logs?

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

                        @toggledbits This is my log (I changed my personal info):

                        [latest-21342]2021-12-09T18:38:18.936Z <Engine:NOTICE> Resuming reaction Tända hos Khalisi<SET> (rule-kuvhc9mc:S) from step 1
                        [latest-21342]2021-12-09T18:38:18.939Z <Engine:INFO> Tända hos Khalisi<SET> all actions completed.
                        [latest-21342]2021-12-09T18:38:19.248Z <NotifyTelegram:ERR> NotifyTelegram failure response from endpoint: 400 Bad Request
                        [latest-21342]2021-12-09T18:38:19.248Z <NotifyTelegram:INFO> NotifyTelegram request URL: https://api.telegram.org/bot2091333304:AXXpXQDQJ1L19xQoI1Gyc9i5XEH0uIwH2Z0/sendMessage
                        [latest-21342]2021-12-09T18:38:19.249Z <NotifyTelegram:INFO> NotifyTelegram request body: {"text":"Hello!!","chat_id":"7777777","disable_notification":"false"}
                        [latest-21342]2021-12-09T18:38:19.249Z <NotifyTelegram:ERR> NotifyTelegram request to https://api.telegram.org/bot2091550404:AXXXXQDQJ1L19xQoI1Gyc9i5XEH0uIwH2Z0/sendMessage failed: Error: NotifyTelegram request failed
                        [latest-21342]2021-12-09T18:38:19.249Z <Engine:ERR> Engine#1 reaction rule-kuvhc9mc:S step 1 notification (Telegram) failed: Error: NotifyTelegram request failed
                        [latest-21342]2021-12-09T18:38:19.250Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
                        
                        1 Reply Last reply
                        0
                        • toggledbitsT Offline
                          toggledbitsT Offline
                          toggledbits
                          wrote on last edited by
                          #21

                          OK, you've found the issue.

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

                          G 1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            OK, you've found the issue.

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

                            WAIT, WAIT, CAN I TELL HIM??? CAN I, CAN I....??

                            🙂

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

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

                            *Prod MSR in docker/portainer
                            MSR: latest-26011-c621bbc7
                            MQTTController: 25139
                            ZWave Controller: 25139

                            1 Reply Last reply
                            0
                            • F Offline
                              F Offline
                              Fanan
                              wrote on last edited by
                              #23

                              I feel like a total fool - but I don't get it... I know it's right in front of me, but I can't see the forest for the trees...

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

                                No worries. Just trying to teach fishing rather than just handing the fish over...

                                The last line of your log snippet:

                                [latest-21342]2021-12-09T18:38:19.250Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
                                

                                It's not happy with the chat ID, it appears. That's a pretty specific message. Where did you get it? Have you verified it?

                                Getting the chat ID can be a bit of work. Sometimes it's in the message you get when you set up in Bot Father, sometimes not. The config file template's comments give you some instructions and a link for how to get the chat ID.

                                        #
                                        # 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: "123456789"
                                

                                At the very least, I'd go through this process and confirm. Watch the case on the ending of the URL that you're asked to fetch. If it's incorrect, the API will give you a bogus empty-ish response rather than an error, which can be frustrating to figure out.

                                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
                                0
                                • toggledbitsT toggledbits

                                  No worries. Just trying to teach fishing rather than just handing the fish over...

                                  The last line of your log snippet:

                                  [latest-21342]2021-12-09T18:38:19.250Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
                                  

                                  It's not happy with the chat ID, it appears. That's a pretty specific message. Where did you get it? Have you verified it?

                                  Getting the chat ID can be a bit of work. Sometimes it's in the message you get when you set up in Bot Father, sometimes not. The config file template's comments give you some instructions and a link for how to get the chat ID.

                                          #
                                          # 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: "123456789"
                                  

                                  At the very least, I'd go through this process and confirm. Watch the case on the ending of the URL that you're asked to fetch. If it's incorrect, the API will give you a bogus empty-ish response rather than an error, which can be frustrating to figure out.

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

                                  @toggledbits Thank you for your patience!
                                  After two hours of digging, google searching and some trial and errors, I finally found why it didn't work...
                                  f5930c45-216e-4496-a030-88e4e0010ec5-image.png

                                  It's easier if the reactor is activated... 🙂 It do not work even in the editing menu, as long as it's not activated. This is strange, since I can activate a specific entity/step to try it out. But that was not the case with the notify function. All of my tries have been in the editing menu with the reaction not activated. Now it's working perfectly, and so are my other notify services. Have a great weekend!

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

                                    Well, it depends on which "try" button you use. The Entity Action "try" button, on the same row as the entity action itself, will run any time. But the "Try Reaction" button in the reaction's header... no... that requires the rule to be enabled. And that fact is logged (attempting to run a reaction in a disabled rule), by the way, so again, careful review of the logs can be very helpful.

                                    But... that resolution does not reconcile at all with the error message handed back from Telegram that you posted earlier. But if it's working for you now, I guess I won't go down that rabbit hole.

                                    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
                                    0
                                    • toggledbitsT toggledbits

                                      Well, it depends on which "try" button you use. The Entity Action "try" button, on the same row as the entity action itself, will run any time. But the "Try Reaction" button in the reaction's header... no... that requires the rule to be enabled. And that fact is logged (attempting to run a reaction in a disabled rule), by the way, so again, careful review of the logs can be very helpful.

                                      But... that resolution does not reconcile at all with the error message handed back from Telegram that you posted earlier. But if it's working for you now, I guess I won't go down that rabbit hole.

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

                                      @toggledbits No, I guess we shouldn't spend any more time trying to understand. It works and I'm delighted. I do appreciate that you try to teach us fishing instead of handing the fish. I always try for hours before I ask for assistence. That's the way to learn and grow. Take care!

                                      1 Reply Last reply
                                      1
                                      • toggledbitsT toggledbits locked this topic on
                                      Reply
                                      • Reply as topic
                                      Log in to reply
                                      • Oldest to Newest
                                      • Newest to Oldest
                                      • Most Votes


                                      Recent Topics

                                      • Oddness in Copy/Move of Reactions
                                        G
                                        gwp1
                                        0
                                        1
                                        18

                                      • [Solved] function isRuleEnabled() issue
                                        CrilleC
                                        Crille
                                        0
                                        4
                                        27

                                      • [Reactor] Problem with Global Reactions and groups
                                        therealdbT
                                        therealdb
                                        0
                                        3
                                        46

                                      • Possible feature request 2?
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        3
                                        40

                                      • Reactor (Multi-System/Multi-Hub) Announcements
                                        toggledbitsT
                                        toggledbits
                                        5
                                        133
                                        79.4k

                                      • Genuinely impressed with Zigbee and HA / Reactor
                                        CatmanV2C
                                        CatmanV2
                                        1
                                        9
                                        338

                                      • Copying a global reaction
                                        toggledbitsT
                                        toggledbits
                                        0
                                        3
                                        86

                                      • [HowTo] Using HABridge with Reactor
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        9
                                        401

                                      • [Reactor] Bug when sending MQTT boolean payloads
                                        toggledbitsT
                                        toggledbits
                                        0
                                        4
                                        141

                                      • Difficulty defining repeating annual period
                                        G
                                        gwp1
                                        0
                                        5
                                        106

                                      • Need help with sequence
                                        therealdbT
                                        therealdb
                                        0
                                        3
                                        64

                                      • Possible feature request?
                                        therealdbT
                                        therealdb
                                        0
                                        5
                                        169
                                      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