If your LG Multi V system is showing error 242, the system has lost its network connection to the central controller.
This one is different from the other communication codes in a way that matters: your equipment may still be running.
What this means for your building
Error 242 is a network error at the central controller level, or a communication defect involving a remote controller. It sits above the unit-to-unit communication that codes like 237 and 05 describe.
The practical consequence is loss of oversight, not necessarily loss of cooling. Indoor units may carry on operating on their last instructions while the central interface shows nothing.
That is precisely what makes it easy to under-react to.
What you actually lose
In a small installation, not much. In a large building, quite a lot:
- Central monitoring — you cannot see system status or faults from one place
- Scheduling — time-based control across zones stops being enforced
- Setback strategies — out-of-hours and unoccupied settings may not apply
- Fault visibility — the next fault to occur will not surface centrally. You find out when a tenant calls.
That last point is the one worth weighting. A building running blind will still discover its problems, just later and more expensively.
The sub-codes
| Sub-code | Unit |
|---|---|
| 2421 | Master outdoor unit |
| 2422 | Slave outdoor unit 1 |
On a multi-module system this narrows which unit’s network connection to investigate immediately.
How urgent is it?
Less urgent than a protection fault, more urgent than it feels.
Nothing is being damaged. Tenants may not notice for days. But you have lost the layer that would tell you about the next problem, and control strategies that reduce your energy costs have quietly stopped applying.
What it typically costs
Low to medium.
Most cases resolve to network cabling, addressing configuration, or controller settings — technician time rather than parts.
Cost rises only where the central controller itself has failed, which is a hardware replacement.
What causes it
- Communication defect between central controller and system
- Remote controller communication problems
- Indoor unit addressing errors — a common and easily missed cause
- Damaged or disconnected network cabling
- Central controller fault or configuration change
- Building management system work that disturbed the integration
Notice how many trace to work on the controls rather than the air conditioning. A BMS upgrade, a replacement controller, or network changes during a fit-out are all common origins — and they are rarely connected to the HVAC fault that appears afterwards.
What happens if you leave it
The system drifts.
Without central control, zones run on whatever they were last told. Scheduling stops. Setbacks stop. Energy consumption typically rises, quietly, because unoccupied space keeps being conditioned.
And the next real fault — a compressor problem, a drain fault, a refrigerant issue — surfaces through a tenant complaint rather than a monitoring alert. In a building with many zones, that delay is where costs accumulate.
What we check
- Use the sub-code to identify which module reported the error.
- Inspect network cabling and terminations between the system and the central controller.
- Verify indoor unit addressing — errors here are a frequent cause.
- Check central controller configuration and confirm it matches the installed system.
- Test remote controller communication where those are involved.
- Establish what changed — controls work is usually the origin.
- Test the central controller itself once cabling and configuration are confirmed.
What you can tell us before we arrive
- Has any work been done on your building controls or BMS? The most useful thing you can tell us.
- Are the units still running? Distinguishes a control-layer problem from something broader.
- Has anything been re-addressed or reconfigured recently?
- The sub-code, if shown — it identifies the affected module.
Related codes
- 237 — Indoor to outdoor communication PCB error. Unit-level communication rather than the control layer.
- 03 — Zone controller to indoor unit communication. Another control-layer fault, one level down.
Get your visibility back
We are certified on LG, Daikin and Mitsubishi VRF platforms, and we service systems we did not install.
Next business day service for commercial VRF.
Related codes
Frequently asked questions
What does error code 242 mean on an LG Multi V system?
A network error at the central controller. The system has lost communication with the central control interface, or there is a communication defect involving a remote controller. The air conditioning units themselves may continue operating normally. What you lose is oversight rather than cooling.
Will my air conditioning still work with a 242 error?
Often yes, at least initially. The units may continue running on their last instructions. What you lose is central monitoring and control, which means scheduling, setbacks and fault visibility across the building stop working as intended. Energy consumption usually rises as a result.
What do sub-codes 2421 and 2422 mean?
They identify which outdoor unit reported the network error. 2421 is the master and 2422 is slave one. On a multi-module system that narrows immediately which unit's network connection to investigate rather than checking every module. That saves real time on larger installations.
What causes a network error on a Multi V system?
Communication defects between the central controller and the system, remote controller communication problems, indoor unit addressing errors, damaged or disconnected network cabling, or a fault in the central controller itself. Addressing errors are a common and easily missed cause.
Why did 242 appear after we changed our building controls?
Because central controller integration is where this fault usually originates. Work on building management systems, replacement controllers, network changes, or addressing adjustments during a fit-out all commonly disturb the connection this code monitors. The HVAC fault is rarely connected back to the controls work that caused it.
How much does a 242 error cost to fix?
Usually toward the lower end. Most cases resolve to network cabling, addressing configuration, or controller settings rather than replacing hardware. Cost rises only where the central controller itself has failed and needs replacement. Most cases are technician time rather than parts.