[Changelog] concox protocol
Added new devices: Jimi IoT (Concox) JM-LL306 Jimi IoT (Concox) JM-LL309
View Article[Changelog] sinocastel protocol
Sinocastel protocol is updated: old parameters are removed after renaming namo
View Article[Changelog] concox protocol
Added HTTP server setting, RTMP server setting for JC200, JC261, JC400 devices
View Article[Changelog] suntech protocol
Updated BDA report parsing. Indexed parameters ble.sensor.payload.hex will be removed in two weeks - 29-Apr-2025. Use ble.beacons array with ble data (payload.hex, id, rssi) instead.
View Article[Changelog] teltonika protocol
protocol updates: FMX650 series parsing: ID 76 parsed as counter.impulses will be parsed as counter.impulses.1. Both parameters are registered till April 30 ID 10640 is now parsed as...
View Article[Blog] Powered by flespi: Telematics inSights
Instead of showcasing a long-running project on flespi, this time we’re sharing what it’s like to build a video telematics platform from scratch – starting with just a business idea. These guys went...
View Article[Changelog] tkstar protocol
Added new devices: TK-Star TK935 TK-Star TKS1-4G TK-Star TK901-4G TK-Star TK913-4G TK-Star TK905B TK-Star TK818-4G TK-Star TK911pro-4G TK-Star TK919-4G TK-Star TK918-4G TK-Star TK905 MINI TK-Star TKS2
View Article[Changelog] teltonika protocol
Tacho fix: fixed the problem of parsing the driver's name. Case when the tracker does not read correctly or the tachograph incorrectly returns the driver's name. Now such behavior does not happen...
View ArticleIssue with custom.param.109 Not Displaying Data Teltonika FMC125
The event is triggered with event.enum = 109, and the corresponding description is expected in custom.param.109. From the device side, the AVL ID 109 is indeed being sent with the data payload. We...
View Article[Changelog] xexun protocol
Added new devices: Xexun X01 Xexun X02 Xexun X04 Xexun X05 Xexun X06 Xexun DDX04 Xexun DDX14 Xexun DDX15
View ArticleIssue with custom.param.109 Not Displaying Data Teltonika FMC125
AAITech I suggest to address this question to flespi support directly from your flespi account using chat button in top-right corner. And try to chat with codi (AI assistant) about it first.
View Article