Charging Cable Theft Prevention
A stolen charging cable takes a bay out of service until the operator notices, orders a replacement and fits it, which is usually days. Locks and heavier cable raise the effort a little. Detecting the cut at the moment it happens changes the economics, because a thief who triggers lights, an alarm and a camera within seconds is a thief who leaves.
Why cables are targeted, how detection works using BLE beacons on the cable paired to the session management device, what can be triggered in response, and the honest difference between deterring theft and detecting it.
Talk about cable theftFor An operator of public or unattended sites losing cables, and the revenue from every bay a missing cable takes out.
Why cables are targeted
A charging cable is a length of heavy copper conductor, unattended, in a public place, attached to equipment that nobody is watching. The value is in the copper rather than in the cable as a cable, which shapes the whole problem.
- The theft takes seconds with hand tools and needs no skill
- The value to the thief is scrap weight, so a cut cable is as good as a whole one, which is why locks at the connector do not help
- The cost to the operator is far higher than the scrap value: a bay out of service, a replacement part, an engineer visit and a reputation problem
- Sites are typically unattended when it happens, so the fault goes unknown until a driver complains or an engineer visits
The asymmetry is the point. A cable worth a small amount as scrap costs a multiple of that to replace, and the bay earns nothing in the meantime.
How detection works
The approach is to make the cable itself something that can be monitored, rather than relying on the charger noticing that something changed electrically.
- 1
Beacons on the cable
BLE beacons are attached to the charging cable. They are part of the cable assembly rather than part of the charger, which is what allows the cable to be monitored independently of whether a session is running.
- 2
Paired to the session management device
The beacons associate with RIOD's EV charging session management device at the unit, so the system knows which cable belongs to which point and what its normal state looks like.
- 3
Detection on cut or removal
When the cable is cut or taken, the expected beacon relationship breaks and the system raises an alert. Detection is immediate rather than waiting for the next session to fail.
- 4
Alert dispatch
The alert goes to whichever destinations the site has configured, described in the next section.
Detecting at the cable rather than at the charger matters because a cable can be cut from a unit that is idle, and an idle charger has no electrical reason to notice.
What can be triggered
The response is configurable rather than fixed, because a basement in an apartment building and an unattended highway forecourt want different things to happen at two in the morning.
Swipe to compare
| Response | What it is for |
|---|---|
| Local alarm unit | Immediate presence at the site. The only response that acts on the person, rather than informing someone later |
| Alert into the CMS | The operational record. The bay is flagged, the fault is logged, and the bay is never found broken by accident |
| Immediate email alert | Reaching whoever is responsible, with a written trail |
| Call alert | For sites where a message at night will not be read until morning |
| Camera trigger | Recording at the moment of the event rather than searching hours of footage afterwards |
Combining them is the normal case. A local alarm interrupts, a camera captures, and the CMS makes sure it becomes a work order rather than an anecdote.
Deterrence and detection are different investments
Worth separating, because operators frequently buy one and expect the other.
- Deterrence makes the site look like a bad target: lighting, visible cameras, signage, cable management that does not leave loops hanging. It reduces attempts and does nothing about the attempt that happens anyway
- Detection does not stop the first cut. It shortens everything afterwards: response, evidence, replacement, and the bay being out of service
- The combination is what changes behaviour on a site, because a thief who triggers a response once tends not to return
Detection also has a value that has nothing to do with the thief: it tells you the bay is down within seconds instead of when a driver complains two days later.
What the system can and cannot tell you afterwards
- The exact time of the event, which is what makes camera footage findable rather than a search
- Which charge point and which cable stopped answering, so the replacement is ordered correctly first time. Not where along the cable it was cut, which the system cannot tell you
- The site state around it, including whether other bays were affected
- A record that supports an insurance claim, which is frequently the difference between a claim being paid and being argued about
The insurance point is undersold. A claim supported by a timestamped detection event and footage from that moment is a different conversation from a claim supported by somebody noticing on Monday.
What you can fit this to
Shipping today, and offered as a technology rather than as a catalogue product, which decides what it can be fitted to.
- 1
Cables already in the field
The beacons retrofit. A site that has already lost cables does not have to replace its units or its cables to get the detection.
- 2
Chargers that are not ours
It works on third-party chargers, taken with the management service. The beacon relationship is with the session management device rather than with the charger's own firmware, which is why the charger's make does not decide the answer.
- 3
Beacon life
Five years, on the fitted battery.
- 4
Sites of any size
A single unattended bay is as valid a case as a hundred. The economics are set by what a cable costs and how long a bay stays out of service, not by site count.
Want this applied to your own site?
Talk about cable theftTechnically reviewed by Deepu Joy, Director of Products and Delivery. Last reviewed 2026-09-10.
Frequently asked questions
How does the system know a cable has been cut?
BLE beacons attached to the cable pair with the charging session management device at the unit. When the cable is cut or removed the expected beacon relationship breaks and an alert is raised immediately.
Can it be fitted to cables we already have?
Yes. The beacons retrofit to cables in the field, and the system works on third-party chargers when taken with the management service, because the beacon pairs with the session management device rather than with the charger firmware. Beacon battery life is five years.
Does it work when the charger is idle?
Yes, and that is the point. A cable can be cut from a unit that is not charging, and an idle charger has no electrical reason to notice. Monitoring the cable itself does not depend on a session.
What happens when a theft is detected?
Whatever the site has configured: a local alarm unit, an alert into the CMS, an immediate email, a call alert, a camera trigger, or a combination. The response is an option set rather than a fixed chain.
Does this stop cables being stolen?
It does not stop the first cut. It makes the response immediate, produces evidence from the moment of the event, and gets the bay back in service faster. Deterrence is a separate investment and the two work together.
Does it help with an insurance claim?
A timestamped detection event with footage from that moment is materially stronger than a report written after an engineer noticed days later.
Losing cables at unattended sites?
Tell us how many bays, how often, and what is at the site already in the way of cameras and lighting. The response set is built around what is there.
Talk about cable theft