Domoticz

Hi Domoticz Forum,

I'm struggling to figure out why my Telegram function not working any more, any one out there experienced the same issue??

My notification function stopped working in the beginning of July, no changes done for the Telegram config.

Telegram ENABLED
API Key correct
Chat ID correct

Has work flawlwess before
Pushing the test button NO Messages arrives in my Telegram APP.

Verifying connectivity from the Raspberry PI i can send Telegram messages from a browser using an https test string using the same API and Chat ID and it arrives correct to the Telegram app.

Also tried another Telegram API key but no success.

Version: 2025.1
Platform: Raspbian GNU/Linux 10 (buster)
Plugin/Hardware: Rapberry PI 3
Description: Telegram issue

Best regards
Peter

For me Telegram still works with my 2025.1 stable. Pressing the Test button triggers a test message in Telegram.

Okay thanks fort the reply the Telegram function in my version isn't broken then.
Is there some other dependencies that must be fulfilled? Like public IP? Firewall rules?

I did become aware of this Telegram issue after we had to change our ISP, the main difference now is that the new ISP will not supply me with an public IP. I'm not sure if that could be an issue for the Domoticz Telegram function?

I also tried to connect my RPI to a different router over 4G but same result.

I also tried to debug using Wireshark if there where some issue showing up there. Hard to find any error that could explain what's all about.

The log from Domoticz is showing this...and it's not happy about something

2025-09-19 12:28:56.259 Status: Notification: Domoticz test
2025-09-19 12:29:06.288 Error: Telegram:
2025-09-19 12:29:06.288 Notification sent (telegram) => Failed
2025-09-19 12:29:06.299 Active notification Subsystems: browser, telegram (2/13)

Any idea what to look for? More logfiles to look into??

/Peter

Try this command From browser

Do you not get any public IP? or not a fixed?
I get a new IP every day, no issues with that.
If the https telegram commands are working it could only be an issue with the RPI where Domoticz is running on?
Dou you have your own firewall installed?
You could try to run the command with curl from a terminal session from the Domoticz server.

habahabahaba wrote: Friday 19 September 2025 13:18 Try this command

Code: Select all

https://api.telegram.org/bot<YOUR_BOT_NUMBER>/getUpdates

From browser

I have now tried that and the result seems to bee okay.
{"ok":true,"result":[]}

Sending a Telegram msg from browser with my bot<MY_BOT_NUMBER> works as it should. If that is a connectivity test so why isn't working from Domoticz test bottom. Same API Key and Chat ID. Very strange.

And what is the result when using curl from the commandline of your rpi you are running domoticz on?

jvdz wrote: Monday 22 September 2025 15:43 And what is the result when using curl from the commandline of your rpi you are running domoticz on?

"curl" cmd gives the same result. Note sure what this means. The result is "Nothing" ??

{"ok":true,"result":[]}

Result is fine for getupdates as that only returns the untead messages.
It also means that things should work from your rpi.
Are you sure you filled the bot info correctly in the domoticz-telegram setup ?

jvdz wrote: Monday 22 September 2025 20:35 Result is fine for getupdates as that only returns the untead messages.
It also means that things should work from your rpi.
Are you sure you filled the bot info correctly in the domoticz-telegram setup ?

Thank's for the reply and verfication of the Bot function.

I wrote before that I can verify the API key and Chat ID from a browser window with a send string and then I recieve a correct Telegram Msg using the same API key and Chat ID that i use in Domoticz.

Further up in my case you can see the error msg in Domoticz log.
Dosn't tell me what's not working, any suggestions what to test or look into another log ??

Any OS updates installed may be?

Domoticz in docker?

Finally I figured out that all of this trouble was a DNS issue. I tried Google DNS 8.8.8.8 but it didn't solve the issue, but when I configured the RASPPI to use the ISP supplied DNS servers it all started to works at it should. The strange part is that normal web browsing and all other stuff was working but not the Telgram url. Try and error way to solve things
Thank's for all help along the way.
/Peter