Heat pumps

For heat pump manufacturers: the dealer commissions the plant, not the homeowner app

The household app sets a room temperature. It does not know the safety limits of the refrigerant circuit. The manufacturer hears about faults late when the dealer only gets in through a VPN, a browser page, or a platform they do not control. The project is the tool for dealers and service.

Book a technical assessment (opens Calendly in a new tab)
Andrej Albrecht
30 minutes, technical assessment
First release, one family
Heat pump controller Dealer
Service app for one controller generation Android · iOS
Manufacturer service

Refrigerant circuit and safety limits stay in the controller. A backend only when the record has to reach the manufacturer.

Typical technology Bluetooth LEservice parametersAndroidiOS What each interface yields

Service is not a room setpoint

Public manufacturers already ship homeowner apps. The opening is the dealer who needs to set parameters, run a new controller generation, or read a fault.

The homeowner app heats

It sets the room. It does not commission the circuit.

The dealer arrives the long way

A VPN, a browser page, or a group platform the manufacturer does not run.

A new controller generation

The current app does not cover it. Dealers stay on the old path.

What the manufacturer learns too late

The fault is already at the customer before service can see it.

The technician's day · Dealer · Heat pumps

Without the app

  1. 1 Installer on site, laptop or VPN missing
  2. 2 The plant stays on factory values
  3. 3 The household reports a fault
  4. Service guesses on the phone

With the app

  1. 1 Installer pairs with the controller
  2. 2 Set the released parameters
  3. 3 Read the fault record
  4. The limits stay in the device
  • Commissioning waits on site. While the laptop or the VPN is missing, the plant stays on factory values.
  • The household reports, service guesses. Without the fault record from the controller, the phone call is a guess.
  • Subsidies and costs for homeowners. That is a different topic. This page is for the manufacturer, not the homeowner.

Why the homeowner app and EEBUS are not commissioning

First question: is the app needed at all? If a product already does the workflow, the assessment ends there.

Buy packaged or build

Can a packaged product already do the workflow?

A packaged product is enough

Products named: myUplink, EEBUS, agency or embedded team
  • The manufacturer already runs a service platform
  • An agency or embedded team builds the service workflow
  • A homeowner app is the goal

A custom app is worth it

One family, one workflow, first release
  • Dealers arrive through VPN or browser
  • A new controller generation has no tool
  • The fault reaches the manufacturer too late

If yes, the assessment ends there. No second platform beside a product that already does the workflow.

myUplink or EEBUS

Remote access and interfaces may already run. They do not replace setting the service parameters on this plant.

A smart-home app

It does not know the refrigerant circuit or the safety limits.

An agency or an embedded team

If they already build the service workflow, that is the path. The opening is the manufacturer whose dealers still depend on a VPN.

What the service app does in the first release

A tool for the dealer on one controller generation. The circuit and the limits stay in the device.

Device, app, system · Heat pumps
Today
Heat pump controller Dealer
manual
VPN, browser page, group platform, laptop
The fault is at the customer before service can see it
Manufacturer service
First release
Heat pump controller Dealer
Service app for one controller generation Android · iOS
Manufacturer service
Commissioning: released parametersRead the faultNot the heating app

Boundary: Refrigerant circuit and safety limits stay in the controller. A backend only when the record has to reach the manufacturer.

Commissioning

Parameters you release for the dealer.

Read the fault

The record service needs before anyone guesses on site.

Not the heating app

No room setpoint for the household, and no design award.

Interfaces of the device family

A tool for the dealer on one controller generation. The circuit and the limits stay in the device.

Interfaces of the device family · Heat pump controller
Device speaks
Bluetooth LEClose range at the controller
Service parametersThe list you release
Path today
VPN / browserThe dealer path today
Packaged product
myUplink / EEBUSRemote access and interfaces keep running

MyStiebel and OCHSNER are not our work.

How the work runs

Discovery. The assessment asks how the dealer reaches the controller today and which parameters commissioning writes. If that is already a platform the manufacturer runs, the scope ends there. We do not build a homeowner app in this step.

  1. 2

    The dealer path

    VPN, browser, or a missing service tool. Only the last one is an app project.

  2. 3

    Released parameters

    The list the dealer may set. Limits stay in the controller.

  3. 4

    Test on site

    Pairing or the access that already exists, a dropout, one fault record.

  4. 5

    One generation

    Not the whole brand, and not the household.

Why Albrecht Apps

No heat-pump reference. Safety limits and the refrigerant circuit stay in the controller.

Named work from another industry

iTENDO · INNIRION · 2019 to 2024

From 2019 to 2024 Andrej Albrecht built the Android app for iTENDO: Bluetooth LE to sensors on an industrial tool holder for INNIRION. That is not a project in the industry on this page. Hardware and firmware stay with the manufacturer. Albrecht Apps takes the app, the backend, and the cloud.

Bluetooth LEAndroidTool holder, other industry
Example, not a client project

Commissioning at the dealer

The installer sets the released parameters of the new controller generation and reads the fault without a VPN on a laptop. The limits of the circuit stay in the device.

The published IIoT article describes how a tablet companion app could be built today. It is a method article, not a delivered client project, and not evidence for this industry.

App development. BLE app development.

Questions before a project

myUplink or EEBUS already handles remote access.
Then watching the plant from afar is not the project. What can remain is whether the dealer still sets this generation service parameters somewhere else.
We already have an agency or an embedded team.
If they build the service workflow, you do not need us. The assessment is for the path that is still a VPN or a browser.
Is this about costs and subsidies for homeowners?
No. That is a homeowner topic. This page is for the manufacturer and does not advertise a household app.
Does the service app need its own cloud?
Not in the first release, if the controller can be reached on site. A backend is added only when the record has to reach the manufacturer.

Commissioning, not the household

Bring how the dealer reaches the controller today. If that is already your platform, we will say so.

Book a technical assessment (opens Calendly in a new tab) 30 minutes with Andrej Albrecht. Opens Calendly in a new tab.

Three points the assessment settles:

01Commissioning: released parameters
02Read the fault
03Not the heating app
Andrej Albrecht, Albrecht Apps GmbH
30 min technical assessment Book a technical assessment (opens Calendly in a new tab)