UPC Connect Box UI changed for Vodafone customers

[robotastic-io]

The problem

Hi,

Vodafone updated the ui for its customers on the UPC Box so the integration is not able to login and retrieve the device information. Let me know if I can support you with any additional information.

What version of Home Assistant Core has the issue?

core-2022.5.2

What was the last working version of Home Assistant Core?

Does not matter. Target system changed

What type of installation are you running?

Home Assistant OS

Integration causing the issue

UPC Connect Box

Link to integration documentation on our website

https://www.home-assistant.io/integrations/upc_connect/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Error received on 123: Server disconnected
22:05:33 – (FEHLER) /usr/local/lib/python3.9/site-packages/connect_box/__init__.py - Die Nachricht ist zum ersten Mal um 19:14:47 aufgetreten und erscheint 342 mal
Can not login to x.x.x.x: Server disconnected
22:05:22 – (FEHLER) /usr/local/lib/python3.9/site-packages/connect_box/__init__.py - Die Nachricht ist zum ersten Mal um 19:14:47 aufgetreten und erscheint 342 mal

Additional information

No response

[probot-home-assistant]

upc_connect documentation
upc_connect source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @pvizeli, @fabaff, mind taking a look at this issue as it has been labeled with an integration (upc_connect) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[pvizeli]

I guess they also change the API. The integration don't login over the UI

[fabaff]

I don't have access to a device that uses the Vodafone modification or their firmware.

[robotastic-io]

I had a look at the code and the API. The tokens are passed as a cookie now. The rest seems quite similiar apart from a few changes. I created a pull request, that should work for both the old and the new version, but I can't test it with the old version.

home-assistant-ecosystem/python-connect-box#28

I'm not a python dev so feedback is welcome

[tams9]

Hi, I can see the modified connect_box/init.py file in the link. I can see green and red highligted lines. I assume green is new code to insert and red lines are the old ones to remove.
I was looking for connect_box/init.py file in my Home Assistant server to update manually and try the modifications, but did not find the same named file.

Could you please help me applying the changes?

Unfortunately in Hungary also Vodafone upgraded the firmware, which destroyed my presence detection.

Thank you in advance!

[philharmonie]

Any updates?

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[fabaff]

Without access to a device that uses the firmware in question there is not much I do. Usually the providers do not publish documentation or know what they have as they do not do the firmware development by themself.

Pretty much the only way get support is if one contributes to the Python module or me having permanent access to a device.

[kvalev]

@fabaff Already did home-assistant-ecosystem/python-connect-box#31 ;)

I also have the patch for the upc_connect plugin ready, but first the above PR needs to be merged and a new version of the library needs to be released to PyPI.

For what is worth I am running my patched version for about a week now without any problems.

[birdie60]

I have the same errors "Error received on 123" and "Error received on 123: Server disconnected" from components/upc_connect/device_tracker.py:69 in my log many times and since long.
Pls tell me if I can be of help!

[kvalev]

@birdie60 Until the fix is upstreamed you can use my patched integration. Details how to install it are in the readme. https://github.com/kvalev/upc_connect

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[birdie60]

@birdie60 Until the fix is upstreamed you can use my patched integration. Details how to install it are in the readme. https://github.com/kvalev/upc_connect

Thanks, kvalev! FYI, I installed upc_connect v2, but I still get this in my logs:
Error received on 123:

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.