Telegram — the main channel

You control the bot and receive every notification in Telegram: statuses, alerts, reports, command confirmations. Other channels only mirror notifications — control always lives here.

How to connect

  1. Create a bot with @BotFather

    In Telegram, find @BotFather, send /newbot, pick a name and username. BotFather returns a token like 1234567890:AA… — that is the bot's password.

  2. Give the token to the bot

    Run the install wizard bash install.sh — it asks for the bot token. For an installed bot: python3 -m ocbot --config config.json --telegram-set 'TOKEN' — the owner ID is detected automatically.

  3. Confirm you are the owner

    Send your bot any message: it takes your Telegram ID from recent messages (fallback — @userinfobot shows your ID). Only the owner can command the bot; everyone else is ignored.

  4. Check it

    Send /status — the bot reports card states and presets. Full command list — /help; commands are autocompleted in Telegram too.

If Telegram is restricted by your ISP

The bot can reach Telegram through a proxy; it speaks HTTP/HTTPS:

python3 -m ocbot --config config.json \
  --telegram-proxy 'http://192.168.3.5:8080'
# with authentication:
python3 -m ocbot --config config.json \
  --telegram-proxy 'http://user:pass@IP:port'
# to disable the proxy:
python3 -m ocbot --config config.json --telegram-proxy ''

The value is stored in config.json as tg_proxy; the wizard asks about the proxy as well, if Telegram is unreachable. SOCKS5 needs extra software and is not supported — use HTTP proxies.

Note: the proxy is your own. The bot can work through one but does not provide or sell proxies: use your network's proxy (a router, corporate) or one bought from an external provider. If a proxy is not an option — mirror notifications to MAX.

What arrives in Telegram

FAQ

401 Unauthorized — the bot errors out

The token is invalid (re-issued or a typo). Generate a new one with @BotFather and set it again via the wizard or --telegram-set.

The bot is silent — Telegram unreachable

Your ISP restricts Telegram: set an HTTP proxy (see above) or connect MAX/Discord/ntfy for notifications; control still needs Telegram.

"Not the owner"

By design: the owner ID is stored in config.json (owner_id), strangers are ignored. To change — message the bot first (the wizard updates it) or set the ID manually.

Telegram notifications do not arrive

They are always on; check the bot answers /status. Extra channels mirror; test them with /notify test.

Can I switch the bot?

Yes: set a new token (--telegram-set or the wizard). History, presets and the database belong to the rig — nothing is lost.

Terms: connect with /notify …, test with /notify test, disable with /notify off …; full terms and disclaimer are in the guide.

Independent project: not affiliated with Hiveon/HiveOS; their names belong to their owners.