Switching to myUplink or not?

[bohtho]

Just a got an email from Nibe that my system can now upgrade from NibeUplink to myUplink, and is wondering whether this is a good idea feature wise, and whether this component will also now switch Nibe API?

[elupus]

This component will not. But there is ongoing work (by another) to support myuplink in home assistant. I suggest holding of a little.

[bohtho]

Thanks for valuable input!

Another somewhat related thing is that I fear, but don't know for certain before I actually switch to myUplink, that the "smart thermostats" feature is missing there. I currently pass on 3 datapoints per room/radiator in my house every time they change (through the service provided by this component and a registered application on api.nibeuplink.com), and the API does some "magic" on these and present a compound status and demand for the whole house to the heat pump.

Do you or anybody know whether it's possible to continue updating this in a somewhat similar fashion with myUplink?

[pricei]

This component will not. But there is ongoing work (by another) to support myuplink in home assistant. I suggest holding of a little. I had exactly the same question as @bohtho so I'll defer upgrading to myUplink for now. Out of interest, is the ongoing work you alluded to part of the NIBE Heat Pump integration (https://www.home-assistant.io/integrations/nibe_heatpump)?

[bohtho]

I had exactly the same question as @bohtho so I'll defer upgrading to myUplink for now. Out of interest, is the ongoing work you alluded to part of the NIBE Heat Pump integration (https://www.home-assistant.io/integrations/nibe_heatpump)?

That standard component communicates via RS483 and/or ModBus. I would assume he was referring to this one: https://github.com/jaroschek/home-assistant-myuplink

That said, I wonder whether the firmware update on our heat pumps also includes the ModBus TCP Server included in the newer S-series heat pumps. Then a direct/local connection is much easier than before (via a ModBus component like the one you linked to).

