You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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
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:
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:
Nothing I do will get this working in HA. Any advice would be most appreciated, I am seriously missing automation of my AC unit!
The text was updated successfully, but these errors were encountered: