Reasons Behind an Offline IoT

Since Segway IoT modules are primarily used for internet connectivity, they can sometimes be mistaken as faulty when they go offline. However, there are several possible causes, and the IoT itself may be fine. This article covers the three main reasons an IoT can go offline.

The Three Main Causes

1. Scooter is in Transport Mode

When scooters are first received from the factory, they are placed in Transport Mode (also called Shipment Mode). In this state, all power to the scooter is cut off, including the IoT's 4G module - so the scooter will appear offline.

Fix: Charge the scooter to bring it out of Transport Mode. See the Transport Mode guide for full instructions.

2. Hardware Failure

The IoT module is resistant to water and normal environmental conditions, but can be damaged by physical impact. Hardware failures fall into three categories:

• Error 32 - The controller is unable to receive a response from the IoT. This is often caused by a loose or damaged connection between the IoT and the scooter's controller.
• Siren (4 loud alarms) - The IoT's anti-theft alarm is triggered. This can drain the battery and cause offline issues.
• No response - The IoT is completely unresponsive, possibly due to physical damage or a failed component.

For hardware failures, the IoT module may need to be replaced.

3. Incorrect Activation, IP, or APN Settings

Even if the IoT hardware is working correctly, it cannot connect to the server if:

• The scooter has not been activated in the Segway Dashboard
• The IP address configured on the IoT does not point to the correct server
• The APN (mobile data network name) is incorrect for the SIM card installed

Fix: See the appropriate guide for your IoT type:

• Troubleshoot Offline Scooter - NB-O, NB-S3, NB-O3 IoT
• The same guide covers NB-Y (Queclink) IoT troubleshooting with ZK600 app steps

Quick Diagnostic Steps

1. Check if the scooter is in Transport Mode (display will show a specific icon)
2. Verify the scooter is activated in your Segway Dashboard
3. Check the IoT type in the Dashboard and follow the appropriate IP/APN verification guide
4. Inspect the IoT physically for visible damage or loose wiring