@vmvelev works like a charm, thank you for your effort!
Would you mind looking into the Energy part of it?
Mine is reporting right now: " Energy Consumption 1 502 094 Wh"
The energy consumption sensor for the Toshiba AC unit appears to be reporting values that are scaled incorrectly by a factor of 1000.
Hey, I am glad to see it working now ![]()
Can you send a screenshot of the consumption which is in the date range before and after the update? I made a small change in the reporting, but I need to se what it's actually reporting.
@vmvelev , this is where I´m seeing the deviation with the app vs integration
Mobile app vs HA setup for review.
Hmm, it looks good to me to be honest?
Your app is reporting 4.30 kWh for the 16th of May. Home assistant shows that on 00.00 on the 16th of May, the consumption is 1 508 000 Wh, which is 1508 kWh. At 16.00 on the 16th of May, I see a consumption of ~1512000 Wh, which is 1512 kWh. The difference is around 4kWh which seems accurate.
Do you see it another way?
I just thought of your point - do you need this to reset every day and start from 0 for each of the ACs you have?
@vmvelev , you are maybe on to something here.
Now it acts as a counter, but as a power consumption I was more expecting per hour. Adding a Adax heater image for reference.
This way it becomes a energy consumption resource in the energy dashboard.
I can create a helper of course, but if possible I think you see the idea? With energy prices shifting per hour it would be nice to adjust high demand power units to be controlled
Hey Kenneth,
I played with this last night and spend around 4 hours, but unfortunately, this is not an easy thing to do. There are several problems:
- The AC library (currently developed by a different developer) does not support the Day view
- The Toshiba IoT server is not built to handle many requests
I tried to edit the AC library by KaSroka on my own Home Assistant and then tried to get daily values and found out that Toshiba return these in buckets - each bucket for each hour of the day, so you can get the hourly stats for all of your ACs. Unfortunately, when I execute the 3 requests for my own 3 ACs, I got rate limited on the 3rd request. So you will not an immediate feedback due to this limitation imposed by Toshiba ![]()
I promise to spend more time on this and get you the stats you need, but until I am able to do this, could you please create a helper for this?
This will require a lot of time, as I will have to outsource the KaSroka library and make a fork of it so I can (maybe) integrate it in our HA wrapper, but that's a big project that will require a lot of time and effort on my end.
@vmvelev , first class response from your end, and thank you for both feedback and approach here! Wish I was a developer, but I am only the process manager person:) So won’t be able to contribute.
I will create an helper for local calculations.
Mans again, thank you for bringing the Toshiba back to home assistant!
Best regards from me here in Norway!
Looks like a textbook example of where a utility meter helper would work nicely ![]()
@vmvelev thank you for maintaining this fork, I really appreciate you for that. Quick question on some of the modes that do seem to be included, but are showing as unavailable - I do believe my units support for instance both ECO mode as well as High Power Mode, but in HA these entities report as unavailable - is there a way to enable them?
And out of curiosity, have you made any investigation into enabling the ability to use auto turn off timer via HA?
Thank you in advance… best regards from Czechia ![]()
My bad, did a bit of looking around and figured those entities are mode dependent - the unit needs to be turned on or set in a specific mode for those entities to function.
Then the only remaining question is about the timer option.
Hey, I’m runnign version Version 2026.5.2 of the Toshiba Home control integration and since a couple of days the integration won’t start. It says this:
Failed setup, will retry: Failed to connect to Toshiba AC
service: HTTP 429 calling /api/Consumer/Login
The officiel iOS Toshiba app does work and makes use of the same API. I guess Toshiba is actively blocking HA usage? Is there something we can do about this?
If you have issues with integration, maybe you can try my free project ![]()
I’d recommend switching to vmvelev’s Toshiba AC (Community) version, he’s taken over further development of the Toshiba AC HACS integration.
Apparently some changes have been made to Toshiba’s API and these most likely have not and won’t be reflected in the original Toshiba AC HACS integration, but are fixed in vmvelev’s.
Hello all,
I’d like to announce my new Toshiba AC Plus lovelace card.
Assuming a lot of you here in this thread are using the standard Toshiba Card, I thought I’d share it with you. The original card has been working perfectly fine over the last couple of years, but I found certain unit settings either non existant or needlessly burried requiring a number of taps or clicks to get to them - e.g. High power or ECO modes. I’ve also added an off timer function which has not been available with the original card at all. This function requires an additional helper entity and automation in HA per AC unit, but it’s all documented in the card’s github repo.
This new card was put together with the help of AI, which I have to admit has been a big help and quite frankly suprisingly successful! I made a post which I’d like to share with you that describes the card features. Feel free to test it out if you’d like, I’ll be happy if you let me know your thoughs and feedback on it.
Here goes:
Hi all, sorry for the late reply - I was on vacation and just caught up with the thread.
@kloboucek thank you for the recommendation and congrats on the Toshiba AC Plus card, it looks great! The off-timer is a nice addition, and I like that you documented the helper setup so clearly.
I’ll check whether I can replicate the official app’s timer functionality natively in the integration, so the timer would ideally work like it does in the Toshiba app (and without needing a helper entity and automation per unit). No promises on timing yet, but I’ll keep you posted here.
In the meantime, the integration has been getting some love - the latest release fixes the energy consumption sensors (Toshiba started rejecting our requests), makes restarts gentler on Toshiba’s rate limits, and adds support for fractional target temperatures. If you’re on an older version, it’s worth updating.
Quick update - the integration got another release today, 2026.8.3:
- Self-cleaning is now visible. If your unit runs a self-clean cycle after you turn it off (the fan keeps going for about half an hour to dry the heat exchanger), you’ll now see a dedicated “Self cleaning” sensor for it. The AC also shows as off in HA during the cycle, like it does in the Toshiba app - previously it looked like the AC was still running in its last mode, which understandably confused people.
- Full 5-16 °C range in 8 °C frost-protection mode on units that support it (model 3, e.g. Shorai Edge) - the old version capped everyone at 13 °C.
- Diagnostics downloads now include the unit’s model information, which makes it much easier for me to investigate device-specific reports - if you ever open an issue, attaching the diagnostics file now tells me most of what I need.
And a call for testers! The next big feature is independent vertical/horizontal swing control - separate controls per axis, so you can do things like vertical Fixed 2 + horizontal Swing. It works, but before I can release it I need confirmation from more people with real hardware, especially the 2026 Shorai Curve models (RAS-…KVSG…, the units with independently movable vanes).
If you have one and want to help:
- In HACS, open Toshiba AC (Community), three-dot menu, Redownload
- Enable “Show beta versions” and pick 2026.9.0b2, then restart Home Assistant
- You should get separate vertical and horizontal swing selects on your units
What I need to know - does setting one axis keep the other’s position, and do changes made from the IR remote or the Toshiba app show up correctly in HA? Report either here or on the pull request (Expose horizontal swing for independent-axis units (2026 Shorai Curve) by vmvelev · Pull Request #34 · vmvelev/home-assistant-toshiba_ac · GitHub), ideally with your indoor unit model and firmware version. Rolling back is easy - just redownload the stable version in HACS.
Note the beta doesn’t yet include today’s 2026.8.3 fixes - those will be bundled in the final release once swing testing is done.




