Skip to content
Home Assistant TestFlight
Climate

myUplink

myuplink

Built inCloud polling

The myUplink integration lets you get information about and control heat-pump devices supporting myUplink using the official cloud API.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
switchSwitch or outlet
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature)
selectMode picker (as switches)

What people report

Nibe and other heat pumps work through the myUplink cloud, with model-specific entity mapping. Firmware updates often change or drop entities.

  • Works2
  • Partly works2
  • Not working1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Nibe F-series heat pumpsWorks CloudMore F-series models mapped to reduce irrelevant entities
Saved copy
Proposed change After firmware upgrades and changes in the API many F-series appliances generate lots of irrelevant entities in this integration. This was taken care of for the F730 model in a previous PR. Now it is clear that all F-series appliances are affected and all such models are treated the

Excerpt saved from GitHub on 2026-10-23.

PR #130283 · 2024-11
Nibe SMO 20Works CloudAdditional entities enabled for this model
Saved copy
Proposed change Enable additional entities on heat-pump model SMO20. Please consider this PR for next patch release. No new functionalty, just additions of already existing entities to a specific model series. ## Type of change <!-- What type of change does your PR introduce to

Excerpt saved from GitHub on 2026-10-23.

PR #131688 · 2024-11
Nibe F1155Partly works CloudFirmware 9718R2 caused unit and state class repair items
Saved copy
Not sure if it's related, but after updating to firmware 9718R2 on a F1155-16 heatpump, I'm also getting repair items for unit change and longterm statistics unavailability for 'F1155-16 Time factor add heat' (sensor.f1155_16_time_factor_add_heat).

Excerpt saved from GitHub on 2026-10-23.

Issue #147981 · 2025-07
Nibe F1245-PCPartly works CloudFirmware 9699R4 removed data point 43115; other entities appeared
Saved copy
The problem I'm seeing a problem getting reported with myUplink. I think it started happening when I updated my heatpump (Nibe F1245PC) to the latest firmware (9699R4), but I am not 100% sure about that, I only noticed it just now while I updated the firmware a little while ago. It seems to be complaining about key `43115`, which might be a new key they introduced. ### What version of Home Assistant Core has the issue? core-2024.7.0b3 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration …

Excerpt saved from GitHub on 2026-10-23.

Issue #120780 · 2024-06
Nibe SMO 40Not working CloudMany entities vanished after firmware 9718r2
Saved copy
The problem After updating the smo40 to firmware 9718r2, a lot of the entities are no longer available in the integration. ### What version of Home Assistant Core has the issue? core-2025.6.3 ### What was the last working version of Home Assistant Core? Core-2025.5 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Myuplink ### Link to integration documentation on our website https://www.home-assistant.io/integrations/myuplink ### Diagnostics information config_entry-myuplink-01J839DCBTMNZ3KTSEM4M4Q3KJ.json ### Example YAML snippet [code] ### …

Excerpt saved from GitHub on 2026-10-23.

Issue #147981 · 2025-07

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Cloud polling

Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.

Details

Installs (analytics)1,584 (0.22%)
Quality scaleSilver
Added inHome Assistant 2024.2
Set up in the UIYes
Maintainers@pajzo, @astrandb

Limitations from the docs

  • The integration makes the best effort to map data-points from the API to relevant entities in Home Assistant. However, some sensors may not appear for certain heat-pump models, or in other cases, numerous irrelevant entities might be created. Please create an issue on GitHub and include a diagnostic download file from …
  • Entity names are available in English and cannot be automatically translated by Home Assistant. The reason is that the names are defined by the API and can be changed by updates of the API or the firmware in the appliance. However, most entity names are self-explanatory, e.g., "Room temperature (BT50)".

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.