356 on a NIBE heat pump: Failed sensor calibration: Sensor calibration differs more than 2 K between BT3 and BT63
Short answer
On a NIBE heat pump, 356 means: Failed sensor calibration: Sensor calibration differs more than 2 K between BT3 and BT63. The manual does not say whether the heat pump stops. An engineer is needed to fix the cause.
Reviewed 23 September 2026 · 1 source
What it means
The manual says: Failed sensor calibration: Sensor calibration differs more than 2 K between BT3 and BT63.
Part involved: temperature/pressure sensor.
When it shows: Sensor calibration differs more than 2 K between BT3 and BT63.
Is it safe?
| Does the heat pump stop? | Not stated |
|---|---|
| Severity | Fault — needs a manual reset once the cause is fixed |
| Engineer needed? | Yes |
The manual does not say whether the heat pump stops.
Resetting itself: no/unknown - GP1 goes over to manual operation.
Manual reset: Reset from the controller alarm menu ('reset alarm' / 'Reset alarm and try again'); alarm recurs if the cause remains - NIBE: GP1 goes over to manual operation.
What you can check
- Read the alarm text and the 'info/action' help on the controller display (VVM/SMO or S-series smartguide). NIBE's manuals let the homeowner select 'reset alarm' ('Reset alarm and try again' on S-series); if the lamp returns to normal the alarm has cleared. If it comes back, do not keep resetting: select 'aid mode' ('Auxiliary operation' on S-series) if offered, so any electric additional heat keeps heat/hot water going, and contact your installer.
What the engineer will check
- Check sensor and its connections/wiring against the wiring diagram; measure sensor resistance against the NIBE temperature/resistance table; check the relevant PCB input.
Who to ask for: NIBE-trained heat pump installer (NIBE PRO / VIP).
Certification: Electrical work to BS 7671 by a competent person.
Sources
- ALARM LIST - NIBE products with Emmy display, Version 1747-1 (updated 2017-11-23) ↗ · 1747-1 · page 9 · Reviewed 23 September 2026
A code explains what the controller detected, not a confirmed root cause.
Reviewed: 23 September 2026