I’m writing to describe an issue I’m experiencing with the Teltonika RUT956. When using the MQTT protocol with this device, I noticed that the data is not sent in ISO-8601 format. Additionally, I would like to configure both birth and Last Will messages, but I found that these settings are not available in the Teltonika dashboard server, specifically in the “data to server” section.
Does anyone have any suggestions or advice on how to address these issues? I’m looking forward to any tips or guidance you might have.
The Data_To_Server service is a separate entity from MQTT. It allows you to gather data from different sources and then periodically transmit it to remote servers. Therefore, when data is sent via this service, it’s no longer in the MQTT format but instead is parsed as JSON.
Thank you for the clarification regarding the Data_To_Server service and its distinction from the MQTT protocol. Given this understanding, I have a couple of follow-up questions:
given that my rut956 recieve data from sources through RS485 s. communication and since i want to send these data to a remote server through MQTT, my questions are:
ISO-8601 Data Format: How can I configure the Teltonika RUT956 to ensure that the data sent via MQTT is in the ISO-8601 format?
Birth and Last Will Messages: How can I set up birth and Last Will messages within the Teltonika RUT956 for MQTT communication? I understand that these settings are not available in the “Data to server” section of the dashboard, but is there another way to configure them?
Any guidance or step-by-step instructions on how to achieve these objectives would be greatly appreciated.
Sorry, to inform but birth and last messages are not implemented. And regarding ISO-8601 Data Format: what do you have in mind? As MQTT broker does not interfere/adjust what is inside published MQTT messages.
I don’t understand what you meant, as you can configure the MQTT message payload yourself and publish it to specific topics. Could you elaborate a bit more on what are you using to publish those messages? Who is the broker?Publisher?Subscriber?
Thank you for your assistance. I’ll try to describe the problem more clearly: as a company, we have many gateways spread across the globe. This means we need a system to identify their locations. We use the time zone in ISO 8601 format to trace the position of the signal by parsing the local time. This is why we need this specific format. It seems that is not possible to customize the data in this format using modbuss message data type in “data to server” section.
So to be brief, i am now wondering, is it possible to perform a sort of “edge computing” on this device?
Sorry if i did not explain well the problem, i really appreciate your help.
I understand now that you’re not using MQTT but monitoring data from a Teltonika device via Modbus. So, in this scenario, we can’t change the format to what you want. However, “edge computing” can still be done since the device can run bash and Python scripts. This would need to be managed by you separately.
Moreover, we can also implement acceptance of different time formats at the server level.
and i tried to install python3 package but there is not enough memory in the flash one.
Also i saw that in Input/Output section ther is this possibility:
Yes, this lead could be followed. And for CLI: maybe you are accessing device remotely, issue in the image other way looks puzzling? YOu can try accessing device using SSH too. Just a reminder → Username: root Password:<your_device_password>
No i am not tring to access remotely since i’m on the section system->mantainance->CLI.
I’ll try to use SSH. thank you for the help. I’ll update you.
Kind regards.
I solved the edge computing problem using Python through remote CLI.
To address the memory constraints, I used an external USB flash memory to expand the device’s storage.
I also installed pip to install external python lib.
I created a script that utilizes the paho and pymodbus libraries.
Additionally, I wanted to leverage the data set by the dashboard configurations “data_to_server” and “modbus_serial” so that users can avoid manually setting parameters in the back-end script. To achieve this, I used the Teltonika web API (Teltonika Developers).
I would like to know if there are other Teltonika devices that can avoid the need for external memory; if so, which ones? I’m curious to know.
I want to report a bug: the MQTT client password in “Data_to_Server” is always reset to ‘set’ even when I change it to the correct password and click “save and apply”. Consequently, I receive ‘set’ as the password when I retrieve it using the web API. Why does this happen, and how can I fix it?
If you need a device with more memory, consider trying TRB1, TRB5, and RUTX series devices. Regarding passwords for MQTT via data sender, does it only affect retrieval via API? What API request are you using? Additionally, is the MQTT password saved correctly in /etc/config/data_sender or as “set”?
