myuplink.com Support

[mhuber77]

Hi,

today i received an email from nibe. I can swap to their new portal [https://myuplink.com]. Do you support this portal too or is it planed to upgrade the adapter!?
thanks and best regards
markus

[mhuber77]

I know in this adapter myuplink isn't supported, but nibe will discontinue nibeuplink for all their pumps....

[sebilm]

I did not receive such a mail from nibe but if my F1245 will work with myuplink, I will support it.

[m-s-b]

Sounds good ;-) F1245 is supported. I also didn't receive any information, but you can Log in withe the Same credentials and nibe will convert IT.

[sebilm]

@m-s-b
Do you know if you can operate myUplink and Nibe Uplink with one heat pump at the same time? Will Nibe Uplink continue to work with my heat pump if I register it with myUplink?

[m-s-b]

@sebilm
Nope, weiß ich nicht, hab mich nicht getraut meinen Nibeuplink-Account zu riskieren.
Evtl. hat @mhuber77 ja mehr Infos dazu. Im Zweifel teste ich nächste Woche mal was passiert wenn ich einen MyUplink-Zugang anlege.

[mhuber77]

@m-s-b Do you know if you can operate myUplink and Nibe Uplink with one heat pump at the same time? Will Nibe Uplink continue to work with my heat pump if I register it with myUplink?

As I know you can only use nibeuplink or myuplink with one pump. I think you need to rewrite the adapter to support both APIs, there also an API for myuplink available, see https://dev.myuplink.com/login

[sebilm]

I couldn't add my heat pump to myuplink, but I found a way to read out the demo system. I think I will write a new adapter for myuplink. I will then link it here.

[mhuber77]

befor you can add your pump, you need to update your pump/system, in my case i found the update here -> [https://www.nibe.eu/de-de/nibe-uplink-to-myuplink?HPModel=nibe-e8]

[FlorianSchulze]

I couldn't add my heat pump to myuplink, but I found a way to read out the demo system. I think I will write a new adapter for myuplink. I will then link it here.

Sebilm, i just started a new fresh installation with a NIBE S1255 on myuplink.com - no longer compatible with older versions. maybe I can provide you access to this system as a small support to your work? we do not urgently need a solution, just started the setup and integration in iobroker is planned for in advance - so just if that would help, let me know,
cheers,
florian

[sebilm]

@FlorianSchulze Thanks, but I can use the demo system from Nibe. I'm already in the process of writing a new adapter.

[sebilm]

If anyone wants to test it, the adapter is available via GitHub: https://github.com/sebilm/ioBroker.myuplink.git

Unfortunately, myUplink does not send back a refresh token, so the adapter currently only runs for one hour and then you have to get a new AuthCode.

[FlorianSchulze]

If anyone wants to test it, the adapter is available via GitHub: https://github.com/sebilm/ioBroker.myuplink.git

Unfortunately, myUplink does not send back a refresh token, so the adapter currently only runs for one hour and then you have to get a new AuthCode.

will do and start it tonight. any debug-log you want or just "sniff" if it works basically?

[FlorianSchulze]

[FlorianSchulze]

First view, works as expected. The naming of the parameters seems to be missing, but is understandable. Heating system is detected automatically and without any issues from the first view.

[mhuber77]

sorry I can't test with my pump, I've troubles to upgrade my pump to support myuplink, nibe support case is open...I'm not sure if they fix the problems during the holidays

[sebilm]

@FlorianSchulze Does it work longer than one hour without relogin?
I think the naming is correct, but your object tree does not show the whole name but only the first letter. I choose the IDs of the system, the device and the data points as IDs for the objects in the objects tree because these are the only unique IDs.

[FlorianSchulze]

@sebilm no - as you mentioned it raises errors after one hour. One detail, the status "connected" stays "true", so from data perspective you dont see the system is detached. But you see it in the logs and the adapter status. So, briliant work for the first approach! Guess, Prio is token now, cant believe there is no solution from nibe to manage TTL from the token by getting a new one?

[sebilm]

I am waiting for an answer from myuplink support.

[sebilm]

I have opened an issue directly at the new adapter for further discussions - please continue to discuss there:

sebilm/ioBroker.myuplink#1