TypeError: int() argument must be a string, bytes-like object or a real number, not 'NoneType' in get_vertical_swing()

[antoinevalentinHA]

Hello,

I am encountering an error in the custom integration Fujitsu Airstage during the climate device state update.

Here is the full error message from Home Assistant logs:

Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 270, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 481, in _async_refresh
self.async_update_listeners()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 180, in async_update_listeners
update_callback()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 561, in _handle_coordinator_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1018, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1140, in _async_write_ha_state
self.__async_calculate_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1076, in __async_calculate_state
capability_attr = self.capability_attributes
File "/usr/src/homeassistant/homeassistant/components/climate/init.py", line 308, in capability_attributes
supported_features = self.supported_features
File "/config/custom_components/fujitsu_airstage/climate.py", line 320, in supported_features
if self.swing_mode:
File "/config/custom_components/fujitsu_airstage/climate.py", line 216, in swing_mode
if self._ac.get_vertical_swing() != None:
File "/usr/local/lib/python3.13/site-packages/pyairstage/airstageAC.py", line 224, in get_vertical_swing
return VALUE_TO_BOOLEAN[int(value)]
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

Additional information:

Home Assistant version: 2025.7.2

Fujitsu Airstage integration version: v1.4.4

The issue seems caused by get_vertical_swing() returning None, which is not handled properly in the code before converting to int.

A fix might be to check for None before attempting int() conversion.

Thank you in advance for your help!

[ohshazbot]

What were you doing that resulted in this error (if anything)?

Additionally, does this happen regularly or was this a one off?

What device model is this and how many vertical swing positions does it have?

[antoinevalentinHA]

Hello @ohshazbot,

Thank you for your quick reply.

What were you doing that resulted in this error?
The error occurred during the execution of the following automation in Home Assistant that interacts with the climate entity:

• id: '1751000000004'
  alias: Security - Power failure mode activation
  description: >
  Activates emergency heating and hot water modes in case of power failure.
  trigger:
  • platform: state
    entity_id: binary_sensor.power_failure
    to: 'on'
    action:
  • service: number.set_value
    target:
    entity_id: number.hot_water_temperature
    data:
    value: 45
  • delay: '00:00:10'
  • service: button.press
    target:
    entity_id: button.trigger_hot_water
  • service: number.set_value
    target:
    entity_id: number.heating_setpoint
    data:
    value: 19

Does this happen regularly or was this a one-off?
This error has happened multiple times, consistently during automation runs.

What device model is this and how many vertical swing positions does it have?
The device model is UTY-TFSXJ3.

Please let me know if you need any additional logs or information.

Thanks again for your support!

[ohshazbot]

When this occurs, does the device continue operating or do you need to take some other action?

I regularly see this type of error when my device starts reporting back garbage values. I've been unable to get in touch wtih Fujitsu about this, but when it does occur I eitehr need to powercycle my hvac system or unplug and replug in the usb dongle to recover. When this occurs, the fujitsu app also will end up reporting a loss of connectivity.

[antoinevalentinHA]

Hello @ohshazbot,

Thank you for the follow-up.

When this error occurs, the device continues to operate normally, despite the error being logged.

However, I have noticed that the error happens when the device starts reporting unexpected or garbage values.

In such cases, although the device keeps working, I sometimes perform a manual power cycle of the HVAC system or unplug and replug the USB dongle to clear the errors and ensure smooth operation.

Also, the official Fujitsu app does not report any loss of connectivity during these incidents.

Please let me know if I can provide further logs or details to help diagnose this issue.

Thank you again for your support.

[ohshazbot]

If that's the issue then there's nothing that can be done with this integration, this is a fault of the device. I experience the same thing with my UTY-TFSXH3 dongles.

You can get final confirmation that this is the same issue by trying to curl the device when it's in that state:

curl --no-progress-meter -X GET --data '{"device_id":"<DEVICE_ID>","device_sub_id":0,"req_id":"","modified_by":"","set_level":"03","list":["iu_fan_spd","iu_indoor_tmp"]}' 'http://<DEVICE_IP>/GetParam'

Be sure to replace <DEVICE_IP> and <DEVICE_ID>, and the device_id should be in all caps. If your response is

{
  "result": "NG",
  "error": "0002"
}

Then that confirms it's the same issue.

[ohshazbot]

While I'm currently in the process of doing a bit of a rework to pyairstage to reduce these sorts of issues, I decided to slap in a fix for this specific case to start finding these sorts of cases / reduce pain. I'm sure there will be another one that you or I encounter the next time they flake 8, and we can whack a mole it until we get them all, we find that underlying bug, or I fix pyairstage's resillience

[ohshazbot]

Anyone still seeing these?