search

Sholofly / lghorizon

Custom integration to control LG Horizon settop boxes for Ziggo(NL), Magenta(AT), UPC(CH), Virgin(GB, IE), Telenet(BE)
GNU General Public License v3.0
62 stars 15 forks source link

Unable to connect to Telenet TV Box #158

Open RonaldGoovaerts opened 2 days ago

RonaldGoovaerts commented 2 days ago

I had my Telenet TV Box connected to HASS using the LGHorizon integration. All was working fine till a few days ago. One action I did was to upgrade HASS to 2024.11.1, so possibly that's what broke it.

Steps to reproduce the behavior: I removed the existing TB Box Item from the HASS LGHorizon integration, then try to add it again. I'm using the login account that I'm using to login My Telenet succesfully. The DTV code I found on my invoice image

The error I get looks like this image

Version of the component: tried it with LGHorizon v0.7.4, also downgraded to 0.7.3 but get the same behavior.

Sholofly commented 2 days ago

Please check the docs and use the refresh token method to register.

RonaldGoovaerts commented 2 days ago

Thanks for your prompt reply ;-). In the JWT, I found the JWT token and I copy-pasted it into the "refreshToken" attribute (see below screenshot, BTW the token is >1300 chars long). But then I wonder what is the next steps to add the integration (that's not mentioned in the doc)? I tried to add the integration again using the account PWD, or the token instead of the password. BTW: I also noticed a DTV ID in JWT which is different then the one on my invoice, is this the one I'm supposed to use? I tried to login with using both DTV ID's, but still no luck...

image

ColinRobbins commented 2 days ago

The screenshot “paste here” confuses me! You paste the refresh token into the HA configuration screen.
The first HA screen comes up, and you select the county. Hit next. The next screen asks for a token - paste it there.

RonaldGoovaerts commented 2 days ago

Found it... Had to first upgrade back to LGHorizon v0.7.4 (instead of 0.7.3). Then the login prompt of the Integration was expecting to put the "Refresh token" (instead of the password). Then the login worked. So it seems that this change came with v0.7.4 of the integration and it's breaking the configuration of an existing integration... If so, then possibly I will not be the only one overlooking this change... Thanks for the assistance!