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?
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
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

Is Telegram working?

Scheduled Pinned Locked Moved Multi-System Reactor
27 Posts 5 Posters 2.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 Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #2

    The bug (that is fixed and there is an announced update to the docker images with that fix) was simply that choosing the default format (parse mode) and notification were causing the UI to flag the fields as missing (they were not marked optional, so the UI assumes required). You can either update the docker image (if you are using docker), or just choose non-default/from-profile values in those drop-downs for testing.

    Other than the UI glitch, I haven't heard of any issues.

    I'll be spinning a new release today.

    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 Offline
      wmarcolinW Offline
      wmarcolin
      wrote on last edited by toggledbits
      #3

      I am using normal Telegram since it was released, with the HTML and Markdown format settings.

      I share below the configuration that I have if it helps in something.

      # Telegram
        Telegram:
          profiles:
            default:
              # description - A friendly description of this profile (for menus)
              description: Default Family
              #
              # 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: "17______83:AAX____________________dBleUXslGTGk"
              #
              # 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: "-58_____24"
              #
              # 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 - 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: "17______83:AAER_UN_______________________lGTGk"
              #
              # 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: "154_____34"
              #
              # 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
      • cw-kidC Offline
        cw-kidC Offline
        cw-kid
        wrote on last edited by cw-kid
        #4

        Yes my notification.yaml file looks the same as above apart from I am not using HTML I left it blank for plain text.

        I have created a Global Reaction as a test with a notify for Telegram. It's still not working. I've also updated to the very latest version of MSR that fixes those two fields being required vs optional.

        This is what I see in the log file. They are not my real bot and chat ID's I have changed them.

        
        2021-06-18T11:50:50.594Z <Engine:5:Engine.js:953> Engine#1 enqueued reaction re-kq29nxzw as 43
        2021-06-18T11:50:50.595Z <Engine:5:Engine.js:1108> _process_reaction_queue() wake-up!
        2021-06-18T11:50:50.599Z <Engine:5:Engine.js:1069> _process_reaction_queue() running task 43 { "tid": 43, "id": "re-kq29nxzw", "rule": --undef--, "__reaction": GlobalReaction#re-kq29nxzw, "next_step": 0, "status": 0, "ts": 1624017050481, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
        2021-06-18T11:50:50.599Z <Engine:NOTICE> Starting reaction Test Telegram (re-kq29nxzw)
        2021-06-18T11:50:50.600Z <Engine:5:Engine.js:1216> Engine#1 reaction re-kq29nxzw step 0 notify Telegram with { "message": "This is a TEST", "profile": "default" }
        2021-06-18T11:50:50.601Z <Engine:5:NotifyTelegram.js:159> NotifyTelegram sending profile default notification request: This is a TEST
        2021-06-18T11:50:50.604Z <Engine:INFO> Test Telegram all actions completed.
        2021-06-18T11:50:50.605Z <Engine:5:Engine.js:1073> _process_reaction_queue() task returned, new status -1; task 43
        2021-06-18T11:50:50.608Z <Engine:5:Engine.js:1108> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
        2021-06-18T11:50:50.697Z <Engine:ERR> NotifyTelegram failure response from endpoint: 404 Not Found
        2021-06-18T11:50:50.699Z <Engine:ERR> NotifyTelegram fres=[object Response]
        2021-06-18T11:50:50.700Z <Engine:INFO> NotifyTelegram request URL: https://api.telegram.org/botBBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage
        2021-06-18T11:50:50.701Z <Engine:INFO> NotifyTelegram request body: {"text":"This is a TEST","chat_id":"314603256"}
        2021-06-18T11:50:50.702Z <Engine:ERR> NotifyTelegram request to https://api.telegram.org/botBBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage failed: Error: NotifyTelegram request failed
        2021-06-18T11:50:50.703Z <Engine:ERR> Engine#1 reaction re-kq29nxzw step 0 notification (Telegram) failed: Error: NotifyTelegram request failed
        

        My raw HTTPS url's that I am currently using, the bot ID has an extra part at the beginning.

        For example like this:

        https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN
        

        Where as in the MSR log its removed the "2188872596:" part and just shows this:

        https://api.telegram.org/botBBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN
        

        Which results in the 404 error etc.

        Thanks

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

          Did you include it in the config?

          Edit: clarifying, by "it" I mean the number (bot ID) before the colon (and the colon). The bot_token value in the config should be on the form nnnnnn:mixedlongstring. The object literally copies the entire bot_token string onto the end of the URL; there's not filtering or editing of any kind, so your log post suggests it's not there.

          Did you enclose it in quotes?

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

          cw-kidC 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Did you include it in the config?

            Edit: clarifying, by "it" I mean the number (bot ID) before the colon (and the colon). The bot_token value in the config should be on the form nnnnnn:mixedlongstring. The object literally copies the entire bot_token string onto the end of the URL; there's not filtering or editing of any kind, so your log post suggests it's not there.

            Did you enclose it in quotes?

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

            @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 1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #7

              You're now getting a 400, not a 404. That likely means that the chat ID is invalid. Is the bot a member of that chat?

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

              cw-kidC 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                You're now getting a 400, not a 404. That likely means that the chat ID is invalid. Is the bot a member of that chat?

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

                @toggledbits

                Oh yes sorry 400 not 404.

                Chat ID is correct and yes I think it must be a member. Because I am using the same bot ID and the same chat ID in a raw HTTPS command and the notifications work and go to my "Vera Group" aka my chat ID.

                This is the type of HTTPS command I've been using previously:

                https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage?chat_id=-314603256&text=This is a test
                
                1 Reply Last reply
                0
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #9

                  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.

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

                  cw-kidC wmarcolinW 2 Replies 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.

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


                                          Recent Topics

                                          • Gradually turn on lights.
                                            G
                                            gwp1
                                            0
                                            4
                                            93

                                          • Stop the MSR by an external switch on Hubitat.
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            1
                                            15

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            83

                                          • Reset attribute value of entity in event handler
                                            R
                                            RHCPNG
                                            0
                                            5
                                            167

                                          • Need help figuring out how to delay a reset on reaction
                                            G
                                            gwp1
                                            0
                                            22
                                            856

                                          • Way to search for rules (rule state) in other rules
                                            T
                                            tamorgen
                                            0
                                            3
                                            90

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            77

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            416

                                          • Wiring Samotech SM308-S into light fitting
                                            akbooerA
                                            akbooer
                                            0
                                            2
                                            136

                                          • Errors after updating to MQTTController build 25139
                                            toggledbitsT
                                            toggledbits
                                            0
                                            6
                                            232

                                          • 🎉 My very first MSR controller: OpenSprinkler
                                            therealdbT
                                            therealdb
                                            5
                                            13
                                            898

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            246
                                          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