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

[Bug]: secrets file is not being picked up? #289

Open
1 task done
Otann opened this issue Oct 16, 2023 · 3 comments
Open
1 task done

[Bug]: secrets file is not being picked up? #289

Otann opened this issue Oct 16, 2023 · 3 comments
Assignees
Labels
bug Something isn't working Next release Extra attention is needed
Projects

Comments

@Otann
Copy link

Otann commented Oct 16, 2023

What happened and in what context?

I have the telegram.conf file

#  Please refer to the wiki(https://github.com/nlef/moonraker-telegram-bot/wiki) for detailed information on how to configure the bot

[bot]
server: localhost
# bot_token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# chat_id: 1

[secrets]
secrets_path: /home/pi/printer_data/config

[progress_notification]
time: 600
percent: 10

[status_message_content]
content: progress, eta, finish_time, m117_status, last_update_time
sensors: rpi, canbus_mcu, chamber
heaters: extruder, heater_bed
fans: chamber, nevermore

[camera]
host: http://localhost:8080/?action=stream
rotate: 180
fps: 30

[telegram_ui]
buttons: [status,pause,cancel,resume],[emergency,macros,shutdown],[HEATSOAK, COOLDOWN]
require_confirmation_macro: false
progress_update_message: false
status_message_m117_update: true

and I have secrets.conf file in the same folder next to it:

[secrets] 
bot_token: xxxxx
chat_id: 111111

But when the bot starts it complains that the values are not provided. And if I use fake values, the log says that the token is invalid.

It looks like the secrets file is not being used, or am I doing something wrong?

If needed, paste the relevant bot log contents here.

No response

If needed, paste the relevant bot journal contents here.

No response

What branch does this occur on?

master

Reports only on latest master or development branches!

  • I have updated to latest development/master version before submitting the bug
@Otann Otann added the bug Something isn't working label Oct 16, 2023
@nlef nlef self-assigned this Jan 6, 2024
@nlef nlef added this to Unsorted bug reports in Bugs via automation Jan 6, 2024
@tinyfluffs
Copy link

Same issue happens here, clean install from KIAUH.

@vasyl83
Copy link

vasyl83 commented Feb 24, 2024

just tried and having the same issue

@nlef
Copy link
Owner

nlef commented Mar 8, 2024

@Otann @vasyl83 @tinyfluffs
For now you can specify the full path with the name of the secrets file.
Default secrets filename fixed in 6601fdf

@nlef nlef added the Next release Extra attention is needed label Mar 8, 2024
@nlef nlef moved this from Unsorted bug reports to In testing in Bugs Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Next release Extra attention is needed
Projects
Bugs
In testing
Development

No branches or pull requests

4 participants