Warning: Set device name with HOOP broken - Athom has changed CLI authentication code+secret

[Joka]

Edit: My first assumption here that the update to 8.1.4 was the reason is wrong. The reason for the broken function is explained below in the threat.

This is a warning to user who use this feature of the HOOP App with a Homey version before v8.1.4:

I use the HOOP app to change device names dynamically very often.

It worked perfectly, but since I installed Homey version 8.1.4. the device names no longer change.

A test of the Set card results in the following error:

To be clear: This is not a criticism of the HOOP app!

Because I did not change anything else it seems to be a problem in combination with v8.1.4.

[Arie_J_Godschalk]

Perhaps this has something todo with it:

Https://api.athom.com/oauth2/token failed, reason: read ECONNRESET

Is there anyone who can help me. When I try to log in to my Homey Pro in NodeJS everything looks normal, but when I enter NodeJS again I see the following error message: request to https://api.athom.com/oauth2/token failed, reason: read ECONNRESET. I had the same error last week, then I deleted and reinstalled the Homey SDK. This doesn’t help now. The screen in the web browser when logging in says that everything is fine, but the token that is returned seems to be rejected.

[Peter_Kawa]

I’m sorry, but it also happens with my Homey on firmware v8.1.3 ?
I think you got your conclusions a bit too quick

@Peter_Kawa

I just installed HOOP and I can’t enter a AVD’s name, there’s no dropdown list (when it should appear that is), and the same error pops up.

[Arie_J_Godschalk]

Yeah, athom has changed there CLI authentication code and secret, so it aint working at the moment

[robertklep]

@Arie_J_Godschalk

athom has changed there CLI authentication code and secret

There was a reason for that:

[Arie_J_Godschalk]

@robertklep

There was a reason for that:

Yeah i know, but that wasn’t hoop, since Arhom knew very well i was using the CLI authentication (during login once), and rejected that from the store. But they specificly said i was allowed publish the app somewhere else (like the HCS).
Also, i only used CLI during setup, after that, hoop only uses the athom-api.

[Joka]

@Peter_Kawa

I’m sorry, but it also happens with my Homey on firmware v8.1.3 ?

I have changed the title and my first statement so that no one is misled.

But good to know that the update is not the reason.

[Peter_Kawa]

@robertklep

There was a reason for that:

Yeah, and Athom concluded this should’ve been the main reason

@MaxvandeLaar

To clarify Athom pointed to the HCS as the cause. There has not been any changes to the hcs app recently. So I cannot comment on if the hcs was really the cause.

If it indeed was the hcs app then I am sorry, however, I have asked multiple times for (api) keys the hcs could use. This all could have been prevented easily. If only they put their money where their mouth was.

[robertklep]

I wasn’t implying that HOOP was the reason, apologies if it looked like I was

[Peter_Kawa]

Hi Robert, you weren’t indeed, but while Athom already made clear what was causing the issue according to them, I just wanted to point that out