-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Telegram message content since update #76
Comments
You're using an extra data point for notification, right? There is also really a text in there when the adapter wants to fetch the notification? |
yes and yes :-) |
Ok thank you. I haven't actually changed anything that could cause the problem. I'll take a look at it anyway in the days. Currently there is a little bit less time... |
It works with a fixed text. If you need further information, just let me know. |
fixed with V 1.2.3 |
Describe the bug
Since version 1.2.1 the sending of telegram messages for the "finish" message fails.
Error message: (1062) Cannot send message [chatId - 1008357771]: Error: ETELEGRAM: 400 Bad Request: message text is empty
In the device reminder configuration an object with the message is used like in the versions before.
The object contains the text to be sent.
Device has been removed and newly created - with the same behavior.
Versions:
The text was updated successfully, but these errors were encountered: