Unable to include the TELEGRAM_BODY to receive direct link

[Schollino]

Unable to include the TELEGRAM_BODY to receive direct link

[pershoot]

${{display_name}}\nLink: ${{link}}

For the above example (Note: code omitted the asterisks (for bold)):
asterisk
dollar sign
two curly braces in
display_name
2 curly braces out
asterisk
backslash n
asterisk
Link
asterisk
colon
space
dollar sign
2 curly braces in
link
2 curly braces out

...

Please also see this: #351

Edit:
Please see this, regarding Portainer (add surrounding single quotes):
#154 (comment)

[Schollino]

Hi,
thank you for your fast reply. I just changed the input accordingly to your suggestion:

I get the following failure-message:

Also the closing with another $ shows the same message.

[pershoot]

Please see this, regarding Portainer:
#154 (comment)

[Der-Henning]

Hi @Schollino.
In Portainer you need to add quotes.

- 'TELEGRAM_BODY=*${{display_name}}*'

[Schollino]

I think this will not work ...
I am using the "Stack"-Feature in Portainer with the "editor", which obviously uses docker compose to create the container. The rest in the editor looks like this:

If I add the quotes, Portainer complains about this which results in a failure.

[pershoot]

Try this:
- "\'TELEGRAM_BODY=*${{display_name}}*\n*Link*: ${{link}}\'"

[Der-Henning]

I use portainer on docker swarm. My telegram config (working):

      - 'TELEGRAM_BODY={{`*$${{display_name}}*\n*Anzahl*: $${{items_available}}\n*Wann*: $${{pickupdate}}\n*Wo*: $${{pickup_location}}\n*Preis*: $${{price}} $${{currency}}`}}'

[Schollino]

This entry is marked red in the portainer editor ...

... and leads to this error:

2024-01-28 14:45:54 ERROR Telegram Error: Can't parse entities: character '{' is reserved and must be escaped with the preceding ''. For details see https://github.com/Der-Henning/tgtg/wiki/Configuration#note-on-markdown-v2

[Schollino]

Any suggestions? :-(

[pershoot]

Any suggestions? :-(

Are you on the latest Portainer update?

[Der-Henning]

In my setup I use the compose version: "3.6".

[Schollino]

My version is 2.18.2. After an update, my version is 2.19.4.
In my Stack-Editor of the tgtg-container, my version is version: '3.3'

I do not understand, why every suggestion begins with an ' before TELEGRAM_BODY? I did not find any config for a docker container, where it is written like this - 'TELEGRAM_BODY ... By the way: also not in the example-config under https://hub.docker.com/r/derhenning/tgtg .
Could you maybe once share your config for docker/portainer or describe the way, you integrate this?

[Der-Henning]

The surrounding ' ' is a portainer thing. I don't know how I figured it out when I had the same problem, but the data you put in the portainer UI is not exactly the same as if you create a compose.yml as you could also include environment variables in compose files.
The environment variables defined as list - key=value are send as strings including key=value to the container.
The ' ' should send the string as is to the compose backend.

Another way is to define them as key-value pairs with key: value.
But you cannot mix both notations.

[Butanding]

I had the same issue with portainer, this is what worked for me:
- 'TELEGRAM_BODY=*$${{display_name}}*\n*Pickup*: $${{pickupdate}}\n*Order*: $${{link}}'
Kind of strange format tbh though.

If somebody could confirm this working, i think it would be nice to add this to the docs.

[Schollino]

Hi,

wow, I don't understand why, but it works!!!
We should really add this in the docs.

Thank you very much :-)

[floriegl]

This information was present in the docker-compose.yml until e6b4c07. Somehow in the transfer of the configration information from the docker-compose file to the wiki a lot of important information got lost. Can we maybe ether add this file back as an e.g., docker-compose.example.yml or add the missing information from there to the wiki (which configurations need special handling in docker compose files (including the 'TELEGRAM_BODY={{...}}' thing), where to get a google maps API key from, ...)? @Der-Henning