On site first and its links, then the scale of the outage in the dashboard’s “Maintenance” tab. Then station by station: the status and the reason for the disconnection in the logs, and the station that keeps rebooting.
Transcript Click a paragraph to play the video from there.
Introduction 0:06 Hello! A station that was working has disconnected, or several at once, or it keeps dropping out: let's see how to find the cause. Before the platform 0:15 In the vast majority of cases, a station that no longer connects has no platform problem. The cause is on site: its network, or the station itself. 0:24 Most often, it's the network: a SIM card whose data plan has run out, or a mobile antenna that's down. 0:30 On a company network, it's often the router or the firewall blocking the station. Or its own network settings, such as the DNS server. 0:39 And sometimes it's the station: faulty, or after a firmware update pushed remotely by the manufacturer. 0:46 There may also be one more link. A master station relaying its satellites: if it drops, they all drop. Or a gateway, such as the manufacturer's supervision or an energy management system, which cuts off all the stations it carries. 1:00 The right reflex: how many stations are affected? Just one, while the others are connected: the cause is on site, not in the platform. Many at once: think of a batch of SIM cards, or an antenna down in one region. Gauging the scale 1:16 To find out how many stations are affected, open the “Dashboard”, “Maintenance” tab. At the top: the stations disconnected right now, and their share of the fleet. 1:26 The “Incident timeline” shows a peak: six stations dropped off in the same hour. This isn't a station failure, it's an event. 1:37 The disconnected stations map pinpoints it: everything is concentrated in Marseille. 1:42 And “Most affected sites” confirms it: Plateforme Marseille Port is entirely offline. When a whole site goes down, it's often its internet access, its power supply, or the antennas in the region. 1:55 In Lyon, on the other hand, only one station is affected: ACME-LYS-04. That one, we diagnose individually. The station's status 2:05 In “Charging Stations”, the status column confirms it: ACME-LYS-04 is “Disconnected”, its neighbours “Connected”. 2:16 Hover over the status: you read how long the station has sent nothing. On its page, the “Hardware” tab also gives its “Last Seen” and its OCPP version. The logs 2:29 To find out why, open “Logs” and search for the station. Here, it no longer answered the platform's checks: after three attempts, the connection was closed. 2:42 Here, the platform cut off a station that no longer answered: the cause is investigated on site, or with the installer. The help center details these checks. The station is back 2:52 Once the problem is fixed, the station reconnects by itself and goes back to “Connected”. An unstable connection 2:58 Last case: a station that keeps dropping out and coming back. If it reboots each time, “OCPP BootNotification bursts” flags it: ACME-LIL-02, six reboots in twenty-four hours. The cause is on site: its power supply, its network or its firmware. Key takeaways 3:21 Remember: most often it's the network or the station, not the platform. A single station or a whole site: the “Maintenance” tab tells you. “Logs” says why the connection was cut; and a station that keeps rebooting shows up in the “bursts” card. 3:38 In the next video: an RFID card that doesn't start the charge.