MQTT->MQTT broker->TQL->MSSQL #251
-
Hello. I'm looking for help to understand the workings of machbase-neo better. I do not see any discussions anywhere yet. Is this because machbase-neo is a new project? I see it started around 2023 February. I found machbase-neo because I need a compact system that can handle MQTT JSON data, have a MQTT broker, and can transfer this to a database (ms sql or machbase own db?) for uses with Grafana. If I'm not wrong I can do all that too with machbase-neo. Even drawing graphs and statistics. (I do not wish to use AWS) AXIS MQTT (JSON) -> MQTT-Broker -> bridge(mqtt) -> ????(TQL?))))) -> bridge (ms sql) -> grafana Now I need subscribe and save the data to MSSQL. If I understand right this can be done with a TQL script. I think I'm stuck with the TQL script writing part right now. I tried to follow the tutorials, but it is not enough or it just not clicks for me how it supposed to work. Here is an example output of an AXIS payload: { |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
welcome to machbase-neo, I'll upload some example or tutorial of your case. It could be take one or couple of days. |
Beta Was this translation helpful? Give feedback.
-
MQTT Client --> MQTT Broker (mosquitto) --> machbase-neo --> External DB (sqlite) tutorial worked. Thank you. I also tried to do the "db/write/{TABLE_NAME}" method but it looks like the JSON format is not standard, so it did not write in the DB. From your example I created a modified TQL script. Which after some tinkering works. Now I need to make some nice graphs and place it on the dashboard. |
Beta Was this translation helpful? Give feedback.
I have update a new tutorial for your case. --here https://docs.machbase.com/neo/tutorials/mqtt-bridge-sqlite/
The tutorial that demonstrates:
In this setup, machbase-neo functions as an MQTT Client (subscriber), a DB Client, and an Application (TQL script parsing JSON document).
While this scenario showcases the capabilities of machbase-neo, it is not practical due to the complexity and numerous components involved for a simple task.
The simplest approach is:
If your goal is to store data from an MQTT client and visualize it, you don't need external MQTT brokers or other dat…