2 out of 3 devices dropping connection in HA repeatedly

[stoto]

I have 3 units configured in HA, but two of them is offline most of the time and only becomes available for 1-2 seconds. All 3 devices working nicely in airstage app. Wifi connection is very stable and signal is strong for all devices (checked in router). It is very strange because the "Office AC" is online and working well in HA all the time. All 3 devices and their sticks are exactly the same type.

19 June 2025 - Device Status Changes
10:12:38 (1 minute ago)

2C3B70000781 Indoor LED became unavailable
2C3B70000781 Quiet fan became unavailable
2C3B70000781 Powerful became unavailable
2C3B70000781 Economy mode became unavailable
2C3B70000781 Power became unavailable
Bedroom AC became unavailable

10:11:53 (2 minutes ago)

2C3B70000781 Indoor LED turned off
2C3B70000781 Quiet fan turned off
2C3B70000781 Powerful turned off
2C3B70000781 Economy mode turned off
2C3B70000781 Power turned off
Bedroom AC turned off

10:04:05 (10 minutes ago)

2C3B70000781 Indoor LED became unavailable
2C3B70000781 Quiet fan became unavailable
2C3B70000781 Powerful became unavailable
2C3B70000781 Economy mode became unavailable
2C3B70000781 Power became unavailable
Bedroom AC became unavailable triggered by action Climate: Set fan mode - Stoto

10:03:51 (10 minutes ago)

2C3B70000781 Indoor LED turned off
2C3B70000781 Quiet fan turned on
2C3B70000781 Powerful turned off
2C3B70000781 Economy mode turned off
2C3B70000781 Power turned off
Bedroom AC turned off

09:57:33 (17 minutes ago)

2C3B70000781 Indoor LED became unavailable
2C3B70000781 Quiet fan became unavailable

[ohshazbot]

What version are you running? And what device models are these?

[stoto]

Based on this, it's 1.4.4

[ohshazbot]

Out of curiosity, what's the general health of your wifi in the rooms where it struggles? Initial reading makes me think this is a local network issue (could also be a device issue as sometimes my dongles become unresponsive). Otherwise something you can do, if your proficient enough, is to try to hit the endpoints for the devices yourself via curl while they're in an inactive state to see if you can repro it (in which case it's a device issue).

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", "af_vertical_num_dir","iu_wifi_led","iu_af_inc_hrz","iu_af_inc_vrt","iu_indoor_tmp","iu_outdoor_tmp","iu_hmn_det"]}' 'http://IP_ADDRESS/GetParam'
Just make sure to sub in IP_ADDRESS and DEVICE_ID (device id must be all caps)

[stoto]

That curl gives back the following response without error:
{"value":{"iu_fan_spd":"2","iu_wifi_led":"0","iu_af_inc_hrz":"0","iu_af_inc_vrt":"4","iu_indoor_tmp":"7150","iu_outdoor_tmp":"7200","iu_hmn_det":"0"},"read_res":"ack","device_id":"DEVICEID","device_sub_id":0,"req_id":"","modified_by":"","set_level":"03","cause":"","result":"OK","error":""}

Using that curl I quickly vibe coded a polling bash script to fetch all 3 devices with 5 seconds repeat. Ran it for 3 minutes and all calls were successful.

Where can I find some more detailed logs from the integration?

=== Poll Cycle: 2025-06-25 22:23:06 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:23:13 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:23:20 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:23:27 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 0s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:23:34 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:23:42 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:23:49 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 0s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:23:55 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 0s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:02 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 0s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:09 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 0s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:16 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 0s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:23 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 0s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:30 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 0s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:37 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 0s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:44 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 0s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:51 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:24:58 ===
✓ Device_40 - HTTP 200 - Duration: 2s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:25:07 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:25:14 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 0s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:25:20 ===
✓ Device_40 - HTTP 200 - Duration: 2s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:25:29 ===
✓ Device_40 - HTTP 200 - Duration: 0s
✓ Device_23 - HTTP 200 - Duration: 1s
✓ Device_24 - HTTP 200 - Duration: 0s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:25:35 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 0s
✓ Device_24 - HTTP 200 - Duration: 1s

Summary: 3/3 endpoints responding successfully

=== Poll Cycle: 2025-06-25 22:25:42 ===
✓ Device_40 - HTTP 200 - Duration: 1s
✓ Device_23 - HTTP 200 - Duration: 0s
✓ Device_24 - HTTP 200 - Duration: 1s

[ohshazbot]

During that time, was HA reporting the devices as unavailable?

[stoto]

Yes.

[firerm]

That’s exactly the same problem I have with the same air conditioner (I just saw the issue), and it’s exactly the same model I own — the only difference is that I have just one unit.

[ohshazbot]

Where can I find some more detailed logs from the integration?

system logs after turning on debug logging for the integration

[ohshazbot]

Okay, did some spelunking to try to improve some debugging and in the process I noticed that we did have a 4s timeout on fetching data. I'm comfortable stating that I do not have a shitty network and it was taking typically 3-4s per request, with some occasional failures occuring. So I went ahead and upped the timeout to 10s which should improve things. This was put out in the 1.7.2 release, please let me know if this improves things

[ohshazbot]

What wireless lan module model do you have installed?

[firerm]

I Think this one : Model: UTY-TFSXH4

[ohshazbot]

More logging/exception handling changes in 1.7.3. After you update, please provide an update on what you are experiencing.

[firerm]

fixed ! You are my Hero !

[ohshazbot]

Oh wow, I honestly wasn't holding my breath on this one. I'll give it a few days for dust to settle before I close out this ticket