TRB140 Probleme

Global Community Deutsch
, ,
1

**CMK version: 2.3.0p34 **
OS version: Debian 12

Error message: Probleme mit TRB140

Hallo,

ich bekomme das SMS-Gateway TRB140 nicht mehr ans Laufen. (Es war schon seit längeren nicht mehr in Betrieb und ich wollte es wieder reaktivieren.)

Firmware des TRB140: TRB1_R_00.07.15.2

Es scheint so, als greift CheckMK auf falsche API-Endpunkte zu? Ausgabe der failed notifications:

Error Status: 200 Details: b'<!doctype html>\n<html lang="en">\n <head>\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/brand.css?v=2"\n />\n <link\n rel="icon"\n href="/favicon.ico"\n />\n <title></title>\n <script type="module" crossorigin src="/assets/index-2025-06-25-60fec960fcd.js"></script>\n <link rel="modulepreload" crossorigin href="/assets/index-2025-06-25-60fec960fcd.js">\n <link rel="modulepreload" crossorigin href="/assets/vendor-2025-06-25-60fec960fcd.js">\n <link rel="stylesheet" crossorigin href="/assets/style-2025-06-25-60fec960fcd.css">\n </head>\n <body>

http://Router-IP/cgi-bin/sms_send → gibt es nicht mehr

Siehe:
https://developers.teltonika-networks.com/

Zudem habe ich das Gefühl, dass “Disable SSL certificate verification” nicht mehr beachtet wird. Sobald ich HTTPS auf dem Router aktiviere, gibt CheckMK einen SSLCertVerificationError aus. Erst wenn ich HTTPS deaktviere (System → Access Control → HTTPS), habe ich keine Zertifikatsfehler mehr, weil es dann über HTTP läuft.

Hat jemand ähnliche Probleme oder kann unterstützen? Danke!

2

Although the Tektonika TRB-140 is currently the only device listed in the “SMS (using the modern API)” notification method it is far from capable to be used with Checkmk.

It is only able to send one SMS per second and has no internal spooling. This means it will lose messages when Checkmk generates too many notifications at once.

You should replace it with a better SMS modem.

3

Thank you for your feedback.

After downgrading to firmware version 7.13.4, SMS dispatch is working again.
It would be great if this functionality could also be ensured in future versions of the Teltonika firmware.

Do you have a recommendation for an SMS modem suitable for 5 to 10 users?

4

Any system that has a builtin spooler and can handle multiple SMS requests in parallel.

I do not know the latest firmware of the TRB-140, maybe they implemented a spooler now?

5

Since Version TRB1_R_00.07.14 (2025.04.24) https://wiki.teltonika-networks.com/view/TRB140_Firmware_Downloads#Changelog of the Teltonika TRB140 the POST/GET package is removed.

image

So the communication does not work anymore with checkmk :cry:

I am now looking for alternative Push Notification Services:

Benachrichtigungen per Pushover (notifications)

6

We are currently working on a fix to support the API endpoint.
Only problem i have is finding a documentation about what permissions are needed. Right now i’m only able to send via a user by granting full write access

1 Like
8

Ah thaks for the fast reply.

Is there a timeline for the fix / new integration?

Where can I find or activate the API on my Teltonika 140?:sweat_smile:

9

We try to get this out as fast as possible. Only thing that’s missing is the permission problem i mentioned.

Where can I find or activate the API on my Teltonika 140?

it’s used by default since firmware version 7.14, the old endpoints are removed

Current workaround would be to downgrade the firmware to 7.12

10

Thanks,
for now I have downgraded my Teltonika TRB140 to 7.12

11

Version 7.13.4 is also working – it’s the release just before TRB1_R_00.07.14.

12

yes, i skipped it because 7.13 has a download warning.
7.13.4 should also be fine

13

:thinking: Since 2.4.0p9 api calling has changed. I am currently testing the new setup…

Werk #18076: SMS (using modem API): Use new API endpoint for TRB140 if needed

14

I have updated the checkmk Server to 2.4.0p9 and my Teltonika TRB140 to version TRB1_R_00.07.17.4

Now the communication between checkmk and Teltonika TRB140 is working again :tada: