If you are buying connected rental scooters or e-bikes and want to self-manage your fleet data, the IoT hardware matters as much as the vehicle itself. Two of the most common platforms we work with are Omni IoT and Segway-Ninebot. Here is what we have learned integrating both.

Omni IoT

Omni’s rental IoT nodes communicate over MQTT and expose a relatively clean API for lock/unlock, GPS position, and battery status. The main advantage is that Omni hardware is designed from the ground up for the rental use case — QR-triggered rentals, remote unlock, and return workflows are first-class features.

For operators who want to bring their own platform, Omni devices can be pointed at a self-hosted MQTT broker. GopalDesk subscribes to the broker and surfaces device state without going through Omni’s cloud.

Segway-Ninebot

Segway-Ninebot hardware uses CAN bus internally, with a gateway module that translates to TCP or MQTT for cloud communication. Integration is more involved — the CAN protocol is partially documented, and some commands (BMS state, custom lock modes) require reverse engineering or firmware customisation.

If you have Ninebot hardware and want it talking to GopalDesk, the path is: device → Teltonika or custom IoT gateway → Traccar protocol → GopalDesk. We have done this for client fleets and it works reliably once the CAN mappings are confirmed.

Which should you choose?

For a new fleet purchase where self-managed IoT is a priority, Omni is lower-friction to integrate. For operators who already have Segway-Ninebot hardware, integration is absolutely possible — it just requires more upfront configuration work.

GopalDesk supports both. Contact us if you want help scoping an integration for your specific hardware.