Telenet stopt working

[Fifke]

After working for years , integration stopt working... Tried to delete and re-install , but now unable to login... Also the data for retrieving the DTV key seems outdated , cant find this page in my Telenet account.

[emiece]

Same

[Sholofly]

Logging?

[Nicoautoxp]

Logging?

Hi, I'm also having some issues with the integration. I've send you the log file of ha core via email. if you need anything else let me know!

[rudi159]

Hello,

About 10 days ago, lghorizon stopped working. I removed the integration in Hacs, did a full restart of HA and added the integration again via Hacs.

When adding the fresh downloaded integration to HA lghorizon i can enter my Telenet credentials but the registration is not succesfull. This is what showed up in the logfiles (short version)

2024-01-16 06:33:30.018 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Step 1 - Get Authorization data 2024-01-16 06:33:30.216 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Step 2 - Get Authorization cookie 2024-01-16 06:33:30.508 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Step 3 - Login 2024-01-16 06:33:31.831 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Obtain mqtt token... 2024-01-16 06:33:31.832 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Executing API call to https://prod.spark.telenet.tv/auth-service/v1/mqtt/token 2024-01-16 06:33:31.897 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Result API call: {'token': 2024-01-16 06:33:31.897 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] MQTT token: 2024-01-16 06:33:31.952 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Get personalisation info... 2024-01-16 06:33:31.952 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Executing API call to 2024-01-16 06:33:32.142 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Result API call: 2024-01-16 06:33:32.144 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Personalisation result: 2024-01-16 06:33:32.144 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Retrieving entitlements... 2024-01-16 06:33:32.144 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Executing API call to 2024-01-16 06:33:32.240 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Result API call: 2024-01-16 06:33:32.240 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Retrieving channels... 2024-01-16 06:33:32.241 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Executing API call to 2024-01-16 06:33:32.350 DEBUG (SyncWorker_4) [lghorizon.lghorizon_api] Result API call: 2024-01-16 06:33:32.352 INFO (SyncWorker_4) [lghorizon.lghorizon_api] 101 retrieved. 2024-01-16 06:33:32.354 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Registering boxes 2024-01-16 06:33:32.354 INFO (SyncWorker_4) [lghorizon.lghorizon_api] Box 000378-EOS2STB-xxxxxxxxxxxx registered... 2024-01-16 06:33:32.427 ERROR (SyncWorker_4) [lghorizon.lghorizon_api] Giving up connect(...) after 11 tries (ConnectionRefusedError: [Errno 111] Connection refused) 2024-01-16 06:33:32.429 ERROR (MainThread) [custom_components.lghorizon.config_flow] [Errno 111] Connection refused

@Sholofly : I forwarded you the full log file via email

Regards

Rudi

[darkpainy]

@Sholofly this is the same issue as reported in #65 currently So you can combine them.

[darkpainy]

@Sholofly I did some debugging and found the following: I noticed MQTT failures going to the domain name: obomsg.prod.be.horizon.tv which is the MQTT url from the const file of the project.

However this domain name is possibly depricated for Belgium (Telenet) looking at the logs of the telenet.tv website and is now: messagebroker-prod-be.lhp.cloud.dmdsdp.com vs

For the netherlands the (same domain name: obomsg.preprod.nl.horizon.tv but then the NL version, seems to still be supported i guess?

However, this is not the full solution because if i change the URL in the const file and use messagebroker-prod-be.lhp.cloud.dmdsdp.com I still don't get it to work...

[lpersoons]

Same problem. Integration can't get past initializing after last HA core update.

[darkpainy]

@Sholofly

For the MQTT i also see this error in the trace i took. (ps I'm trying on Pre-prod, but should be the same) I see TLSv1.2 error.

[Sholofly]

I've released a new beta version with an update for the domains. Please check them out and let me know if it works. Please add country/provider to your reaction so ican see what works and what doesn't...

[darkpainy]

I've released a new beta version with an update for the domains. Please check them out and let me know if it works. Please add country/provider to your reaction so ican see what works and what doesn't...

@Sholofly Keep in mind that for me changing the domain still leads to the error just above LTSv1.2: CA unknown. which is worrying. does this mean we now needs some certificate? or is the version not correct. I cannot investigate further without instructions

[Sholofly]

@darkpainy Can you head over to discord? My name is Sholofly over there

[Nicoautoxp]

@Sholofly I tested the beta version and it has fixed the issue for me. I did have to restart my home assistant, just reloading the integration did not work. (Telenet/Belgium) Thanks for the fix!

[Sholofly]

Lol :) @darkpainy, you are a Telenet customer too, It still doesn't work for you?

[rudi159]

The beta-version v0.5.4b1 did the trick for me too! Everything is working as before.

Thanks sholofly!

[Fifke]

The beta-version v0.5.4b1 works for me too! Everything is working again.

Thank you for the great work sholofly!

[tgilis]

Same here, Telenet/Belgium and works again with v0.5.4b1 Thanks!

[Sholofly]

I'll release a stable version soon. Thanks for testing. A part of the thank you's are also for @jsiegenthaler. He found it out before I did!