xdwart / mqtg-bot Goto Github PK

Currently every telegram user (or telegram channel) is greeted with /start and asked to configure the server. Once configured, each users data is stored individually instead of using the same data that is already in the database for another user.

Proposed solution::

• configure the server only once
• have all users use the same database (only store each subscription once, delete one no one is using the data anymore).
• make button configurations the same for all users (or possible to copy from another user)

Cheapest solution :

• Add a startup flag to make the server 'secure' allowing no new users.

I used tcp. Another client connect normally.

1618470430: New connection from 34.242.211.143:35710 on port 1883.
1618470430: Client disconnected due to out of memory.
1618470430: New connection from 34.242.211.143:35720 on port 1883.
1618470430: Client disconnected due to protocol error.

Добрый день.
спасибо за проект подскажите, чтобы запустить бот у себя мне нужно поднять БД postgres?

А можно как-то одной кнопкой считать все или выбранные subscriptions и вывести? Т.е. иногда полезно знать состояние девайса в целом. Так же есть проблемка с кнопками toogle на хорошее им нужна какая-то обратная связь. Т.е. если параметр изменил другой клиент или скрипт, то кнопка тоггле сработает только со второго раза. Хотя это наверное сложно поправить.

Just a small glitch, the bot crashes (division by 0):
Preconditions: Fresh bot, with no subscriptions
Activity:
Added a folder
Added a button of type "last value"
Gave it a name, and division by 0 and dies
"Workaround":
Add a subscription first

Currently anyone who can talk to the bot can also send commands and subscriptions. This poses the risk of strangers abusing your service to interact with your environment (via mqtt or the configuration) and or using your server for their likely malicious purposes to connect to other mqtt servers on the internet.

Proposed solution::

First user (or channel) to connect & configure mqtg after a start (empty Database) becomes the owner of the server, might be a flag that can be granted to others.

Additionally the owner would have then the possibility to decide whether :

• the server is public (as it is today) or private
• whether access requests would be allowed (new users connecting with /start) -or- users are to be added manually.