766 on an alpha innotec heat pump: compressor's functional range: Operation for 5 minutes outside the compressor's functional range; resets after max. 2 h
Short answer
On an alpha innotec heat pump, 766 means: compressor's functional range: Operation for 5 minutes outside the compressor's functional range; resets after max. 2 h. The heat pump stops until the fault clears or is reset. An engineer is needed to fix the cause.
Reviewed 23 September 2026 · 1 source
What it means
The manual says: compressor's functional range: Operation for 5 minutes outside the compressor's functional range; resets after max. 2 h.
When it shows: Operation for 5 minutes outside the compressor's functional range; resets after max. 2 h.
Likely causes:
- Operating conditions outside compressor envelope.
Is it safe?
| Does the heat pump stop? | Yes |
|---|---|
| Severity | Fault — clears by itself when the condition goes |
| Engineer needed? | Yes |
The heat pump stops until the fault clears or is reset.
Resetting itself: yes.
Manual reset: automatic.
What you can check
- Note the error number and text shown on the Luxtronik display.
- The controller resets this automatically after the stated time - wait for the automatic restart before calling.
- Acknowledge the message by pressing the rotary pushbutton for about 7 seconds (as the Luxtronik manual permits); if the same error reappears, contact your installer or ait customer service with the error number.
- Check the heat pump breakers/isolator at the consumer unit are on (do not open any casing).
What the engineer will check
- If a ZWE (additional heat generator) is present, switch it on for heating.
Who to ask for: F-gas certified refrigeration / heat pump engineer (R290 flammable-refrigerant competence for propane units such as LWD).
Certification: F-gas certification (R407C/R410A units); flammable refrigerant training for R290 units.
What you might notice
Sources
- Operating manual Luxtronik heating and heat pump control Part 2 (UK) 83055400lUK - 2.1 ↗ · 83055400lUK 2.1 · page 54 · Reviewed 23 September 2026
A code explains what the controller detected, not a confirmed root cause.
Reviewed: 23 September 2026