Skip to content
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

Can't get telegram bot working #25

Open
N1k145 opened this issue Aug 22, 2023 · 5 comments
Open

Can't get telegram bot working #25

N1k145 opened this issue Aug 22, 2023 · 5 comments

Comments

@N1k145
Copy link

N1k145 commented Aug 22, 2023

When I try to setup the telegram bot I can't send a test message, it always prints
undefinedChatId and invalidChatId in the docker log.

When I send a message to the bot it seems that it can't get the chat id.

When I set the chat id manually in the JSON file as "telegramLastChannelId": "12345" (with my correct Id) I don't get the error anymore but I also don't get a message

Is this something you can look into?

@edoardolimone
Copy link

edoardolimone commented Sep 19, 2023

HotHost_issue
I've the same problem in a docker installation. When I try to send the test message after the configuration, the LOG register this event:

Incorrect chat id

and

[90mundefined�[39m chatId

@SkiperX
Copy link

SkiperX commented Jan 22, 2024

Notifications in Telegram and Gmail do not work

@SkiperX
Copy link

SkiperX commented Jan 22, 2024

Please make telegram chat id a separate field, now it’s not clear how to make sure that it is defined correctly in the application. And how to change it

@SkiperX
Copy link

SkiperX commented Jan 23, 2024

Managed to launch telegram alerts

  1. create a volume for the data folder
    volumes:
    - ./data:/var/lib/hothost/data/
  2. add the bot token to the plugin settings
  3. stop the container
  4. replace in the hothost.json file in the line "telegramLastChannelId": ["-111111111111111"] your chatid
  5. run the container
  6. send a test notification in the plugin

@ivictbor
Copy link
Contributor

ivictbor commented May 3, 2024

Thanks, we will take a look. We are now working on v2. Probably fix will be there, probably in this version. @MultiFox200 how do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants