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.