This does not sound accurate, I am able to manage my device in both HA and Fujitsu air stage. Is that the app you’re using or are you on the other one?
Can someone fix the manifest.json so that it shows the correct version?
Sorry for being unclear.
Yes you can have both on. My intention was that if you want to run it only locally on HA and first registered to the app, then you can unregister from the app and then run the airstage integration locally only.
But my issue remains. In home assistant I can see my airstage going offline/online every minute. Starting to get annoying.
I was able to run it for a full day online when I was off to work. Immediately when I was back from work it started acting weird again. This has not happened since. And I tried turning off wifi of all the devices I possible could have had with me.
It’s running on 2.4Ghz wifi. Broadcasting 5Ghz on a separate SSID.
How far from your router are your head units? Is the computer your running ha on hardwired or wifi? If the latter, how far away is it from your router? Do you live in a dense environment or one with multiple Wi-Fi networks? Have you done any network analysis to determine how often packets are getting dropped?
I ask these questions because from your anecdote, it’s fine during the day but once the after-work hours hit the connection gets poor (possibly due to your use of the network or neighbors reducing the effectiveness of your local network). I would start there, personally
Thanks for your reply!
Router is in same room as heat pump, so 5 meters. HA is running on Raspberry pi 4 over wifi. About the same distance. All other devices are fine, so don’t think that’s an issue. I have about 5 shellys.
Only wifi herre in my area are my own.
I pinged the IP and get 87 timeouts, then 2 successful and then 50+ until I stopped pinging.
It’s annoying, really would want this to work. My heat pump is new now in October -24.
EDIT: tried resetting the wifi (sending code L3 to the pump). When I reconnect by accessing the AP-WH3E…and selecting my wifi and pwd, my computer wifi automaticlaly jumps back to my normal wifi and the wifi led turns on. But still same issue. I get “no route to host” when pinging.
EDIT 2: There are two modes for connecting (so pressing the wifi-button twice you get to L2 with settings 1 or 2. I think this had something with easy connection/manual, but I can’t find any information about this?
If you’re having that much issues just pinging it, that is an issue with your network or whatever hardware you have from Fujitsu. That is beyond HA and and indicates a failure in your networking or hardware.
When you did the Wi-Fi reset, did your device get the same IP address? Because if you’re trying to hit the old IP address then it’s understandable that there’s no route to host.
Router assigned the same IP address. I have reserved the IP in the router. But I tried removing the rules as well, same issue. Will spin up another router in bridge mode and check if that helps.
I hope it’s the router and not the wifi on the heat pump, but if it is I assume I need to talk to Fujitsu for some warranty claim or something.
Thanks for the help!
Did you figure it out @oscarrudnas?
I have two indoor air handlers and each one has a WiFi adapter. One of them is rock solid but the other (which was fine for months and months) has started exhibiting the same behavior you’ve described above.
Hi All,
@danielkaldheim et al, thanks for a fantastic integration! It works very well in my home for a little while now.
There are two tweaks that I’d love to be able to do, but I’m not sure that they’re even theoretically possible:
- For energy monitoring purposes, I’d love to be able to read out if a unit is actively warming/cooling or not. Is that possible?
- Is it possible to perform setting changes over the dongle? In particular, I’d love to change the offset temperature, because that seems to change somewhat with outdoor temperature. Option 30/31 on page 53 for those curious: DESIGN & TECHNICAL MANUAL
Probably not possible, but it would be lovely if there are options to be explored.
Hi all, I would like to know if this integration is made up for iOS. I need way to call temperatures from Siri
Am I in the right topic?
Yes and no, this is specifically about Fujitsu air stage integration for home assistant. But I believe there are mechanisms for wiring home assistant to Apple’s ecosystem (but there are different topics for that support)
Yes I have Fujitsu AIRSTAGE, and I wanna integrate that with apple HomeKit is it possible?
Hey, anything is possible with HA ;).
That being said, it is important to understand how Home Assistant (HA) and this integration work to be able to answer your question:
The logic of this add-on is as follows:
- HA provides a framework in which this integration resides
- The Fujitsu integration is able to call the (open) HTTP endpoints of the air conditioning units(in HA = devices) to switch or read:
- different modes (in HA = entity ‘switch’)
- set the temperature (in HA = entity 'climate).
- By adding a aircon unit to the integration, you are able to execute all the commands that were discovered thus far.
What this means is that HA is able to contact the Aircon units.
Your question is if you can link Siri. In order to do this, you need first for HA to be able to read/set values to the Fujitsu units. Next, you need to expose information from HA to Homekit, the protocol/framework Apple uses to
Link to documentation: [HomeKit Bridge - Home Assistant](https://expose HA to Homekit).
A quick search tells me you are not alone in wanting this:
- [Expose Scripts in Homekit Bridge]
- [How to make HomeKit see more of your gadgets with Home Assistant - Ars Technica]
Best of luck!
just install the new version of HA core 2025.4.2 and Airstage integration doesn’t run, it’s only my case? i’m returning to the last version with the backup
Can you specify which version of the integration your using and what sort of errors you’re experiencing
My airstage integration 1.2.3 is running fine with HA 2025.4.2.
Same problem here with 2025.4.2, all my Airstage units are showing as unavailable - here is the relevant error (similar ones throughout log):
2025-04-16 08:10:20.049 ERROR (ImportExecutor_0) [homeassistant.loader] Unexpected exception importing platform custom_components.fujitsu_airstage.climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1249, in _load_platform
cache[full_name] = self._import_platform(platform_name)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1281, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 201, in protected_loop_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.13/importlib/__init__.py", line 88, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/config/custom_components/fujitsu_airstage/climate.py", line 75, in <module>
VERTICAL_HIGHEST: constants.VerticalSwingPosition.HIGHEST,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'pyairstage.constants' has no attribute 'VerticalSwingPosition'. Did you mean: 'VerticalSwingPositions'?
2025-04-16 08:10:20.133 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module with args ('custom_components.fujitsu_airstage.climate',) inside the event loop by custom integration 'fujitsu_airstage' at custom_components/fujitsu_airstage/__init__.py, line 115: await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS) (offender: /usr/src/homeassistant/homeassistant/loader.py, line 1281: return importlib.import_module(f"{self.pkg_path}.{platform_name}")), please create a bug report at https://github.com/danielkaldheim/ha_airstage/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#import_module
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module>
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.13/asyncio/base_events.py", line 712, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.13/asyncio/base_events.py", line 683, in run_forever
self._run_once()
File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2040, in _run_once
handle._run()
File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 896, in async_setup_locked
await self.async_setup(hass, integration=integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 662, in async_setup
await self.__async_setup_with_context(hass, integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 751, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/fujitsu_airstage/__init__.py", line 115, in async_setup_entry
await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
2025-04-16 08:10:20.138 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.fujitsu_airstage.climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1249, in _load_platform
cache[full_name] = self._import_platform(platform_name)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1281, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 201, in protected_loop_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.13/importlib/__init__.py", line 88, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/config/custom_components/fujitsu_airstage/climate.py", line 75, in <module>
VERTICAL_HIGHEST: constants.VerticalSwingPosition.HIGHEST,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Also:
Logger: homeassistant.components.dhcp
Source: helpers/deprecation.py:222
integration: DHCP Discovery ([documentation](https://www.home-assistant.io/integrations/dhcp), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+dhcp%22))
First occurred: 08:10:07 (2 occurrences)
Last logged: 08:10:07
DhcpServiceInfo was used from fujitsu_airstage, this is a deprecated constant which will be removed in HA Core 2026.2. Use homeassistant.helpers.service_info.dhcp.DhcpServiceInfo instead, please report it to the author of the 'fujitsu_airstage' custom integration
Oh hang on for some reason my Airstage integration is still on 1.1.7 and isn’t showing in HACS as installed, might be some weird thing with HACS not remembering what it needed to update? Investigating…
Yep - this turned out to be a weird HACS thing where it wasn’t updating Airstage (and basically all my other HACS stuff) so Core 2025.4.2 must have just finally made a breaking change that actually was fixed a while back in the Airstage integration, I just wasn’t running the latest. @ferwaish - check your integration version!
The DHCP version issue should be addressed in 1.3.1, the latest release.
Otherwise, looks like the underlying pyairstage library got updated but not ha_airstage. I had to make a breaking change to pyairstage to support 4 and 6 position fans. Unfortunately versions of ha prior to 1.3.0 did not restrict max pyairstage version so if you system sticks with an old ha_airstage but updates pyairstage then failures like that will be experienced.