search

flopp999 / NIBEmyUplink-Domoticz

0 stars 0 forks source link

Hey mate, thanks for your work so far, but its not working #2

Open Mx34 opened 5 months ago

Mx34 commented 5 months ago

I have done al you say. Make a app with client identifier, a secret also, then I most generated my access code, what was a little bit different as you scribed. But whit the help of the nibe dev site even that was a success. And in my domotixz it cums up as hardware where I can al the credentials input. But after that the hardware is not shown in the list of devices and in the log it is well connecting. Something go wrong, but I don't no what?

flopp999 commented 5 months ago

Thanks, I may have been the .ZIP-file that was missing. Please download the .ZIP and try again. I will take a look at the instruction how to create an access code.

Jvsjvs commented 5 months ago

I have made an app with client identifier, a secret etc.

Generating the access code does not work for me like described. How should I get an access code?

I also do not see any NIBE hardware in my drop down list in Domoticz, also not after rebooting. How to get this Hardware visible in the drop down box?

Thank for your work!!

Jvsjvs commented 5 months ago

I have generated the access code now.

I still do not see any NIBE hardware in my drop down loast in Domoticz. How to make this virtual HW visible, what could I have done wrong?

Mx34 commented 5 months ago

I have generated the access code now.

I still do not see any NIBE hardware in my drop down loast in Domoticz. How to make this virtual HW visible, what could I have done wrong?

Hi, that's also my problem, i have an access code and I'm able to create hardware in Domoticz, but nothing appears by the devices..

eijowk commented 4 months ago

I have the same issue. Have spent some hours to get this working - but there are errors about missing categories. I think that there is something wrong in plugin.py: In the Swagger UI for myuplink for GET points its written /v2/devices/{deviceId}/points - But in plugin.py its systemId in the code for points - I think this could be at least one bug. Have tried to change it - but my knowledge of python and this code is to much on a noob level...

flopp999 commented 4 months ago

I have now done some small work, it works for me but you need to use a new Auth code everytime you restart the Hardware or Domoticz. Version 0.2 should work

flopp999 commented 4 months ago

image

Mx34 commented 4 months ago

Hello, in description you name the callback url https://api.nibeuplink.com/ but this has to be https://api.myuplink.com/ right? And is the callback url for the app the same as for the plugin and the one i use in the url for generating the access code? Thanks.

flopp999 commented 4 months ago

Hello, in description you name the callback url https://api.nibeuplink.com/ but this has to be https://api.myuplink.com/ right?

And is the callback url for the app the same as for the plugin and the one i use in the url for generating the access code?

Thanks.

I think it can be any url as long it is same in your setup as you use when getting Auth/Access code

Mx34 commented 4 months ago

Ok thanks for your answer. I have on al places the url, and i generates many access codes but is still not working. The Nibe log says the following: 2024-06-02 15:24:02.272993 Entered CheckInternet 2024-06-02 15:24:02.273473 Ping 2024-06-02 15:24:02.510684 Internet is OK 2024-06-02 15:24:02.511299 Get Token 2024-06-02 15:24:02.511591 Using reftoken 2024-06-02 15:24:02.563808 Status = 400 2024-06-02 15:24:02.615163 Disconnect called for connection 'Get Token'. Again and Again. So is this the refresh token or the access code? Thank you in advance.

flopp999 commented 4 months ago

Don't care about the refresh token, leave that field with just a few characters. You can only use the access code once, so if you used it and then restart hardware you need to create a new access code