CMK version: 2.4.0p16 CEE
OS version: Appliance 1.7.14
Error message: HTTPError sending SMS: 422 Client Error: Unprocessable Entity for url: …
and
Error sending SMS: HTTPConnectionPool(host=‘192.168.1.1’, port=80): Read timed out. (read timeout=30.0)
It took me quite a while to be able to send an SMS at all. Now that it works, however, I regularly receive error messages from the sms_api.
Despite the messages, the SMS messages are reaching the recipient.
Message 1:
Error sending SMS: HTTPConnectionPool(host=‘192.168.1.1’, port=80): Read timed out. (read timeout=30.0)
Message 2:
HTTPError sending SMS: 422 Client Error: Unprocessable Entity for url: , b’<!doctype html>\n\n \n <meta\n name=“robots”\n content=“noindex”\n />\n <meta charset=“utf-8” / >\n <meta\n http-equiv=“X-UA-Compatible”\n content=“IE=edge”\n />\n <meta\n http-equiv= “Cache-Control”\n content=“no-cache, no-store, must-revalidate”\n />\n <meta\n name=“viewport”\n content=“width=device-width,initial-scale=1.0”\n />\n <link\n rel=“stylesheet”\n href=“/brand/colors.css?v=1”\ n />\n <link\n rel=“stylesheet”\n href=“/brand/tokens.css?v=1”\n />\n <link\n rel=“icon”\n href=“/favicon.ico”\n />\n \n \n \n <link rel=“modulepreload”
A test with my own script (Bash and Python) to send the messages has similar problems, and I thought it was due to the script. The script was only created because the text of the SMS cannot be customized with 2.4! ![]()
The login always seems to work, and I always find a token in my log, but sending the SMS triggers errors.
For example, from my log:
Login OK – Token received. – [2025-12-09 15:27:49] Router returned 422: {“success”:false,“errors”:[{“source”:“Message sending”,“code”:2,“error”:“Failed to send message”,‘section’:“send”}]}
What I noticed is that I almost only experience the errors during the day (approx. 6 a.m. to 10 p.m.), up to three or two out of 500 messages.
Could the LTE cell or something similar be overloaded and the TRB’s API be sensitive to this?