Unable to update settings error in update_port_controls

[danielgoepp]

Describe the bug
This started happening 7/4 at 18:45. Is anyone else experiencing an issue?
I'm not sure if this is something I did or if there is a bug, but I can't figure it out. When I turn a fan on or off I get this error:

2025-07-07 06:13:51.428 WARNING (MainThread) [custom_components.ac_infinity.core] Unable to update settings. Retry attempt 1/2
2025-07-07 06:13:57.993 WARNING (MainThread) [custom_components.ac_infinity.core] Unable to update settings. Retry attempt 2/2
2025-07-07 06:14:04.095 ERROR (MainThread) [custom_components.ac_infinity.core] Unable to update settings. Retry attempt limit exceeded
Traceback (most recent call last):
  File "/config/custom_components/ac_infinity/core.py", line 823, in update_port_controls
    await self._client.set_device_mode_settings(
        controller_id, port_index, key_values
    )
  File "/config/custom_components/ac_infinity/client.py", line 128, in set_device_mode_settings
    _ = await self.__post(API_URL_ADD_DEV_MODE, settings, headers)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/ac_infinity/client.py", line 248, in __post
    raise ACInfinityClientRequestFailed(json)
custom_components.ac_infinity.client.ACInfinityClientRequestFailed: {'msg': 'Something went wrong with your request.\nPlease try again later.', 'code': 100001}
2025-07-07 06:14:04.096 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [123444906790240] Error during service call to select.select_option: {'msg': 'Something went wrong with your request.\nPlease try again later.', 'code': 100001}

What's interesting though is that it does actually update the fan. I have the app on my phone, and I can see the fan turn on and off.

What's even more odd..I can set the mode to "Cycle" and I get no error, but "On" and "Off" both error.

To Reproduce
Just turn the fan on or off from Home Assistant.

Expected behavior
I expect the fan to turn on and off without erroring.

Desktop (please complete the following information):

• Any - The issue is server side, not client side

[HansBerghofer]

I am experiencing similiar behaviour. If i change the max in min speeds of my fan I get an error. But if I change for example the VPD leaf offset everything is working fine. I get no error if I change the values in the ACI app.

[danielgoepp]

I'm not sure what the cause was here, but it stopped happening, and I can't reproduce. I'll keep an eye.

[danielgoepp]

My mistake, this is still happening. Is there any debug info that would be helpful?

For what it is worth, I boot I see all these warnings too:

2025-08-01 03:41:20.759 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_devCt" (temperature_calibration) for platform "number".
2025-08-01 03:41:20.759 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_vpdCt" (vpd_leaf_temperature_offset) for platform "number".
2025-08-01 03:41:20.760 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_1_devTt" (dynamic_transition_temp) for platform "number".
2025-08-01 03:41:20.760 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_1_devBt" (dynamic_buffer_temp) for platform "number".
2025-08-01 03:41:20.760 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_2_devTt" (dynamic_transition_temp) for platform "number".
2025-08-01 03:41:20.761 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_2_devBt" (dynamic_buffer_temp) for platform "number".
2025-08-01 03:41:20.761 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_3_devTt" (dynamic_transition_temp) for platform "number".
2025-08-01 03:41:20.761 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_3_devBt" (dynamic_buffer_temp) for platform "number".
2025-08-01 03:41:20.761 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_4_devTt" (dynamic_transition_temp) for platform "number".
2025-08-01 03:41:20.762 WARNING (MainThread) [custom_components.ac_infinity.core] Ignoring unsuitable entity "ac_infinity_3C84271F844E_port_4_devBt" (dynamic_buffer_temp) for platform "number".
2025-08-01 03:41:21.064 WARNING (Thread-1 (_monitor)) [homeassistant.util.logging] Module custom_components.ac_infinity.core is logging too frequently. 200 messages since last count

[dalinicus]

unsuitable entity just means your device does not support that field (aka its missing from the api payload that was returned.) Those can be safely ignored, and I think I switched them to info in the 2.0 update I was working on a few months ago (life got in the way)

#108

As for the root error you posted, the AC Infinity API is very unstable, and it happens from time to time that you'll see those retry attempts. Unfortunately there's nothing I can do from the HA side to alleviate that other than increase the retry count. You can read more about it in this thread

#39

[danielgoepp]

Thanks @dalinicus! I definitely know what you mean about life getting in the way ;) Appreciate the update.

[danielgoepp]

@dalinicus I know you said it was the API, but I couldn't stop wondering what was going on here and decided to investigate a bit further. The thing I was having a hard time with was that it was happening 100% of the time for me, and that the setting would update, it would just error each time. I didn't feel like an intermittent API access issue. Also, It was "working" but with errors. I decided to fork your repository do run it through some testing with claude code to look at the payloads closer. After much testing and conversation, it came back with a result that fixed the problem for me. I'm wondering if you would be interested in considering this change? I can create a PR if you prefer. This change 100% fixes the problem for me, I no longer have errors.

Here is a diff of client.py

--- a/custom_components/ac_infinity/client.py
+++ b/custom_components/ac_infinity/client.py
@@ -93,12 +93,27 @@ class ACInfinityClient:
         """
         settings = await self.get_device_mode_settings_list(device_id, port_id)
 
-        # Remove fields that are not part of update payload, as well as the devSettings structure so we're not messing
-        # with the controller settings.
+        # Remove fields that are not part of update payload or cause issues with newer controllers
         for key in [
             PortControlKey.DEVICE_MAC_ADDR,
             PortControlKey.IPC_SETTING,
             PortControlKey.DEV_SETTING,
+            # Additional fields that may cause issues with Type 11 controllers
+            "loadType",
+            "loadState", 
+            "abnormalState",
+            "timestamp",
+            "reportSeq",
+            "fieldSet",
+            "devTimeZone",
+            "humidity",
+            "temperature", 
+            "temperatureF",
+            "tTrend",
+            "hTrend",
+            "speak",
+            "trend",
+            "isOpenAutomation",
         ]:
             if key in settings:
                 del settings[key]
@@ -123,6 +138,12 @@ class ACInfinityClient:
         for key in settings:
             if settings[key] is None:
                 settings[key] = 0
+            # Convert boolean values to integers for API compatibility
+            elif isinstance(settings[key], bool):
+                settings[key] = 1 if settings[key] else 0
+            # Ensure all values are valid integers or strings
+            elif isinstance(settings[key], float):
+                settings[key] = int(settings[key])
 
         headers = self.__create_headers(use_auth_token=True)
         _ = await self.__post(API_URL_ADD_DEV_MODE, settings, headers