MyUplink binding?

[helander (Lars-Erik Helander)]

I am looking for a binding for Nibe myUplink devices, but fail to find any binding (not uplink but the newer myuplink). In case you know of any such binding I would greatly appreciate a ”pointer” to it.

[elektrolubach (Jonathan Lubach)]

Hi helander,
in some other Threads there are some discussions about it. I am also reading it with interest as I have NibeUplink running which will be presumably switched off this year after reading the messages from Nibe:

Nibe Uplink REST API Binding [3.3.0;4.2.0)

@pacive, lately when I access the NibeUplink portal, I get spammed with notices to upgrade my machine, and switch over to MyUplink. Afraid of NIBE shutting down the old service in the near future; do you get the same, and have you been able to take a look into the new API? Digging around, I hear the API is quite similar to the old one. And for the new one, they at least have “some” documentation: Swagger UI

Nibe uplink binding

Hi @AlexF, any thoughts about update the Binding to support MyUplink? I’m using your current Binding with my F2040-8/VVM320 and ERS20-250, but I received an Email from NIBE, that I could migrate to the newer MyUplink instead of Uplink. I think they want to support only one firmware and Webportal in the future. Thanks a lot and keep up the great Work Best regards Tobias

Cheers
Jonathan

[vavo01 (Valentin Voth)]

Hi @helander,
I’ve been using the official nibe uplink binding for a while. Then switched to nibe uplink rest api binding.
Since the move to MyUplink I use iobroker.myuplink adapter running in parallel as interim solution. It’s quite reliable and has all essential channels to monitor and control my VVM500.

[AlexF (Alexander F)]

Hi there I started working on a myUplink binding. It is still in an early state. Currently it supports:

• automatic discovery of units within the account
• automatic detection of available channels per dervice
  • no write support currently
  • status/enum channels are just mapped as numbers currently

Compared to the old NibeUplink I miss a few channels. In addition it seems that some channels are not updated unless the heatpump is restarted (such as heat meters) I already reported this to NIBE. If others have similar issues I would recommend to report this as well. It seems that their firmware still has some issues.

Current version can be found here:
myUplink SNAPSHOT Download

[Andreas_Bierfert]

Thanks for providing.

Dropped into M2, added bridge, discovery of my VVM500 worked like a charm, values are populated.

[shotte (Ralf)]

Tahnk you for sharing, but I have some trouble using it:

• successfully migrated today my VVM500 to myuplink; it is shown there

• added your latest 4.2 SNAPSHOT to my 4.1.2 openhab installation

• added bridge with my login data for myUplink
  → no successful login possible
  → UNKNOWN: @text/status.waiting.for.login to OFFLINE (CONFIGURATION_ERROR): Bad Request

• checked permissions in myuplink account
  → no Third-Party Apps listed

Do you have any further instructions for me?
Do I need openhab 4.2 snapshot version?
If yes, could you provide a 4.1 version too?
Is it possible to configure your plugin via textfiles?

[shotte (Ralf)]

@AlexF
Meanwhile I updated openhab to 4.2M2 but again without success. After switchung your plugin to DEGUG I get the following messages repeatly every 5 seconds:

2024-05-14 12:34:41.032 [DEBUG] [ink.internal.command.AbstractCommand] - [Login] running command
2024-05-14 12:34:41.066 [DEBUG] [ink.internal.command.AbstractCommand] - [Login] received content, length: 218, encoding: UTF-8
2024-05-14 12:34:41.066 [DEBUG] [ink.internal.command.AbstractCommand] - [Login] HTTP response 400
2024-05-14 12:34:46.033 [DEBUG] [link.internal.connector.WebInterface] - run queued commands, queue size is 12

[AlexF (Alexander F)]

You will need to create API credentials. Your personal User (Email + password) will not work.

[MrRusch (NA)]

Wow, have I been waiting for this… I have a CTC EcoZenith i255, so the NibeUplink binding wasn’t an option for me.
I eagerly just added your initial JAR, created an app at dev.myuplink.com to get the credentials, and discovered my device - values populated!
A HUGE thank you for spending time on this! Looking forward to coming versions. It seems you’ve got this in the bag, but let me know if there is something I can help test…

[shotte (Ralf)]

@AlexF
Meanwhile I got it working creating an APP as described by @MrRusch and performed successfully an autodiscover which worked without any trouble.
But I prefer text based configuration. Is there any documentation available?

[shotte (Ralf)]

Meanwhile I was able to create successfully text based files for account and thing configuration. The only problem I had is getting the Thing-ID for my VVM500. to be successful I simply performed the autodiscover and took the ID from there (after deleting the previously generated Bridge and Thing).

Here are my details

myuplink.thing:
Bridge myuplink:account:myAccount "myUplink" @ "Nibe Heizung" [ 
    clientId="id from dev.myuplink.com application", 
    clientSecret="secret from dev.myuplink.com application", 
    dataPollingInterval=60 
    ] {
        genericDevice VVM500 "VVM 500" @ "Nibe Heizung" [ deviceId="id taken from automatic discovery" ]
    }

myuplink.items:
Number:Temperature Nibe_Out_Temp	"Außentemperatur [%.1f °C]"	(gNibeVVM) { channel="myuplink:genericDevice:myAccount:VVM500:40004"}
...