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. CallMeBot new interface?
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
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
Custom capabilities in MQTT templates
M
Hi, I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far. But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter. So this is what I have in the local_mqtt_devices.yaml capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int And this is the template: templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json So the speak action should send something like this to topic sonos/cmd/speak { "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" } At startup the MSR seems to be quite unhappy with my configuration: reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction. Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable. br, mgvra MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Multi-System Reactor
[SOLVED]Hass websocket falsely reporting ready on boot??
V
Hi, @toggledbits I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting. Here is the sequence of the test case (All time converted to Zulu to match logs): Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error. Here is what I see from the log: 14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready. Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...). Questions: Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas? Here is the log: OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
Multi-System Reactor

CallMeBot new interface?

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 2 Posters 985 Views 2 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.
  • wmarcolinW Offline
    wmarcolinW Offline
    wmarcolin
    wrote on last edited by
    #1

    Hi @toggledbits

    Apparently, there have been some changes to the CallMeBot interface, as the service recently stopped working for me. I've tried several configurations, and none of the ones below are working.

      # CallMeBot
      CallMeBot:
        profiles:
          default:
            # description - A friendly description of this profile (for menus)
            description: Default Profile New
            #
            # api_url - Access URL for CallMeBot API being used
            api_url: http://api.callmebot.com/start.php
            #
            # api_key - (if needed) API key (use for Facebook API, WhatsApp API, etc.).
            #           If the API you are using does not require it, leave it
            #           commented out or blank.
            api_key: "177xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTGk"
            #
            # source - (if needed) Source field for some APIs. If yours does not require
            #          it, leave it commented out or blank.
            #source: "source-value"
            #
            # phone - (if needed) Phone field for some APIs. If yours does not require
            #         it, leave it commented out or blank.
            phone: "+5xxxxxxxx33"
            #
            # user - (if needed) User field for some APIs. If yours does not require
            #        it, leave it commented out or blank.
            #user: "@xxxxxxxxxxxxx"
            #
            # lang - (optional) Language/voice; default "en-US-Standard-C".
            #        See CallMeBot docs for possible values.
            lang: "en-US-Standard-C"
            #
            # rpt - (optional) Number of times to repeat message; default: 1.
            rpt: 2
    

    I have already tested using the phone or the user.

    Looking at the action log, I see that it starts, runs and finishes without any problems.

    [latest-23302]2023-11-05T14:35:54.106Z <Engine:INFO> Enqueueing "teste<SET>" (rule-lolk0nlj:S)
    [latest-23302]2023-11-05T14:35:54.108Z <Engine:NOTICE> Starting reaction teste<SET> (rule-lolk0nlj:S)
    [latest-23302]2023-11-05T14:35:54.111Z <Engine:INFO> teste<SET> all actions completed.
    

    When testing directly on the site, I see that it no longer uses API, and I haven't even found where to generate the API KEY.

    http://api.callmebot.com/start.php?source=web&user=+5xxxxxxxx33&text=Teste callmebot pelo numero novo&lang=en-US-Standard-C
    

    Please, can you advise me on what I should do to solve the problem?

    Thanks.

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

      What's your target messaging client? That's important, since CallMeBot can contact several and the API URL and parameters are different for each.

      The CallMeBot web site has instructions for each client. That will tell you the correct URL and parameters to use.

      I only use Telegram, and I just tested both Text and Voice with Telegram and it works fine.

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

      wmarcolinW 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        What's your target messaging client? That's important, since CallMeBot can contact several and the API URL and parameters are different for each.

        The CallMeBot web site has instructions for each client. That will tell you the correct URL and parameters to use.

        I only use Telegram, and I just tested both Text and Voice with Telegram and it works fine.

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

        @toggledbits hi!

        I used CallMeBot normally until I changed my phone number, and then I looked up where to generate the new API KEY, and I couldn't find it. So I chose to use the phone number only, and it didn't work. If I execute the command via HTTP on the MSR, it works perfectly. Strange as I said, there is no error message in the logs.

        Now you mention voice in Telegram, I didn't know about that. Do you have any recommended material or examples of how to use it?

        Thank you.

        toggledbitsT 1 Reply Last reply
        0
        • wmarcolinW wmarcolin

          @toggledbits hi!

          I used CallMeBot normally until I changed my phone number, and then I looked up where to generate the new API KEY, and I couldn't find it. So I chose to use the phone number only, and it didn't work. If I execute the command via HTTP on the MSR, it works perfectly. Strange as I said, there is no error message in the logs.

          Now you mention voice in Telegram, I didn't know about that. Do you have any recommended material or examples of how to use it?

          Thank you.

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

          @wmarcolin Here's my profile for using Telegram Voice API with the CallMeBot notifier in Reactor:

            CallMeBot:
              profiles:
                default:
                  # default profile details redacted, not important here
                telegram_voice:
                  api_url: http://api.callmebot.com/start.php
                  user: "@username"
          

          Here's my action:

          4db4afa4-5309-4b7b-a1e2-ae38be49752e-image.png

          If you read their documentation (recommended), it says you need to authorize your user to receive messages that way (same is true of text, and I imagine, most other modes now, which may be your real problem). There's a link in the instructions to grant that authorization.

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

          wmarcolinW 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            @wmarcolin Here's my profile for using Telegram Voice API with the CallMeBot notifier in Reactor:

              CallMeBot:
                profiles:
                  default:
                    # default profile details redacted, not important here
                  telegram_voice:
                    api_url: http://api.callmebot.com/start.php
                    user: "@username"
            

            Here's my action:

            4db4afa4-5309-4b7b-a1e2-ae38be49752e-image.png

            If you read their documentation (recommended), it says you need to authorize your user to receive messages that way (same is true of text, and I imagine, most other modes now, which may be your real problem). There's a link in the instructions to grant that authorization.

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

            @toggledbits

            I still can't understand what's going on, in theory I'm following everything that the manual says, but for some reason when I change the phone number, @username no longer works, test calling http directly or even the CallMeBot test site doesn't work.

            However, if I use the phone number, test it by calling the CallMeBot test site, or use this routine in MSR, it works perfectly.

            b0b5b925-a38f-4889-bffb-84f74890886f-image.png

            Direct nagigator:

            http://api.callmebot.com/start.php?source=web&user=+507XXXXXXXX&text=teste pela api&lang=en-US-Standard-B
            

            The MSR configuration is the one you mentioned, which I have below, but instead of user I have phone

              # CallMeBot
              CallMeBot:
                profiles:
                  default:
                    # description - A friendly description of this profile (for menus)
                    description: Default Profile
                    #
                    # api_url - Access URL for CallMeBot API being used
                    api_url: http://api.callmebot.com/start.php
                    #
                    # phone - (if needed) Phone field for some APIs. If yours does not require
                    #         it, leave it commented out or blank.
                    phone: "+507XXXXXXXX"
            

            And in this situation it doesn't work.

            As I mentioned by user, there's something blocking it from working, no matter if it's through the CallMeBot website, direct http or MSR. In the case of using a phone number, it works via the CallMeBot website, it works via http calling directly in the browser or via the routine I put in the MSR. However, using MSR Notification with the above configuration doesn't work.

            Could @toggledbits check if the call is in this structure?

            http://api.callmebot.com/start.php?source=web&user=<+phone>&text=<text>&lang=en-US-Standard-B
            

            Another rare occurrence is that no logs are being generated in reactor.log.

            Thanks.

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

              Add this to your logging.yaml file and restart Reactor. Then test and see what URL is being generated/queried.

              logging: # don't include this line, it's just for indenting reference
                NotifyCallMeBot:
                  level: 5
              

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

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

                Hi @toggledbits

                First, thank you for your guidance, and see below for the log I've obtained.

                [latest-23302]2023-11-15T14:27:47.501Z <NotifyCallMeBot:5:NotifyCallMeBot.js:108> [NotifyCallMeBot]NotifyCallMeBot requesting http://api.callmebot.com/start.php?text=novo%20teste%20para%20numero%20do%20telefone&phone=%2B507xxxxxx33&lang=en-US-Standard-C
                [latest-23302]2023-11-15T14:27:48.125Z <NotifyCallMeBot:5:NotifyCallMeBot.js:117> [NotifyCallMeBot]NotifyCallMeBot success 200 OK
                

                If I compare the calls made in MSR with the ones I make directly, there are small differences. The point is that the MSR one isn't working and the direct one is.

                MSR NOTIFY CALLMEBOT

                http://api.callmebot.com/start.php?text=NEW%20TEST%20NOTIFY&phone=%2B507xxxxxx33&lang=en-US-Standard-C
                

                DIRECT SITE

                http://api.callmebot.com/start.php?source=web&user=+507xxxxxx33&text=NEW%20TEST%20NOTIFY&lang=en-US-Standard-C
                
                

                What I'm checking is that if I configure the phone in this way:

                    phone: +507xxxxxx33
                

                the call appears like this - no + in front the number

                   &phone=507xxxxxx33&
                

                if I configure it like this

                    phone: "+507xxxxxx33"
                

                the call looks like this - between hasps - I have the %2B

                   &phone=%2B507xxxxxx33&
                

                When I use the direct browser call

                http://api.callmebot.com/start.php?text=NEW%20TEST%20NOTIFY%205&source=web&phone=%2B507xxxxxx33&lang=en-US-Standard-C&rpt=2
                

                Back

                943b60a8-0eef-4f83-97fa-9fb1c094c234-image.png

                Than I change phone to user and add +, work:

                http://api.callmebot.com/start.php?text=NEW%20TEST%20NOTIFY%205&source=web&user=+507xxxxxx33&lang=en-US-Standard-C&rpt=2
                

                What I don't understand is that in all the tests, the log always comes back successful.

                [latest-23302]2023-11-15T14:57:42.938Z <NotifyCallMeBot:5:NotifyCallMeBot.js:117> [NotifyCallMeBot]NotifyCallMeBot success 200 OK
                

                At the end of the day, if I try to use my @wilxxxxxin username, the call is linked to my old phone, even though I've already changed it on Telegram. In this case, I've already sent a mail to CallMeBot support with no reply for over a week.

                Using the phone, which is authorized, the direct call works in the browser or using HTTP in MSR, if I use the Notify feature it doesn't work.

                And what bothers me the most is that I understand that anyone who places a call in a browser with my phone number will be made, because there is no API KEY to limit use.

                Well, if you have any more ideas to help me, I'd appreciate it.

                toggledbitsT 1 Reply Last reply
                0
                • wmarcolinW wmarcolin

                  Hi @toggledbits

                  First, thank you for your guidance, and see below for the log I've obtained.

                  [latest-23302]2023-11-15T14:27:47.501Z <NotifyCallMeBot:5:NotifyCallMeBot.js:108> [NotifyCallMeBot]NotifyCallMeBot requesting http://api.callmebot.com/start.php?text=novo%20teste%20para%20numero%20do%20telefone&phone=%2B507xxxxxx33&lang=en-US-Standard-C
                  [latest-23302]2023-11-15T14:27:48.125Z <NotifyCallMeBot:5:NotifyCallMeBot.js:117> [NotifyCallMeBot]NotifyCallMeBot success 200 OK
                  

                  If I compare the calls made in MSR with the ones I make directly, there are small differences. The point is that the MSR one isn't working and the direct one is.

                  MSR NOTIFY CALLMEBOT

                  http://api.callmebot.com/start.php?text=NEW%20TEST%20NOTIFY&phone=%2B507xxxxxx33&lang=en-US-Standard-C
                  

                  DIRECT SITE

                  http://api.callmebot.com/start.php?source=web&user=+507xxxxxx33&text=NEW%20TEST%20NOTIFY&lang=en-US-Standard-C
                  
                  

                  What I'm checking is that if I configure the phone in this way:

                      phone: +507xxxxxx33
                  

                  the call appears like this - no + in front the number

                     &phone=507xxxxxx33&
                  

                  if I configure it like this

                      phone: "+507xxxxxx33"
                  

                  the call looks like this - between hasps - I have the %2B

                     &phone=%2B507xxxxxx33&
                  

                  When I use the direct browser call

                  http://api.callmebot.com/start.php?text=NEW%20TEST%20NOTIFY%205&source=web&phone=%2B507xxxxxx33&lang=en-US-Standard-C&rpt=2
                  

                  Back

                  943b60a8-0eef-4f83-97fa-9fb1c094c234-image.png

                  Than I change phone to user and add +, work:

                  http://api.callmebot.com/start.php?text=NEW%20TEST%20NOTIFY%205&source=web&user=+507xxxxxx33&lang=en-US-Standard-C&rpt=2
                  

                  What I don't understand is that in all the tests, the log always comes back successful.

                  [latest-23302]2023-11-15T14:57:42.938Z <NotifyCallMeBot:5:NotifyCallMeBot.js:117> [NotifyCallMeBot]NotifyCallMeBot success 200 OK
                  

                  At the end of the day, if I try to use my @wilxxxxxin username, the call is linked to my old phone, even though I've already changed it on Telegram. In this case, I've already sent a mail to CallMeBot support with no reply for over a week.

                  Using the phone, which is authorized, the direct call works in the browser or using HTTP in MSR, if I use the Notify feature it doesn't work.

                  And what bothers me the most is that I understand that anyone who places a call in a browser with my phone number will be made, because there is no API KEY to limit use.

                  Well, if you have any more ideas to help me, I'd appreciate it.

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

                  @wmarcolin said in CallMeBot new interface?:

                  MSR NOTIFY CALLMEBOT

                  http://api.callmebot.com/start.php?text=NEW TEST NOTIFY&phone=%2B507xxxxxx33&lang=en-

                  This is showing that you haven't configured the user field, which it seems you must do or the call will not work. Your direct site version of the URL shows a user field and is working. The error message you get back is telling you as much, and yet you seem focused on the phone field.

                  The difference in the phone field between the first two calls is probably not relevant, as the + must be URL-encoded when making the request to the server, and + encodes as %2B. Reactor is showing the final encoded URL, and the web interface is likely not. If the plus is left un-encoded, it actually reads as a space character to the server (URL encoding translates spaces to either + or %20); I'm sure it's not meant to be a space, but a literal plus, and as such, it must be %2B when finally sent to the server.

                  What I don't understand is that in all the tests, the log always comes back successful.

                  "Successful" means that the server was connected and the request made, and the server did not respond with an error. While the content of the response may or may not indicate an error, what matters is the server's response code. Their server hands back a 200 (OK status) but the content of the response body is an error message, and that's a defect of their server (which I'm not going to address). They should return a 400-series error if the parameters of the request are incorrect, but they don't.

                  And what bothers me the most is that I understand that anyone who places a call in a browser with my phone number will be made, because there is no API KEY to limit use.

                  This is another big defect in the changes they've made recently, and a good reason not to use this interface. It's alarming, in fact. Honestly, I'm not spending a lot more time on it, because it doesn't seem to be in wide use, you've found a structure that works, and there's a workaround available (making the call using an HTTP Request action).

                  Really, with their recent changes, the NotifyCallMeBot interface is little more than a pass-through HTTP request that is actually made more difficult by the interface trying to "simplify" handling of the parameters as configuration, especially in their evolving API. I may deprecate this interface, for all these reasons.

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

                    Thank you very much for your explanation. I've tried several ways to configure the phone number or user, without success, but as you say, I think this tool should really be abandoned.

                    I understand that it's good, because we often don't pay attention to messages, and a phone call is much more useful.

                    But this change to making calls without an API KEY is really bad, and your decision is totally reasonable.

                    Thanks.

                    1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      Add this to your logging.yaml file and restart Reactor. Then test and see what URL is being generated/queried.

                      logging: # don't include this line, it's just for indenting reference
                        NotifyCallMeBot:
                          level: 5
                      
                      wmarcolinW Offline
                      wmarcolinW Offline
                      wmarcolin
                      wrote on last edited by
                      #10

                      Hi @toggledbits

                      Sorry for using this post, but by giving this instruction, you helped me a lot to find the error.

                      Is there a way to configure logging.yaml to generate specific files for event types? For example, a file to store only logs that are ERR, another file to have Rule:INFO, or Rule:NOTICE?

                      I don't want to do without the general file, but if I could create some especially to only show ERR, it could make it easier to maintain the system on a recurring basis.

                      Any recommendations?

                      Thanks.

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

                        Yeah, would have preferred a new thread for this question.

                        See the Troubleshooting section of the manual.

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


                        Recent Topics

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

                        • Reactor (Multi-System/Multi-Hub) Announcements
                          toggledbitsT
                          toggledbits
                          5
                          121
                          35.2k

                        • Disaster recovery and virtualisation
                          CatmanV2C
                          CatmanV2
                          0
                          5
                          601

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

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

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

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

                        • Need help reducing false positive notifications
                          T
                          tamorgen
                          0
                          7
                          471

                        • Deleting widgets
                          toggledbitsT
                          toggledbits
                          0
                          4
                          445

                        • MQTT configuration question
                          tunnusT
                          tunnus
                          0
                          11
                          599
                        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