ha-tahoma: CozyTouch is not working anymore due to login API changes (3.0)

Did you read the instructions?

The problem

After updating the app to 3.0.0, I opened it and then some kind of update proccess are beeing made to my account (maybe also the bridge I guess).

Here is the app release note (sorry in French even when trying to for the language to Englich):

What version of this integration (ha-tahoma) has the issue?

2.8.0

What version of Home Assistant Core has the issue?

core-2021.9.6

Which gateway / hub do you use?

Cozytouch

Device model

unknown

Home Assistant log

Logger: custom_components.tahoma
Source: helpers/update_coordinator.py:227
Integration: Overkiz (by Somfy)
First occurred: 10:36:25 (1 occurrences)
Last logged: 10:36:25

Authentication failed while fetching device events data: Bad credentials

I did not get better logs after setting log level to debug

Additional information

Before the installation of the update, the hub firmware version was 2021.3.4

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 49 (14 by maintainers)

Most upvoted comments

Great !! the authentification has worked 😃 NB: I notice that the integration has taken some time to set up in HomeAssistant

I don’t know, I don’t own a CozyTouch device.

I hope to have the new CozyTouch implementation released after this weekend, which has been tested by multiple users.

It seems Android has been updated as well, I will try to add support for new CozyTouch this week.

@hewittd we agree that I had to put all files present in ha-tahoma-feature-support_custom_authentication folder in custom_components/tahoma ? Without erase all files ?

Nope, as said here https://github.com/iMicknl/ha-tahoma/issues/589#issuecomment-940495377

Here are the steps:

  1. remove your current [ha_dir]/custom_components/tahoma folder
  2. unzip ha-tahoma-feature-support_custom_authentication.zip
  3. copy the ha-tahoma-feature-support_custom_authentication/custom_components/tahoma folder
  4. paste in [ha_dir]/custom_components folder

Hello, no error at all during this day 😃

Confirmed working on my side too.

@iMicknl It’s not me but geogeocutcut did this fix on its plugin for jeedom and i adapted it for homebridge.

It seems that @davidbonan already figured this out, we will see if we can easily support this as well. (cc @tetienne)

It is a pity that CozyTouch and Nexity are all moving to different login methods. Apparently CozyTouch is using a JWT token, where Nexity is using the SSO token. We need to see if we can support all of this within our OverKiz client, or if we just use this a first time, to create a secondary Overkiz account.

context: https://github.com/dubocr/overkiz-client/pull/3/files

@steve41200 best would be to create a new issue, since the CozyTouch situation is a bit different. Happy to help you in a new issue. I think you are the first Rexel user to test this out.