# \[App\]\[Pro\]Toshiba AC

**URL:** https://community.homey.app/t/app-pro-toshiba-ac/126642
**Category:** Apps
**Tags:** app, official, homey-pro
**Created:** [January 5, 2025, 1:58pm UTC](https://community.homey.app/t/app-pro-toshiba-ac/126642 "2025-01-05T13:58:41Z")
**Posts on this page:** 1
**Showing post:** 42

<div class="post-metadata">

### Author: ![Henk\_Van\_de\_Streek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_van_de_streek/32/120781_2.png) [@Henk\_Van\_de\_Streek](https://community.homey.app/u/Henk_Van_de_Streek)
#### Post date: [July 21, 2026, 11:46am UTC](https://community.homey.app/t/app-pro-toshiba-ac/126642/42 "2026-07-21T11:46:08Z")

</div>

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.

---

_[View the full topic](https://community.homey.app/t/app-pro-toshiba-ac/126642)._