--- title: "myUplink" description: "myUplink is a Marketplace integration for Home Assistant. It has 614 installs sharing analytics, needs the vendor's cloud and was last updated October 5, 2026." canonical: "https://vulpo.app/integrations/marketplace/jaroschek-home-assistant-myuplink" url: "https://vulpo.app/integrations/marketplace/jaroschek-home-assistant-myuplink.md" last-updated: "2026-10-22" version: "1.4" --- # myUplink > myUplink is a Marketplace integration for Home Assistant. It has 614 installs sharing analytics, needs the vendor's cloud and was last updated October 5, 2026. myUplink is a custom integration that brings devices and sensors from a myUplink account, including NIBE systems, into Home Assistant. It talks to the vendor's cloud and signs in through the vendor's own sign-in page, with setup done in the UI. It provides binary sensors, climate, numbers, selects, sensors, switches, updates and water heaters, including a connection state, thermostat, notifications and firmware update. A Smart Home Mode select and optional smart home zone support can be turned on, along with firmware and notification fetching, each of which costs extra API calls. Expert settings allow overriding the platform or writable state of a parameter, limiting the requested parameters to a whitelist, or adding extra parameter IDs. Two actions set a device parameter to a value or set a property on a smart home zone. Automatic summary of the README and code of jaroschek/home-assistant-myuplink. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=jaroschek&repository=home-assistant-myuplink&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=jaroschek&repository=home-assistant-myuplink&category=integration) ## Supports - **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor. - **Sign in with the vendor**: Connects through the vendor's own sign-in page. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Options - **Enable Smart Home Mode?**: The Smart Home Mode is a system related entity in the myUplink API. If a system has only one single device, the Smart Home Mode will be added to this device. Otherwise the Smart Home Mode will be added to an additional device, that is based on the available system information. The support of the Smart Home Mode requires one additional API call per system. - **Fetch Firmware Info from API?**: Requires an additional API call per device. - **Fetch Notifications from API?**: Requires an additional API call per system. - **Scan Interval (seconds)** - **Keep disconnected parameters available?**: Show parameter entities of disconnected devices as available. - **Expert Mode**: Configure advanced options. ### Expert Settings - **Platform Overrides**: Force a specific platform for a given parameter ID. This is sometimes necessary if the myUplink API provides incorrect parameter data and the integration detects the wrong platform. Must be valid JSON. To restore the default, invalidate the field and save. An empty field will cause no change. - **Writable without Premium**: When you do not have a Premium subscription and are not able to write parameter values, create writable entities in Home Assistant anyway This is enabled by default to avoid issues with lapsed subscriptions, non-Premium users adding subscriptions, and the possibility of myUplink providing manage permissions unilaterally. - **Writable Overrides**: Set specific parameter to writeable or not writeable. This is sometimes necessary if the myUplink API provides the wrong state for the paramter option writable. Must be valid JSON. To restore the default, invalidate the field and save. An empty field will cause no change. - **Parameter Whitelist**: Restriction of the requested parameters to a specific list of parameter IDs. This can be useful if the myUplink API provides an extremely large number of parameters, some of which are unimportant, and you want to restrict the available list of parameters. List of parameter IDs separated by commas. An empty list does not result in any restriction. Must be valid JSON. To restore the default, invalidate the field and save. An empty field does not result in any change. - **Additional Parameter**: Add additional parameter IDs to the query. In extremely rare cases, the myUplink API does not provide all available parameters. With this list, it is possible to add known parameter IDs, which are then queried directly. Comma-separated list of parameter IDs. An empty list does not result in any restrictions. Must be valid JSON. To restore the default, invalidate the field and save. An empty field does not result in any changes. ### After setup - **Enable Smart Home Mode?**: The Smart Home Mode is a system related entity in the myUplink API. If a system has only one single device, the Smart Home Mode will be added to this device. Otherwise the Smart Home Mode will be added to an additional device, that is based on the available system information. The support of the Smart Home Mode requires one additional API call per system. - **Enable Smart Home Zone?**: Requires an additional API call per device. - **Fetch Firmware Info from API?**: Requires an additional API call per device. - **Fetch Notifications from API?**: Requires an additional API call per system. - **Scan Interval (seconds)** - **Keep disconnected parameters available?**: Show parameter entities of disconnected devices as available. - **Expert Mode**: Configure advanced options. - **Platform Overrides**: Force a specific platform for a given parameter ID. This is sometimes necessary if the myUplink API provides incorrect parameter data and the integration detects the wrong platform. Must be valid JSON. To restore the default, invalidate the field and save. An empty field will cause no change. - **Writable without Premium**: When you do not have a Premium subscription and are not able to write parameter values, create writable entities in Home Assistant anyway This is enabled by default to avoid issues with lapsed subscriptions, non-Premium users adding subscriptions, and the possibility of myUplink providing manage permissions unilaterally. - **Writable Overrides**: Set specific parameter to writeable or not writeable. This is sometimes necessary if the myUplink API provides the wrong state for the paramter option writable. Must be valid JSON. To restore the default, invalidate the field and save. An empty field will cause no change. - **Parameter Whitelist**: Restriction of the requested parameters to a specific list of parameter IDs. This can be useful if the myUplink API provides an extremely large number of parameters, some of which are unimportant, and you want to restrict the available list of parameters. List of parameter IDs separated by commas. An empty list does not result in any restriction. Must be valid JSON. To restore the default, invalidate the field and save. An empty field does not result in any change. - **Additional Parameter**: Add additional parameter IDs to the query. In extremely rare cases, the myUplink API does not provide all available parameters. With this list, it is possible to add known parameter IDs, which are then queried directly. Comma-separated list of parameter IDs. An empty list does not result in any restrictions. Must be valid JSON. To restore the default, invalidate the field and save. An empty field does not result in any changes. Texts from the code of [jaroschek/home-assistant-myuplink](https://github.com/jaroschek/home-assistant-myuplink). ## Entities - **Binary sensors**: Connection State - **Climate**: Thermostat - **Selects**: Smart Home Mode - **Sensors**: Notifications - **Updates**: Firmware ## Actions - **Set device parameter to value**: Service for setting any parameter identified by ID for a specific device to the desired value. Fields: myUplink Device, myUplink Parameter ID, Value - **Set smart home zone property to value**: Service for setting a property identified by its name for a specific smart home zone identified by ID of a device to the desired value. Fields: myUplink Device, myUplink Smart Home Zone ID, Property Name, Value ## From the README > Custom Home Assistant integration for devices and sensors in myUplink account. > > This integration should work with most smart devices from brands listed here. From the README of [jaroschek/home-assistant-myuplink](https://github.com/jaroschek/home-assistant-myuplink#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Climate](https://vulpo.app/integrations/category/climate.md), Heat pumps and air conditioning - Brand: [NIBE](https://vulpo.app/integrations/nibe.md) - Number: 614 installs sharing analytics; 71 GitHub stars - Connection: Needs the vendor's cloud - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: 1.8.5, last updated October 5, 2026 - Domain: `myuplink` - Source: - Issues: - Screenshot: https://vulpo.app/integrations-img/094e6157820e68b0.webp (from jaroschek/home-assistant-myuplink's README) In Vulpo: Quick Toggle card, Climate card, Select card, Chart card, Apple Watch, Control Center, Climate Live Activity (Pro) [Widgets & Live Activities in Vulpo](https://vulpo.app/features/widgets-and-live-activities) ## Other ways in for NIBE | Name | Kind | Installs or stars | Connection | Upkeep | | --- | --- | --- | --- | --- | | [myUplink](https://vulpo.app/integrations/core/myuplink.md) | Built-in integration | 1.6k installs sharing analytics | Needs the vendor's cloud | Part of Home Assistant | | [Nibe Heat Pump](https://vulpo.app/integrations/core/nibe-heatpump.md) | Built-in integration | 1.1k installs sharing analytics | Works locally | Part of Home Assistant | | [NIBE Energy Conversion](https://github.com/VitisEK/nibe_energy_conversion) | Marketplace integration | 6 installs sharing analytics | Works locally | No update in 6 to 18 months | | [Nibe service USB gateway](https://github.com/tumik/ha-nibe-service-usb) | Marketplace integration | No installs sharing analytics yet | Works locally | Updated in the last 6 months | | [Nibe Price Optimizer](https://github.com/thundrM/nibe-price-optimizer) | Marketplace integration | No installs sharing analytics yet | Works locally | Updated in the last 6 months | Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/jaroschek-home-assistant-myuplink --- - HTML version of this page: https://vulpo.app/integrations/marketplace/jaroschek-home-assistant-myuplink - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml