Parking systems
What happens when a parking system loses internet?
A lost internet connection does not tell you, by itself, whether a parking barrier will open. The answer depends on where access decisions are made, which data is available locally and which equipment still has power.
The operating model
Define the interruption before describing the outcome
An internet outage can leave the local network running. A failed switch can disconnect devices from one another even when the internet service is healthy. A power failure can stop the controller, reader or barrier altogether. Each interruption needs a different test.
Lexoh uses a hybrid architecture: cloud management plus an offline mode, with a mesh network that lets site devices communicate without internet. The mesh provides a local communication path; remote cloud access, payment authorization and electrical power remain separate parts of the operating design.
Existing permissions and new changes are different cases
A controller designed and configured for local decisions may continue recognizing rights it already holds. Verify which credential types, schedules and expiry rules are available in that mode. A plate-reading workflow also needs the recognition equipment and its path to the controller to remain operational.
Changes are a separate question. A new visitor, cancelled booking or revoked credential may not reach a disconnected controller. Define how operators identify that gap and what they do until communication returns.
For example, suppose a contractor’s access is revoked centrally while the entrance is disconnected. An acceptance test should establish whether the local controller still holds the previous right, when it receives the change and what temporary procedure applies. This is a scenario to verify, not a statement that every controller behaves alike.
Separate access, payment and assistance
The lane may still admit a known permit holder while a visitor cannot buy a new parking session. Payment depends on the terminal, provider and configured transaction path. Obtain a specific answer from the payment provider about supported disconnected behaviour; credential storage does not answer that question.
Remote opening, off-site intercom response and live video each need a functioning communication path. A separate cellular service may preserve an assistance call while the main data connection is unavailable. Verify that the operator can also obtain the necessary context and send an authorized command. Local video recording, where configured, does not by itself provide remote viewing.
| Function | What to verify |
|---|---|
| Existing credential | Local rights, schedules, expiry and reader connection |
| New or revoked right | Delivery delay and temporary operating procedure |
| Payment | Terminal and provider behaviour; uncertain transaction handling |
| Remote help | Voice, console and command paths |
| Video | Live access versus any configured local recording |
| Recovery | Permission updates, event retrieval and reconciliation |
A backup connection only protects the path it replaces
A second internet connection can help with loss of the primary service. It cannot repair an unpowered controller, failed local switch or damaged cable between a reader and the lane equipment. Identify shared dependencies before describing a backup as independent.
Test the transition using the services the site needs: a new permission reaching the entrance, a payment attempt and an assistance call. Then restore the primary path and repeat. A router displaying a connected status is not proof that every application has recovered.
Power backup needs a separate scope covering the required loads and operating duration. The barrier’s release behaviour, emergency access and manual procedure must follow the approved site design and equipment instructions. Do not infer them from the word “cloud.”
Recovery includes records and delayed decisions
When communication returns, check more than the device status. Confirm that pending permission changes have arrived and review any events stored locally under the selected configuration.
Finance and operations should have a procedure for uncertain transactions and assisted openings. If a driver reports an apparently failed payment, find its actual status before requesting another attempt. Reconcile any supported delayed records through the agreed workflow and identify gaps that cannot be recovered.
Keep an incident record of the interruption, actions taken and unresolved exceptions. That record helps distinguish a communications failure from an access-rule problem during a later complaint.
Rehearse the interruption before the busy period
Arrange controlled tests with the installer and operating team, during an agreed period with an alternative for drivers. Avoid disconnecting live equipment without a traffic and safety plan.
Use the checklist below for each entrance. Record the observed result, required intervention and person responsible for resolving any difference from the specification. Repeat the affected tests after changes to controllers, payment services or the network.
Project checklist
Outage acceptance record
Use a controlled test window agreed with the site team.
-
Known credential
Test an eligible credential, an expired one and a locally unknown one.
-
Changed permission
Create and revoke a right during the interruption; verify delivery after recovery.
-
Paid visitor
Establish the supported payment path and response to an uncertain result.
-
Assistance
Test the call, operator context and authorized action through the backup path.
-
Recovery
Confirm current permissions and account for records created or missed during the outage.
Questions
Practical questions
Does Lexoh have an offline mode?
Yes. Lexoh combines cloud management with an offline mode. Its mesh network lets site devices communicate with one another without internet. Remote cloud services, payment authorization and electrical power have separate requirements.
Will every valid credential keep working offline?
No universal answer applies. Confirm which rights and credential-processing functions remain available in the selected controller and surrounding equipment.
Does an internet outage make the barrier open automatically?
Not necessarily. Communications-loss behaviour and power-loss behaviour must each be specified for the site. One does not establish the other.
Is a cellular backup enough?
It can address a primary internet-path failure when properly designed and tested. Local networking, power, device faults and service-specific dependencies need separate consideration.
References and further reading
- Lexoh access control
Project-specific interruption, event handling and recovery requirements.
- Lexoh PARCS solution
The relationship between local access, payments and the parking visit.
- Entrance acceptance checklist
Organize the tests and handover records.
Your project
Document the outage plan
Share the controllers, connectivity and required operating hours with Lexoh to define the interruption and recovery tests.
Discuss the project