[Blog] Our Christmas forecast: Telematics in 2025
The roadmap is set, and the final days of December are the perfect time to reflect. We’re sharing our thoughts on what’s on the horizon for the next year while wishing you a joyful holiday season...
View Article[Blog] Hands-on guide: Teltonika RUT906
Hey , Jan nice article . I did not try to control digital output via MQTT , but I was able to control Modbus via MQTT and send commands to modbus enabled device to control (write) or read data.
View Article[Changelog] e-TOLL PL stream
Stream logs were rebuilt. Now, a log is registered for each message received by the stream. If the message was not sent, the log contains the reason. Also, the stream can now send historical messages.
View Article[Changelog] sinocastel protocol
New Protocol ID 0x401F Comprehensive data upload is supported for sinocastel protocol
View Article[Changelog] assistant-telematics protocol
flespi now works with Assistant Telematics devices. The list of supported models: ATL100 AVT110 AVT111 AVT131 AVT20 AVT50
View Article[Changelog] suntech protocol
Added BLE report parsing. The array of beacons is stored in ble.beacons array. Small assigned header 88 is parsed in the parameter dead.reckoning.state
View Article[Changelog] meitrack protocol
Custom command updated: additional check for command_type parameter added: it can not be longer than 3 characters.
View Article[Blog] Flespi Platform Monthly Changelogs
🎄 December 2024 change log 100% uptime for the 3rd month in a row protocols integrated: assistant-telematics and generic jt808 streams logging expanded for detailed message delivery tracking new UI...
View Article[Changelog] concox protocol
Added dsm.event.enum, dsm.alarm.level, adas.event.enum, adas.alarm.level parameters for jc371, jc181, jc450 devices
View ArticleClik here to view.
[Changelog] flespi AI assistant
We've enhanced codi's capabilities with protocol implementation analysis features. Now our AI assistant can: Analyze protocol implementation details Explain parameter names, values and conditions...
View Article[Changelog] meitrack protocol
Report type 110 data representing Transparent CAN data is now stored as payload.hex message parameter.
View Article[Changelog] BCE protocol
Change in sending custom command. According to the protocol, the devices do not have the ability to send text commands that are intended for SMS in binary form via TCP. Now text commands can only be...
View ArticleClik here to view.
[Changelog] itriangle protocol
itriangle protocol is supported in flespi telematics hub. The list of supported devices iTriangle TS101 Basic
View Article[Changelog] tollbg stream
Stream logs were rebuilt. Now, a log is registered for each message received by the stream. If the message was not sent, the log contains the reason.
View Article[Changelog] maxoptra stream
Stream logs were rebuilt. Now, a log is registered for each message received by the stream. If the message was not sent, the log contains the reason.
View Article[Changelog] gefco stream
Stream logs were rebuilt. Now, a log is registered for each message received by the stream. If the message was not sent, the log contains the reason.
View Article[Changelog] xirgo-mqtt protocol
Change in sending custom command. According to the protocol, the devices have the ability to send text commands only via SMS. When trying to send a text command not via the SMS, an error message will...
View Article[Changelog] streamax protocol
The protocol contains DMS codes, some of which mean ADAS event and were stored in dsm.event.enum and dsm.event.name parameters. Now events are divided into two types ADAS and DMS and corresponding...
View Article[Changelog] omni protocol
Fixed S6 Obtain scooter information report parsing from OMNI M136 IoT Box
View Article