Botmother, AI assistant and Telegram

All topics · 08 · Bots & automation · Deutsch

Where to find it

Preferences → General → Botmother; then Accounts → account → Botmother

A bot processes messages or performs configured tasks. You do not need these features for normal chatting. Local Botmother requires DinoX to be running; a separately hosted CloudBot is a different service.

An AI or Telegram integration passes content to the configured service. Deliberately choose destinations, permissions and provider before enabling it. An API token is an access key and does not belong in public chats or pictures.

What to do

Enable Botmother under General. Keep the local API mode for normal local use.
Open Botmother for the intended account. Check account activation and create a bot or select an existing one.
Set the name, permissions and target restrictions. Permit only required actions and save.
Configure and enable additional sections individually. Use status indicators and offered test actions.

What do the choices mean?

AI Assistant

Enter the provider, model, credentials and any custom server address. The AI test question checks a response without sending it to an XMPP chat. Costs and data processing depend on the chosen service.

Telegram bridge

Enter the Telegram bot token, chat ID and offered mode, save and enable. A Telegram chat ID is not an XMPP address. Check destination and direction before real use.

Webhooks and local API

For integrating your own software. A webhook sends events to a configured address. Configure network mode and a TLS certificate only when deliberately granting other devices access. Use the API documentation for concrete programming calls.

CloudBot

An existing hosted bot can be loaded using its management token. Check ownership and status. Local API tokens, CloudBot management tokens and event tokens are different credentials; rotation can invalidate previous access.