hello the community, since yesterday I’ve had strange behavior with my door sensor scenes, I receive the text messages a bit late then a few minutes, and now even the next day, I just tested a scene for a door sensor and I receive a text message from another one, it’s completely erratic, does anyone have the same issue or is it coming from the operator?
I also use Free’s SMS service and I don’t have this problem (SMS received this morning at the expected time).
Thanks for the reply, I’m still looking but I can’t find anything. I’m not receiving anything now even though I haven’t changed anything. I even installed Telegram and still nothing. I’m stuck here. For info, I used both the external and internal Free integration and changed the token as well, but still nothing.
If it’s the same with Telegram, then it’s probably an issue with your system or your scenes.
As it is, it’s hard to know. Could you share your Gladys logs, maybe we can see why with them?
Hi, I received a ton of text messages last night and during the night with a delay of several hours…
And I’m still receiving text messages even though I’ve stopped all my scenes…
My scenes have always worked and I haven’t touched anything, I’m sending my logs
2026-09-10T06:41:03.327773230Z 2026-09-10T08:41:03+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:03.652996247Z 2026-09-10T08:41:03+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:03.980811910Z 2026-09-10T08:41:03+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:04.307539108Z 2026-09-10T08:41:04+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:04.672716317Z 2026-09-10T08:41:04+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:04.998623686Z 2026-09-10T08:41:04+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:05.324536385Z 2026-09-10T08:41:05+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:05.649636603Z 2026-09-10T08:41:05+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:05.976338191Z 2026-09-10T08:41:05+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:06.300050004Z 2026-09-10T08:41:06+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:06.625164060Z 2026-09-10T08:41:06+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:06.954711298Z 2026-09-10T08:41:06+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:07.283891614Z 2026-09-10T08:41:07+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:07.649947638Z 2026-09-10T08:41:07+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:07.975397640Z 2026-09-10T08:41:07+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 401 Unauthorized
2026-09-10T06:41:08.172271918Z 2026-09-10T08:41:08+0200 <info> connect.js:76 (MqttClient.<anonymous>) Attempting to reconnect to MQTT broker...
2026-09-10T06:41:08.174922008Z 2026-09-10T08:41:08+0200 <warn> connect.js:80 (MqttClient.<anonymous>) Error while connecting to MQTT
2026-09-10T06:41:08.175589736Z 2026-09-10T08:41:08+0200 <warn> connect.js:81 (MqttClient.<anonymous>) Error: connect ECONNREFUSED 127.0.0.1:1883
2026-09-10T06:41:08.175630579Z at TCPConnectWrap.afterConnect [as oncomplete] (node:net:2017:16) {
2026-09-10T06:41:08.175639291Z errno: -111,
2026-09-10T06:41:08.175645270Z code: 'ECONNREFUSED',
2026-09-10T06:41:08.175651239Z syscall: 'connect',
2026-09-10T06:41:08.175656530Z address: '12
Is the integration for Telegram properly configured? Because the logs show connection errors.
Same with MQTT!
Nothing on the Free Mobile side.
thanks for the reply, I stopped using telegram I’m using ntfy temporarily, as for free now I no longer receive any sms, there really is a problem but I don’t know where.
My scenes are good, and anyway I haven’t touched anything everything was working before.
how can you see in the logs if an sms is taken into account?
Gladys and the integration don’t do much, they just send an HTTP request to Free.
Also give me the Free Mobile integration logs to see if there’s an error, but there’s no line to confirm a send.
[2026-09-11T07:32:50.982Z] [WARN] [gladys-sdk] connection to Gladys lost (close code 1006)
[2026-09-11T07:32:50.983Z] [WARN] [gladys-sdk] not connected to Gladys (ws://172.30.0.1:80), retrying in 1000 ms (attempt 1)
[2026-09-11T07:32:50.992Z] [INFO] Received SIGTERM -> graceful shutdown
[2026-09-11T07:32:51.398Z] [INFO] Starting the Free Mobile integration...
[2026-09-11T07:32:51.533Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-09-11T07:32:59.979Z] [INFO] onSendMessage -> delivering an SMS to Free Mobile 23
[2026-09-11T07:39:24.469Z] [INFO] onSendMessage -> delivering an SMS to Free Mobile 23
[2026-09-11T07:39:59.271Z] [INFO] onSendMessage -> delivering an SMS to Free Mobile 23
Here are the last lines, it seems to be working fine on Gladys' side, it must be Free that's bugging. I checked my phone to see if the number isn't blacklisted, but no. In the meantime, I'll continue with ntfy. It's still strange though!Well, I just checked on the Free website. When I enter the command line provided in HTTPS, I get an access denied error 403, despite having the correct API code and identifier. Nothing works.
well I’m answering myself, after 1 hour of trying, I ended up disabling the service and reactivating it, I got a new key and bingo weirdly it works again, when I had done the manipulation twice yesterday and nothing?
So maybe a misunderstood API key or a Free bug???