1KOMMA5° Heartbeat — unofficial Home Assistant integration

Hi everyone,

:warning: this integration was built entirely with AI assistance (vibe-coded).

I built an unofficial HA integration for 1KOMMA5° Heartbeat — a German home energy platform combining PV, battery, heat pump, EV charger and dynamic electricity pricing.

I was already aware of the existing hacs_1komma5grad integration, but was missing a few things - so I started this as a vibe-coding experiment, and it turned into a surprisingly complete integration.

What you get:

  • Live power sensors for PV, battery, grid, consumption, EV charger, heat pump (30 s)
  • Energy sensors (kWh) for the Energy Dashboard
  • Electricity cost & feed-in revenue sensors (dynamic pricing)
  • 30-hour price forecast + cheapest-hour attribute
  • Binary sensor: ON when price is below today’s average
  • EV charger controls (charging mode, target SoC, departure time)
  • EMS auto mode switch

GitHub:

Let me hear what you think.

Thanks & Best Regards,
Markus

1 Like

Please make it more clear at the top of the post that it was vibe-coded. Thank you.

1 Like

Hey Markus,

i am getting this error code after adding the integration.

Einrichtungsfehler, wird erneut versucht: Failed to get EMS settings: {“error_code”:30401,“correlation_id”:“hierstehteineID”,“message”:"DeviceGateway not found: No DeviceGateway found for System with ID “hierstehteineID”}

Can you help me out?

Best Regards
Lennard

Hi Lennard,

sorry, i did not track the conversation here accordingly. Better use the Issue tracker of the project.

The error “DeviceGateway not found” comes from the 1k5 API — it means the API could not find an EMS gateway registered for your system. The correlation_id is a server-side tracking ID set by the 1KOMMA5° backend, not by this integration.

This can happen if:

  • Your system doesn’t have a Heartbeat/EMS controller installed (yet)
  • The system wasn’t fully provisioned on the 1KOMMA5° backend at the time of setup
  • Hardware was recently swapped or re-registered
  • Backend error at 1k5
    Since this is a server-side issue, it may have resolved itself in the meantime — could you try removing and re-adding the integration to see if the error persists?

If it does, I’ll look into making the integration more resilient so that EMS settings are treated as optional and the setup doesn’t fail entirely when the gateway is unavailable.

BR,
Markus

Just to mention, it seems to work well as well with another set of 1k5 hardware like FoxESS Inverter and battery. Many thanks for this which integrates like a charm!
Cheers
Ansgar
P.S. Not sure, this is the right place for this.

1 Like

in general, there’s nothing really hardware specific.
The integration uses the API of 1k5 which is also used by the 1k5-app.
The Integration implements the functionality which is possible by the offered data and functionality of this interface.
It makes me happy to see that it works smoothly in other setups too.

BR,
Markus