Rsudp json errors? no telegram messages

Technical Support
1

Using the online instructions, I created a telegram bot and configured the json to send alert messages. I’ve done this on two machines - a Pi 5 and OSX Sequoia. I can send messages to the bot from the iPhone telegram app.

One json is configured to use the chat id from https://api.telegram.org//getUpdates, and the other uses my telegram user name @UserID.

The rsudp log files from both machines show no errors, looking like this:
2025-01-23 21:44:21 [Telegram id 6860072171] Telegram message: (Raspberry Shake station AM.R025E - region: Utah) Event detected at 2025-01-23 21:44:21.09 UTC - live feed Station View: Raspberry Shake Network & EQ Activity Map

I do see a warning from the terminal session where the client was started:
2025-01-23 21:44:21 [Telegram id 6860072171] Telegram message: (Raspberry Shake station AM.R025E - region: Utah) Event detected at 2025-01-23 21:44:21.09 UTC - live feed Station View: Raspberry Shake Network & EQ Activity Map
/Users/miniconda3/envs/rsudp/lib/python3.12/site-packages/rsudp/c_telegram.py:165: RuntimeWarning: coroutine ‘Bot.send_message’ was never awaited
self._when_alarm(d)

My json telegram config:
“telegram”: {
“enabled”: true,
“send_images”: true,
“token”: “”,
“chat_id”: “”,
“extra_text”: “”
},

Guidance welcomed!

I’ll be happy to provide more detail or full files…

Kevin

2

Note: I had place holders for the getUpdates, token, and chat_id. Apparently the use of angle brackets caused 'em to vanish. Lesson learned…

3

Hello NotSrirred,

It would be difficult for me to try and replicate this, as I don’t have a Pi5 available. I have the Telegram module enabled on my Pi3 and I am not seeing these messages.

This error is probably due to the different architecture of the Pi5 compared to the older models. The quickest thing you can do is open a new issue in the GitHub RSUDP repo (GitHub · Where software is built) so that our collaborator can look at it.

Attach all files you deem relevant (and the logs you showed here). And thank you for notifying us about this.