Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed AC to different vlan, now can't connect #280

Open
Alby247 opened this issue Mar 31, 2024 · 3 comments
Open

Changed AC to different vlan, now can't connect #280

Alby247 opened this issue Mar 31, 2024 · 3 comments

Comments

@Alby247
Copy link

Alby247 commented Mar 31, 2024

I created a vlan for my IoT devices, including my Fujitsu AC. It was previously working fine with this add on when HA and the AC were on the same subnet.

AC is at 192.168.30.58, I can control it using FGLAir on my android phone on the 192.168.10.x subnet.

There are no ACL rules preventing communication across vlans (TPLink Omada ER605 - defaults to full access across vlans)

HA is at 192.168.10.5. Mosquitto is running on this server.

Add on config as follows:

log_level: INFO
mqtt_host: 192.168.10.5
mqtt_port: 1883
mqtt_user: mqtt-user
mqtt_pass: password
port: 1886
app:
  - username: [email protected]
    password: password
    code: fglair-us
local_ip: 192.168.30.58

With MQTT-Explorer running on my laptop (on the 192.168.10.x subnet), the AC is reporting as online, and HA is getting a configuration from it. Output from MQTT Explorer:

{"unique_id": "a0cc2b3271d6", "device": {"identifiers": ["hisense_ac_a0cc2b3271d6"], "manufacturer": "Hisense (fglair-us)", "model": "AP-WA3E", "name": "AC000W000768786", "sw_version": "bc 2.6.17-fgl2 06/29/20 09:03:57 ID jre/mfg/2dfbf5d"}, "availability": [{"topic": "hisense_ac/LWT"}, {"topic": "hisense_ac/a0cc2b3271d6/available/status"}], "precision": 1.0, "temperature_unit": "C", "fan_mode_command_topic": "hisense_ac/a0cc2b3271d6/fan_speed/command", "fan_mode_state_topic": "hisense_ac/a0cc2b3271d6/fan_speed/status", "fan_modes": ["auto", "quiet", "low", "medium", "high"], "mode_command_topic": "hisense_ac/a0cc2b3271d6/operation_mode/command", "mode_state_topic": "hisense_ac/a0cc2b3271d6/operation_mode/status", "modes": ["off", "fan_only", "heat", "cool", "dry", "auto"], "swing_mode_command_topic": "hisense_ac/a0cc2b3271d6/af_vertical_swing/command", "swing_mode_state_topic": "hisense_ac/a0cc2b3271d6/af_vertical_swing/status", "swing_modes": ["on", "off"], "temperature_command_topic": "hisense_ac/a0cc2b3271d6/adjust_temperature/command", "temperature_state_topic": "hisense_ac/a0cc2b3271d6/adjust_temperature/status", "max_temp": "30", "min_temp": "16"}

Nothing I do will get this working in HA. Any advice would be most appreciated, I am seriously missing automation of my AC unit!

@Alby247 Alby247 changed the title Changed AC to different vlan, now can;t connect Changed AC to different vlan, now can't connect Mar 31, 2024
@kevtuning
Copy link

It's a known limitation of the Fujitsu AC that only replies in the same subnet.

The workaround is to use the local ip configuration.

You'll find some documentation on it but basically:
you create a virtual ip for your HA in the iot vlan and you put it in the local op configuration parameter

@Alby247
Copy link
Author

Alby247 commented Apr 1, 2024

put it in the local op configuration parameter

Ok, so my AC IP address is 192.168.30.58, and I have it configured as

local_ip: 192.168.30.58

The IP of my HA server is 192.168.10.5

What am I doing wrong?

And what does "virtual IP" mean

you create a virtual ip for your HA in the iot vlan

@kevtuning
Copy link

No,
you're HA server should have an additional IP in the 192.168.30.x range, say 192.168.30.200

and so you should have local_ip: 192.168.30.200

That way, your Fujistu will reply back to 192.168.30.200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants