Title: Unable to establish communication with Hisense AC (Smart-1-110 model, AEH-W4F1 Wi-Fi module)

[yshapir]

Hello,
I'm trying to set up communication with my Hisense AC (Smart-1-110 model) using the AirCon project, but I'm encountering issues. Here are the details:
AC Details:

Model: Hisense Smart-1-110
Wi-Fi Module: AEH-W4F1
IP Address: 192.168.8.186
Firmware Version: HET 1.4.3 hisense ameba 2018-06-25 09:04:00 1.1.628

Environment:

Home Assistant running on Ubuntu in KVM
MQTT broker (Mosquitto) running as part of Home Assistant
AC and Home Assistant are on the same network (192.168.8.x)

Current Status:

The AC is online and responds to ping requests.
The AC is successfully connected to and working properly with the official app (Tornado-US).
MQTT communication between Ubuntu host and Home Assistant is working.
The AC entity in Home Assistant is in an "unknown" state and doesn't respond to commands.
Port scan results:

TCP port 80 is open
UDP port 8888 (expected for this project) is not responding

MQTT Communication:
When subscribing to all MQTT topics (#), these are the only messages I receive:
Message received on homeassistant/climate/405ee160305f/hvac/config:
jsonCopy{
"unique_id": "405ee160305f",
"device": {
"identifiers": [
"hisense_ac_405ee160305f"
],
"manufacturer": "Hisense (tornado-us)",
"model": "Smart-1-110",
"name": "Mamad AC",
"sw_version": "HET 1.4.3 hisense ameba 2018-06-25 09:04:00 1.1.628"
},
"availability": [
{
"topic": "hisense_ac/LWT"
},
{
"topic": "hisense_ac/405ee160305f/available/status"
}
],
"precision": 1,
"temperature_unit": "F",
"current_temperature_topic": "hisense_ac/405ee160305f/f_temp_in/status",
"fan_mode_command_topic": "hisense_ac/405ee160305f/t_fan_speed/command",
"fan_mode_state_topic": "hisense_ac/405ee160305f/t_fan_speed/status",
"fan_modes": [
"auto",
"lower",
"low",
"medium",
"high",
"higher"
],
"mode_command_topic": "hisense_ac/405ee160305f/t_work_mode/command",
"mode_state_topic": "hisense_ac/405ee160305f/t_work_mode/status",
"modes": [
"off",
"fan_only",
"heat",
"cool",
"dry",
"auto"
],
"swing_mode_command_topic": "hisense_ac/405ee160305f/t_fan_power/command",
"swing_mode_state_topic": "hisense_ac/405ee160305f/t_fan_power/status",
"swing_modes": [
"on",
"off"
],
"temperature_command_topic": "hisense_ac/405ee160305f/t_temp/command",
"temperature_state_topic": "hisense_ac/405ee160305f/t_temp/status",
"max_temp": "86",
"min_temp": "61"
}
QoS: 0 - Retain: true
Message received on hisense_ac/405ee160305f/available/status:
Copyonline
QoS: 0 - Retain: true
Message received on hisense_ac/LWT:
Copyonline
QoS: 0 - Retain: true
It's important to note that these are the only messages received when subscribing to all topics (#). When sending commands (e.g., setting mode to cool), I don't receive any response or status update from the AC. Additionally, I don't receive any messages on the status topics specified in the config message, such as current temperature, fan mode, or operation mode.
Add-on Configuration:
Here's my current configuration in the add-on's YAML file:
yamlCopylog_level: INFO
mqtt_host: core-mosquitto
mqtt_port: 1883
mqtt_user: mqtt-user
mqtt_pass: [redacted]
port: 8888
app:

• username: [redacted]
  password: [redacted]
  code: tornado-us
  local_ip: 192.168.8.186
  Attempted Troubleshooting:

Verified MQTT communication by subscribing to AC topics.
Attempted to send commands via MQTT.
Checked network connectivity between Home Assistant and the AC.
Verified the AC's IP address and network settings.
Power cycled the AC.

Questions:

Is the AEH-W4F1 Wi-Fi module compatible with this project?
Given that port 80 is open but 8888 is not responding, are there any known firmware versions or AC models that use a different port or protocol?
Are there any specific settings or steps needed to enable local control on this AC model?
How can I further troubleshoot the UDP communication on port 8888?
Since the AC works with the official app, is there a way to capture and analyze that communication to understand how it's interacting with the AC?
Are there any issues with my add-on configuration that could be preventing proper communication?

Any guidance or suggestions would be greatly appreciated. I'm happy to provide any additional information or perform further troubleshooting steps as needed.
Thank you for your time and assistance!

[kevtuning]

Is your AC in the same VLAN than HA ? (It's a requirement... even with two clans with full access it doesn't work... it's a limitation of the adapter)

[yshapir]

all devices are on the same subnet 192.168.8.X
My Home Assistant is on virtual machine on Ubuntu and is set up as a bridge with the same subnet.
I have a TP-link Mesh in AP mode connected to a router that assigns all the IP's

[PeterH63]

I have the same problem. On the dashboard if i click on the ac it shows the message "This entity is no longer provided by the mqtt integration. If the entity is no longer used, delete it in Settings."