search

iobroker-community-adapters / ioBroker.telegram

Use Telegram service to communicate with ioBroker
MIT License
56 stars 45 forks source link

Recipient mix with username and firstname - Benutzername vs Vorname #854

Open OneCreek opened 3 months ago

OneCreek commented 3 months ago

Describe the bug
Recipient is one user (M) having a public username (eg. Mpublic), the second recipient (K) doesn't have a public username. See **Expected behavior": I expected to be able to mix username and firstname (when no username exists).

To Reproduce
'Store username not firstname' active. Send message to "Mpublic; K" But when "store username" is active, only Mpublic gets the message. When "store username" is deactivated, only K gets the message.

Expected behavior

"If the option is set and the user did not specify a public username in his telegram account, then the adapter will continue to use the firstname of the user."

„Benutzernamen statt Vornamen speichern“ in den Adaptereinstellungen aktiviert ist oder nicht.) Wenn die Option aktiviert ist und der Benutzer in seinem Telegram-Konto keinen öffentlichen Benutzernamen angegeben hat, verwendet der Adapter weiterhin den Vornamen des Benutzers."

So I expected to be able to mix username and firstname, since I use the username for M with Mpublic and K as firstname (no username existent). When "store username" is active, both Mpublic and K should get the message.

Versions: