Anyone tried Fujitsu AnywAiR controllers? (rebranded Advantage Air MyAir)

Hi Home Assistant Community,

I’m currently in the market for a new ducted reverse cycle system for my home and are interested in integrating it with Home Assistant.

A number of installers in my area are pushing Fujitsu systems which use the Fujitsu AnywAiR controller (Ducted Controller | anywAiR® Technology | Fujitsu General). As far as I can ascertain this is a rebranded Advantage Air MyAir controller. I’ve done a lot of searching around on the forums and the Google and haven’t been able to find a lot of information outside of the marketing material.

I was wondering if anyone here had an AnywAiR controller in their home and had they succeeded in integrating it with Home Assistant?

Thanks, Jake.

1 Like

I’ll add my interest to this as well, and would be willing to start a bounty.

Certainly keen to get this working too.
Would make it much easier to automate the zones vs movement.

So I have the AnywAiR controllers installed in my home and I have been able to set them up using hte existing Advantage Air integration that already exists: Advantage Air - Home Assistant

I inspected the traffic going from the app using an app and found that they use the a different port to the default in the Advantage Air i.e. port 10211

The rest of the configuration and APIs seemed to be identical. All that is needed is to find the local ip address of the tablet. You can do this by following: How to check IP address of the local network on iOS, Android and Windows devices | Poster Help Center

Then try to setup the advantage air integration by entering the ip address and replacing the port with 10211

The only thing I have found is that zones that don’t have an associated thermostat are not showing up as controllable but everything else is working fine.

Edit: Everything appears to be working perfectly

Hey, @zecuria was there anything else you did that was special?

I just got Fujitsu AnywAir installed in house, I can easily find IP address of device (tablet). I made it static as well. I did some traffic checking and it looks like my phone sends a message to device via port 10211 as well. But I tried entering that in Advantage Air integration but just keep getting “Failed to connect”. I’m thinking have Fujitsu done something different to lock it down? What did you use for traffice sniffing? I’m just using wireshark but maybe it’s reporting wrong port?

Im in New Zealand if that helps at all.

Any help would be great.

EDIT: I definitely have the right settings. I just use Postman to send a GET Request via http://tabletip:10211/getSystemData

and got a completely valid request back:

e.g.
{"aircons":{"ac1":{"info":{"activationCodeStatus":"noCode","airconErrorCode":"","deleted":8,"deleted":64,"cbType":50,"climateControlModeIsRunning":fals/

Hey, just wondering if you ever got this working and how you are finding the anywAiR system. I’m looking at installing one. Lack of integrations is a massive negative tho.

Hey, yep got it working. See more details and conversation as part of github issue.

I think the anywAir system goes to sleep so something and can’t communicate with it. But once you connect, the integration keeps it awake and its been working great. Once setup can easily control all areas and set zones etc. See attached picture.

Only thing to note. When I’ve had my Home Assistant server randomly shut down (turned off power) and integration hasn’t talked to anywAir for a while. The integration can’t talk to anywair again on first boot. I just need to restart home assistant and fiddle with anywAir a bit to get them talking again, but once connected again runs fine. This has happened two to three times over the month but it’s always after I’ve reset power.

Things should be stable for now but that’s the only thing, read the github issue more but something with these specific tablets provided, need continuously pinging to keep connection alive or something. The integration does that for you in a way. It’s just if integration is down for while, you might have issues with me to get them talking again.

Great, thanks for the reply. Im going to be getting a system installed in the coming weeks so will report back on how I get on with getting this running

Installed today and changing to the port you mentioned above allowed me to connect! Im a home assistant nob so need to do some research into how you created the cart in your image above

Hey, hope it’s working well. Here is my YAML config for that widget on the dashboard. So you should be able to replicate. Just change sensors as your’s etc. Just not I’m also using some custom UI components from HACS store like mushroom cards and multiple-entity-row, but you will be able to see that all in the YAML config below.

type: vertical-stack
title: Central Heating
cards:
  - type: custom:mushroom-chips-card
    chips:
      - type: conditional
        conditions:
          - entity: climate.ac
            state_not: 'off'
        chip:
          type: entity
          entity: select.ac_myzone
      - type: entity
        entity: sensor.average_home_temperature
        icon: mdi:home
      - type: entity
        entity: sensor.average_room_temperature
        icon: mdi:bed-queen
      - type: entity
        entity: input_boolean.ac_monitoring
        icon: ''
        tap_action:
          action: toggle
      - type: entity
        entity: input_boolean.heater_monitoring
        tap_action:
          action: toggle
  - type: custom:mushroom-climate-card
    entity: climate.ac
    name: Climate
    show_temperature_control: true
    hvac_modes:
      - heat
      - cool
      - dry
      - 'off'
  - type: conditional
    conditions:
      - entity: climate.ac
        state_not: 'off'
    card:
      type: entities
      entities:
        - entity: climate.ac_master
          type: custom:multiple-entity-row
          name: Master
          icon: mdi:fan
          show_state: false
          tap_action:
            action: toggle
          entities:
            - entity: sensor.ac_master_temperature
              name: Current Temp
            - attribute: temperature
              unit: °C
              name: Target Temp
            - entity: sensor.ac_master_vent
              name: Duct
        - entity: climate.ac_nayan
          type: custom:multiple-entity-row
          name: Nayan
          icon: mdi:fan
          show_state: false
          tap_action:
            action: toggle
          entities:
            - entity: sensor.ac_nayan_temperature
              name: Current Temp
            - attribute: temperature
              unit: °C
              name: Target Temp
            - entity: sensor.ac_nayan_vent
              name: Duct
        - entity: climate.ac_yaashni
          type: custom:multiple-entity-row
          name: Yaashni
          icon: mdi:fan
          show_state: false
          tap_action:
            action: toggle
          entities:
            - entity: sensor.ac_yaashni_temperature
              name: Current Temp
            - attribute: temperature
              unit: °C
              name: Target Temp
            - entity: sensor.ac_yaashni_vent
              name: Duct
        - entity: climate.ac_entry
          type: custom:multiple-entity-row
          name: Entry
          icon: mdi:fan
          show_state: false
          tap_action:
            action: toggle
          entities:
            - entity: sensor.ac_entry_temperature
              name: Current Temp
            - attribute: temperature
              unit: °C
              name: Target Temp
            - entity: sensor.ac_entry_vent
              name: Duct
        - entity: climate.ac_hall
          type: custom:multiple-entity-row
          name: Hallway
          icon: mdi:fan
          show_state: false
          tap_action:
            action: toggle
          entities:
            - entity: sensor.ac_hall_temperature
              name: Current Temp
            - attribute: temperature
              unit: °C
              name: Target Temp
            - entity: sensor.ac_hall_vent
              name: Duct
        - entity: climate.ac_living
          type: custom:multiple-entity-row
          name: Living
          icon: mdi:fan
          show_state: false
          tap_action:
            action: toggle
          entities:
            - entity: sensor.ac_living_temperature
              name: Current Temp
            - attribute: temperature
              unit: °C
              name: Target Temp
            - entity: sensor.ac_living_vent
              name: Duct
        - entity: climate.ac_kitchen
          type: custom:multiple-entity-row
          name: Kitchen
          icon: mdi:fan
          show_state: false
          tap_action:
            action: toggle
          entities:
            - entity: sensor.ac_kitchen_temperature
              name: Current Temp
            - attribute: temperature
              unit: °C
              name: Target Temp
            - entity: sensor.ac_kitchen_vent
              name: Duct
      state_color: false
      show_header_toggle: false

I got mine connected today, as @apat183 said, looks like the tablet goes to sleep, I tried sending commands form the app on my phone just before trying to connect but still it would respond.

What it worked for me was to send a ping to the port via windows powershell, first attempt came negative response, second attempt was positive and did the home assistant connection straight after and it worked

$ Test-NetConnection 192.168.1.102 -p 10111

For anyone arriving in 2024 looking to get this to work, please rest assured that the confusingly named “myanyWair Next” actually uses the Sensibo add-on which can be found here: Sensibo - Home Assistant

All you need is to generate an API key on the sensibo website.

Hi mate just ran across this. How do you made it to static IP? I’m very annoyed with the IP always change when there’s power cut.

You should be able to go into the android settings and set IP? I set my statics IPs on the router DHCP settings, so that it provides the IP so I guess the tablet doesn’t get to pick.

Yeah the wall mounted tablet doesn’t have the setting to choose DHCP / Static so I guess would require to set the static from the router itself. Thanks for letting me know