Hi Monique, hi all,
I found a likely cause for the current login failures.
Since around 17 July 2026, the Toshiba/Carrier cloud appears to require a Device-ID HTTP header during authentication. Requests without this header are reportedly rejected with HTTP 429 Too Many Requests (source: Home Asistant integration, where they had similar issues).
This matches the current Homey behaviour:
- all existing Toshiba devices suddenly became unavailable;
- the official Toshiba Home AC Control app required a new login;
- the Homey app shows App Unavailable;
- adding a new device hangs before the login screen appears;
- restarting Homey or reinstalling does not solve it.
The Home Assistant Toshiba AC integration has reportedly restored login by generating, storing and sending a stable Device-ID with the cloud requests.
It therefore seems likely that the Homey app needs the same change in its Axios/API headers, especially for the authentication request.
Hope this will also bring a solution for Homey users too,
Br Henk.
