On September 4, 2024, flespi reached 1 million registered devices. I won't say we worked a lot towards this particular milestone; it just happened naturally while our primary focus was, and still is, bringing easy-to-use telematics to applications. But it was a pleasant and memorable day that we celebrated with the team. Check the article for detailed statistics on the countries, device manufacturers, and industries that contributed to our first million. We're already on the way to our second million.
Our monthly uptime was 99.9936% due to a single downtime of 167 seconds we experienced on September 26, and this time it was beyond our direct responsibility. Telia, our Tier 1 connectivity provider, reported a failure of their IP card in Amsterdam, which temporarily affected flespi network accessibility for around 70% of various locations worldwide.
We added Cipia to the list of compatible manufacturers for the video telematics functionality in flespi. Our internal tech stack achieved tremendous throughput capabilities with the integration of new protocols. Now, it's not just about standard telematics ones; even MDVRs can be easily integrated into flespi within just a few days - Actia and Dragino-mqtt protocols were integrated that fast.
We decided to enable the assignment of geofences to individual devices to simplify configurations on top of flespi. Now, it will be possible to define a per-device list of geofences to control entry/exit with a single app-wide plugin or calculator. This feature is already implemented in the REST API and plugins, while calculators will handle geofence-to-device assignments in mid-October.
We introduced numerous DTC codes to the msg-dtc-decoder plugin and plan to add even more manufacturer-specific codes when the exact manufacturer can be selected in the plugin configuration.
We added the ability to right-click on the log line in Streams, Plugins, and Webhooks, allowing you to navigate directly to the raw traffic related to that log entry. This feature simplifies diagnostics for plugins, webhooks, or streams.
We've noticed a growing number of Apple stack users reporting issues connecting to flespi.io. After preliminary diagnostics, we discovered that we're not alone in facing such problems; the reason is that Apple released a buggy implementation of frame compression for WebSockets in beta versions of Safari and iOS. WebSockets are used as the transport for MQTT connections to the flespi MQTT Broker, which flespi.io heavily relies on. Due to the popularity of Apple products among our users, we disabled compression in the MQTT Broker for all WebSocket connections. Once Apple resolves the compression issues in their products, we will enable it again in our MQTT Broker.
We finally removed REST API methods operating with deprecated device and container snapshots. Internally, snapshots are part of our database backup system, and we're preparing to overhaul it soon with a more modern and effective implementation.
In September, we committed several new features to the TrackIt application, including UI modernization and real-time tracking mode. Check the TrackIt Changelog for details.
Tachograph-specific functionality is now almost ready for use. We've already implemented the framework and are actively testing and adjusting the entire cycle of the durable DDD file retrieval process for Ruptela devices. So far, everything is running smoothly and according to our expectations. Just give us one more month to finalize the work and make it as seamless as possible. Expect the announcement of tacho-related features in November, so stay tuned for updates!