namo Invers-oneapi protocol is supported by flespi telematics hub. The channel is capable to consume real-time events from AMQP broker and send commands via CloudBoxx API
namo Invers-oneapi protocol is updated, new settings added: VIN, Info tab Central Lock and Immobilizer, Access tab
namo Invers-oneapi protocol is updated. Now when VIN setting is requested from the device, message with vehicle.vin parameter will be registered for the device. As a result vehicle.vin parameter will be stored in device's telemetry.
kial Message parameter position.sattelites will be renamed to position.satellites in a week, Tue Jan 24. Now both parameters are registered.
baja The invers-oneapi channel protocol now supports the new Invers OneAPI for device commands. What changed: New Client ID and Client Secret fields in channel configuration for OneAPI OAuth2 authentication Commands now use the OneAPI vehicle-centric endpoints instead of the legacy CloudBoxx device API Action required: If you are using device commands or settings with the invers-oneapi protocol, please obtain OAuth2 credentials from FleetControl (Administration > API Clients) and fill in the Client ID and Client Secret fields in your channel configuration. The legacy API Key field will be removed in 2 weeks (March 12, 2026). Please migrate to the new credentials before that. AMQP telemetry streaming is not affected by this change.
baja baja transition finished. The commands can be sent now only with the OAuth2 credentials from FleetControl
