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?
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
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
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
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

CallMeBot new interface?

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 2 Posters 1.0k 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.
  • 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

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

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

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

                      • Set Reaction > Script Action
                        toggledbitsT
                        toggledbits
                        0
                        4
                        53

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

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

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

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

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

                      • Disaster recovery and virtualisation
                        CatmanV2C
                        CatmanV2
                        0
                        5
                        693

                      • Remote access of Zwave stick from Z-wave server
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        414
                      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