Nope, my Homey reboots every night.
Yeah same issue here. 
Iām not using Homey anymore, so it is very hard for me to maintain the app. Is there anybody who can/want to take the development of this app over from me?
@Abe_Haverkamp can you or somebody from Athom help Monique?
I would love to learn how to do that. But COBOL was my last language I used. My last line of code in 1986.
But if Athom can start a class, how too, I would love that!
His username is @Doekse though
Ofcourse always happy to guide a transfer of the app if anybody wants to take over as maintainer.
Toshiba is on our internal wishlist as well but unfortunately without any progress thus far.
Hi Abe,
We need someone who is familiar with programming Homey apps. Zou jij eens een āballletje kunnen opgooienā binnen jou netwerk? (Could you perhaps āthrow the idea outā within your network?)?
Thx,
Community developers are best found here, in the community 
If this app would become official it could live with one of our agencies but that isnāt the case at the moment
@Doekse Iām testing a fix for the known 429 rate-limit bug in the Toshiba AC app (com.toshiba): the app requested a fresh SAS token from Toshiba on every Homey restart instead of reusing it, which got Toshibaās cloud to rate-limit it. Iāve added caching + retry backoff and am testing it locally via homey app run (developer test install) on my Homey Pro.
Due to the many test pairing attempts while debugging, Iām now getting an AxiosError: Request failed with status code 429 from https://my.homey.app itself when adding the device ā so not from Toshiba, but from your own pairing cloud service. Could someone reset this rate limit for my account so I can continue testing the fix?
Oh, by the wayā¦
Iām not experienced in homey (yet) but iāve some ābasic knowledgeā on webservicesā¦ With al little help from my dear friend Claude I came to a possibel solution to the problemā¦
When iāve tested my fix I will share the solution ofcource!
Please shoot an email to partners@athom.com during my absence, Iāll be on holiday until the 3rd of August. My colleagues from the partnership team can help you out. Tell them Iāve sent you
Would also be nice @Doekse if the code could be checked by Athom? Should be a warm handover of the app from @Monique_Jilesen or does it have to be rebuild completely?
New āheatwaveā is on itās way overhere in The Netherlands, so I hope I can start my flows again soon 
If you have a fix, you can send it to me and I will (for now) fix the code and publish the app.
If there is another developer I can handover the code to him/her and also the app. No need to rebuild.
No luck yet. But when iāve got it working Iāll share the fix
Update: Iāve finished testing the fix for the 429 rate-limit bug in the Toshiba AC app (com.toshiba) and submitted it as a pull request: github.com/mjilesen/com.toshiba/pull/97
Root cause turned out to be twofold: the app was requesting a brand new SAS token on every restart instead of caching it, and it was missing a Device-ID header and BrandId field that the official Toshiba app sends (found by sniffing the official appās traffic). Both are now fixed, tested against the real Toshiba API and a full pairing flow on my Homey Pro.
@Monique_Jilesen, whenever you get a chance to take a look, thatād be great!
Toshiba AC integration stopped working - AxiosError 401 / 403 on Homey Pro
Hi everyone,
My Toshiba AC integration on Homey Pro stopped working a few hours ago and is now showing as āUnavailableā (Ikke tilgjengelig).
When checking the device logs, I see that the app is stuck in a loop trying to fetch energy data, but it gets constantly rejected by the Toshiba servers. It alternates between 401 Unauthorized and 403 Forbiddenerrors every 5 minutes.
Here is a snippet from my log:
AxiosError: Request failed with status code 401 at HttpApi.doPostRequest (/app/lib/httpApi.js:162:18)
AxiosError: Request failed with status code 403 at HttpApi.doPostRequest (/app/lib/httpApi.js:162:18)
I have tried restarting the app and using the āRepairā function to log in again, but the connection is still blocked. It seems like Toshiba might have updated their API/cloud security requirements recently (possibly requiring a missing Device-ID header).
Is anyone else experiencing this, or is there a beta/test version available that addresses this API change?
Thanks for any help or updates!
@Lloyd_Nedrum I have absolutely no ideaā¦!
Thanks, I have merged your changes and published it. The fixed version is now available.
