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?
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

Is Telegram working?

Scheduled Pinned Locked Moved Multi-System Reactor
27 Posts 5 Posters 1.7k 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.1.151
                            *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                            *HASS 2025.3.4
                            w/ ZST10-700 fw 7.18.3

                            *Prod MSR in docker/portainer
                            MSR: latest-25082-3c348de6
                            MQTTController: 24257
                            ZWave Controller: 25082

                            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

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

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

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

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

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

                                      • Disaster recovery and virtualisation
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        5
                                        682

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

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

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

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

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