At first: Thanks for the nice work!
I got it running now, just need to figure out how to easily remote control the pi desktop itself. Since i'm a few thousand kilometers away the next weeks i would feel better having the possibility to restart/stop the reset tool manually. I don't like the theoretical possibility of getting my rigs rebooted continuously for weeks
Concerning the telegram bot: You have to set your telegram username (i had to choose one at first) as admin name in the json file. Not the Bots admin name! Got the "not my master" message, too. After that you are able to ask the bot via /status, /ping Rig, /help, ... (see commands in telegram.go switch)
For my opinion a notification each time a rig reboots would be great, too. But anyways - great work so far!
I just messed with this for probably five hours (learning curve). I got it up and going now though, at least half, really awesome idea and it may or may not be "that difficult" for someone already experienced. It's a massive help here. So, thanks! I have been meaning to dive into a micro controller for a while, figured now is a good spot to start.
Now I just keep getting an error "Problem with the API key. Fix the problem or disable the TelegramBot from the config file" seems like the api key (around 32 letters/numbers) is correct to me..... I'll mess with it later
Ok, made it past that, now when I send a message from my phone to the bot it just says you're not my master. Skimming through the code it seems it checks something and says this before it can go further. So that's what I'm working on now, step by step pretty good learning experience.
Journey continues, bot now accepts commands, bot name, vs username changes, and everything else lol.
So, a question: Is telegram suppose to send me a message when a rig goes down? I looked through the code some more and I don't think it does currently, but I can't be sure lol
OK, Pushover notifications worked lol