Hey folks, I’m about to push a fix for the issues with reconfiguring existing devices and I’m starting to think that the workflows around web-based airstage are kinda broken. Are there users who are using this integration against fujitsu’s servers (instead of local)? Ultimately this message is a temperature check to see if this is functionality that maybe should just be excised (or forked to an independent integration) to simplify things.
only locally
Is there a list of compatible Fujitsu AC devices ?
I got a quote for outside unit AOEG-30KBTA4, with 1x ASEH14-KMCG, 1x ASEH09-KMCG and 2x ASEH07-KMCG which are Airstage with wifi devices.
Anyone that has these and can confirm they are compatible with HomeAssistant via this (or a different) integration , just to be sure before I install these.
Thanks!
They should be compatible, this integration is effectively compatible with anything you can use the fujitsu airstage app to engage with. That may require buying additional parts for your units though.
Working flawlessly with my Fujitsu ASEG09KPCE. Thank you!
Is there any ongoing activity or certain interest in retrying to add the remote/cloud integration again?
I would like to connect to devices which are located in another house. For that purpose it would be great to have the possibility for connecting to the cloud interface.
Hi @ohshazbot ,
I´m a little bit late for providing feedback to your survey, but I would be one of the guys who is interested in the servers integration. The devices I like to monitor are on a remote location.
I could get it up and running by using the code from https://github.com/bendun-io/homeassistant-airstage-integration. However, the project seems not to be maintained anymore. I could fix the not properly read-out room temperature by comparing the code, but would appreciate to use this maintained and more enhanced integration.
Hey, if you scroll back in the thread, you will see the function for cloud was removed since the API of Fujitsu blocks your IP after a certain amount of calls.
The code will probably still be in an older version of the add-on if you want to check it.
I’m not familiar with that integration, GitHub - danielkaldheim/ha_airstage: Connects your Fujitsu Airstage air conditioner to Home Assistant. is the one that many others use and is maintained.
And afaik air stage api integration has not been removed, but it’s not recommended due to the above issues.
Hi all,
I have the feeling, every since I have connected my Fijutsu’s via Home Assistant. that the indoor temperature sensor is like 1 or 2°C higher than what it actually is.
(referring to this https://ilovemyfujitsu.com/images/techtips/temp-correction-hfi.pdf)
any chance that this has been set by the HA and how can I adopt?
These are the results from the internal sensors in the unit, verbatim. You’ll notice a similar discrepancy on the official Fujitsu app.
Hi all,
Just wanted to add the Daniel Kaldheim AIRSTAGE repository from GitHub. When I try the link GitHub - danielkaldheim/ha_airstage: Connects your Fujitsu Airstage air conditioner to Home Assistant. in the add repository command, hacs replies that this is not a valid add on repository. Anybody can help with a solution or the correct link? Thanks in advance for your support 
Kind regards
Did you add the following url as a custom repository in HACS?
Type = integration.
Works here, tried removing and re-adding
I am going to assume it is because it is more visible that you notice. I too notice that it does not match 100%, however do know that hot air rises and it’s therefore often warmer where the unit is, than where your other sensors might be.
What version of hacs and are you specificying the repo as an integration?
You need to recalibrate the AC units. There is a guide on how to do this, but it’s “not very fun” 
Also, @danielkaldheim - do you know if anyone found the “special” mode flag? I’m trying to find it - but iu_err_code doesn’t show it
Basically I have one unit in “heat” mode and one in “dry” and on AirStage I can see “Mode Mismatch” - but the iu_op_mode is just the mode requested and err_code shows 0.
I HAVE however found that “ou_current” gives the current draw of the OU (and therefore all attached IU…) also…
So far no, though you could compute it yourself by checking the state of devices that share the same heat pump (not ideal, I know, but I think that’s how the app is doing it as well). And it looks like ou_current is not universally supported (my device acks on that key)
The unit with a mode mismatch flashes it’s power LED when it’s in that state, so it deffo has a state flag ‘somewhere’.
The unit itself does, sure. But it doesn’t seem to convey that state via the api (at least none of the parameters in the airstage apk correlate to this error mode). So I believe it’s calculated