Regarding deferment of the firmware upgrade to myUplink, it is alluring to both get the seemingly much better rate limit in that API, and just possibly the local ModBus TCP server. But whether I go the route of the myUplink component or a local ModBus connection it seems I will have to do the "smart thermostats" magic on my side myself before updating the demanded temperature for the house zone (which I just assume is Current mean temperature for the house + mean(every radiator thermostat's valve position (%) x (Set room temperature - Current room temperature))))

[elupus]

Nope. There is a myuplink component merged to core for next ha release. Likely limited in feature.

[pricei]

Thanks for the information, @elupus. Until NIBE provides more information about the benefits of moving to myUplink, I'm minded to stay with your integration - it works well and provides all the data I need about my F1145.

[marcusthorstrom]

I switched yesterday to myUplink (official from 2024.2 nor HASS) and I will go back today as the smart thermostats feature is missing. I also looked at the API for myUplink vs Nibe Uplink, and there is no endpoint to set thermostats in myUplink. So unless they add that endpoint to myUplink it will not be possible to use smart thermostats.

What myUplink does better is the rate that parameters is updated, its every minute now instead. With Nibe Uplink the power consumption for the compressor and water heater was updated every 70th minute, but those values is missing in myUplink.

[AnonymousRetard]

I registered a myUplink account on the 8th of February and used the contact for to report a bug about the consumption for compressor and water heater missing. I was told they sent my request to their developers for future updates and improvements but they also told me that after summer 2024 they will close down NIBE uplink and therefore recommended me to proceed with the update I have currently held off on because of this.

I answered that I will delay the upgrade as long as possible until I am made aware that these fields now exist in myUplink as well. I don't feel so secure that it will happen but maybe it helps if more of you also try to contact NIBE about it?

[Marrrs]

I'll just add my two eurocents here since I have been hesitant moving to the MyUplink and the native HA integration for it after reading the comments here. I have a F730 and I updated it to the latest firmware, which transfered it to MyUplink. I had to wait maybe 30 min for it to show up in their app. Setting up the rest was a breeze and I was happy that the entities was aptly named so it was easy to change the automations and dashboard items as needed. I don't have a Nibe subscription so I only use HA for sensor readings. The native integration loads fast and the connection to MyUplink seems stable, for my use case the move to MyUplink has been a success without downsides.

That said, after using the hass_nibe integration also without issues for almost four years, I want to thank @elupus from the bottom of my heart. I actually found HA when looking for a way to get better readings from the F730 and I was blown away by the amount of sensors it provided. It has has been a joy to figure out how to make best use of all the data provided from hass_nibe. I have unsuccessfully been looking for a "buy me a coffe/beer" link or similar, but the next best I could come up with is just thanking the project owner for putting in so much work inte this project. Effectively it is saving money for us Nibe users, and also helps people like me with a bit of FOMO relief during the cold (read expensive) winter months up here in the north.

Thank you @elupus and other persons involved in the project!

[elupus]

It warms my heart to hear! Thanks for the writeup!

[imist]

Well said @Marrrs, I cheer in in the tribute!

[Delph1]

I second the tribute to @elupus Grade A plugin and support really.

[AES-256-GCM]

I can only repeat the others in this issue and want to truly thank @elupus for the great work on this integration! Never hat problems with it and I enjoyed how feature-rich it is. What a shame that I can't use it sooner or later, anymore.

I have a F730 and updated to FW 9701R3 which got released this month.

In principal most of the sensor readings Nibe Uplink provides are there. (I have no premium abo, so I can't test if values can be modified.)

What I like about myUplink is that it provides a Swagger web UI so you can easily explore the api. This way I found out that it's still possible reading the current operating state of the heat pump. A feature I'm missing from myUplink integration. An excerpt of the API endpoint /v2/devices/{deviceId}/points using GET method:

{
    "category": "F730 E EM 3x400V",
    "parameterId": "50095",
    "parameterName": "status:",
    "parameterUnit": "min",
    "writable": false,
    "timestamp": "2024-07-07T19:23:15+00:00",
    "value": 15003,
    "strVal": "15003min",
    "smartHomeCategories": [],
    "minValue": null,
    "maxValue": null,
    "stepValue": 1,
    "enumValues": [
      {
        "value": "15000",
        "text": "starts",
        "icon": ""
      },
      {
        "value": "15001",
        "text": "runs",
        "icon": ""
      },
      {
        "value": "15003",
        "text": "off",
        "icon": ""
      },
      {
        "value": "15004",
        "text": "hot water",
        "icon": ""
      },
      {
        "value": "15005",
        "text": "heating",
        "icon": ""
      },
      {
        "value": "15006",
        "text": "pool",
        "icon": ""
      },

Unfortunately the myUplink integration only shows the values of the sensor reading and not the text information. But I guess this can be resolved by doing some manual templating work in Hass.

Current downsides for me I noticed so far are:

• sensors about the blocking state of the compressor and integrated additional heating are missing (the latter is provided on the myUplink dashboard, though, and both can be queried via the API, see above)
• there is no sensor about the currently consumed electrical power of the integrated additional heating
• myUplink doesn't categorize my F730 into different devices. There is only one devices with a bunch of sensors which makes finding the ones I need difficult.
• It seems myUplink doesn't provide data about the lower and upper bounds when the F730 starts and stops heating the water in the boiler -- the current water temperature is provided
• On the other side myUplink provides sensor readings which weren't available in nibeUplink
  • Lots of sensors about configured schedules. They are hard to distinguish since the sensors are called Start <day of week> and Finish <day of week>
  • You can find information about the currently configured heating curve

I hope these information help deciding whether switching to the new integration is suitable for you at the moment. I don't use and external equipment, so I can't tell about smart thermostats.

[SimonLeigh]

Thank you to @elupus for such a great integration and support. Worked flawlessly with my F1145 for two years. The smart thermostats integration made a big different to my home comfort once I had it working this last winter.

I have messaged NIBE letting them know that myUplink not having the API for smart thermostats is a big step back and that they should fix it. In any case, they have forced us to upgrade, but at least we can try to apply some pressure if we leverage that feature as it really affects household comfort.

[stepanv]

Hi everyone, I got an email from Nibe, that the "Connection to NIBE Uplink will be broken on August 30, 2024". My understanding is that NIBE will shut down https://www.nibeuplink.com in 3 weeks so I'm confused why you still develop and release this integration?

By any chance, does it mean, either

• you somehow know nibeuplink.com will continue to work even after August 2024
• this integration will work against myuplink.com

?

Thanks for this integration, it perfectly worked in last few years!

[elupus]

I've not upgraded my pump yet. It will not work against my uplink. Had not received a shutdown notice, so did not know about the deadline.

[nickcj931]

Yep can confirm ive just received a "Last reminder" threat from NIBE to switch or i lose all functionality "the connection to NIBE Uplink will be broken on August 30, 2024"

Joke... given the price i paid for my equipment... now i cant send dynamic Thermostat readings to influence the temperature calculation on the unit :(

Also echo everyone above thanks for all the hard work @elupus this has been such a great integration for our house and made such a difference to our efficiencies, sadly this is no more.

[bohtho]

Joke... given the price i paid for my equipment... now i cant send dynamic Thermostat readings to influence the temperature calculation on the unit :(

I totally agree. MyUplink is a halfassed product and there's a lot of daily features and data missing vs the current platform (NibeUplink). Reported product specific data points without actual data is very strange that isnt't fixed. And don't get me started on The Smart Thermostat menu item on the heatpump (inside part) now not having an impact on anything or being possible to influence. Should they remove this as well by firmware update I would be pissed as it won me over to NIBE when choosing what heat pump system to invest in. I have tried to send emails telling NIBE and the developers to just invest a few hours on MyUplink to not piss off the slightly technically interested customer base (which I think is considerate for (supposedly) connected premium heat pump systems etc.). But not even a reply. Like they are trying to forget the "connected"/web part after having outsourced the platform.

[nickcj931]

@bohtho - i have actually received a reply from myUplink its not helpful but for reference - they said they passed the feedback to developers however failed to answer any questions i had which is the same as you - I picked NIBE for the pure function of being able to pass my already in place thermostats/zones to the heatpump to essentially make it more efficient in operation - and this change has removed features which was one of main purchasing driving decisions for me (and sounds like you as well) to invest in their heat pump.

After I challenged the lack of response to that issue he suggest I contact Nibe (which is who i thought i was contacting! email address for reference help.myuplink@nibe.se)

I am actually in process of figuring out any legal path as I'm pretty sure this is a breach of consumer protection act and contract of sale in the UK.

[Delph1]

@nickcj931 MyUplink is run by a company called Myuptech AB (556633-8140), which is a subsidiary of Nibe. Why they have chosen to have this pretty crucial technology in a separate entity is beyond me, but it answers the question as to why they asked you to talk to Nibe. It's not exactly crystal clear that they are two different companies, but they are.

[nickcj931]

@Delph1 - thats interesting to know thanks for the flag will add that into the armory.... However from a consumer point of view, which is what we all are, we paid NIBE for a service and product - which is now inferior to what was purchased based on decisions they made internally. The fact that they chose to complicate their company structure isnt really a concern of ours since our business is with NIBE fundamentally.

[Delph1]

@Delph1 Agree 100%. I just wanted to add some facts and context. More people are going to get upset about this sooner rather than later. The more people that complain to BOTH companies, the better.

[nickcj931]

Hi all just wanted to put this here so other people know.

Ive heard back from myUplink team with an update this is a copy and paste from their email received 4th Sep 2024

Hi

We have discussed your feedback further within the organization and decided to introduce a similar function via our open api also on myUplink, our developers have started to look at it and hopefully we can release a function later this year, we will get back to you when we have a function ready.

Have a nice day!
Team myUplink.

Fingers crossed we can have full functionality restored!

[imist]

Sounds very interesting and promising! Which missing functions did you ask for?

[nickcj931]

Ability to pass remote thermostat function like the old uplink API used to let you do. Funny when you use words such as contractual breach things suddenly happen.... Not counting chickens yet we'll see what if anything they deliver. Ill still be sending a legal letter to Nibe when i get back from Holiday just to keep the pressure up.

My request was basically - Put the removed functionality back OR allow access to local Modbus OR I want to be compensated...

[SimonLeigh]

@nickcj931 good to hear. I will also email help.myuplink@nibe.se as I was "fobbed off" with the response they had passed it to their developers and was met with silence when I noted they would make a material difference to the comfort and warmth of my home this winter as a consequence of removing necessary features.