Which HomeAssistant integration works with a IS-ACX-WIFI-1 module from airconwithme?
You can use it with IntesisHome integration.
It’s currently only working with cloud connection, but if you want to use locally, you need to use this PR: Add IntesisBox + IntesisHome local support by jnimmo · Pull Request #57883 · home-assistant/core · GitHub.
Installation instructions in my comment here.
The thing is that the cloud connection doesn´t work. All I see is “Unavailable” with some function being called on a NoneType.
Interesting. I just checked my cloud connection and it’s still working.
Can you share your climate configuration block from configuration.yaml?
By the way, can you control your AC unit from Airconwithme app on Android/iOS?
The climate configuration block is the same as the documentation, but in a different order. It has a device: airconwithme entry too. The order should not matter, however.
The only thing I can still think of is that the password contains some characters that might trip up yaml, but even then I’d have expected a “wrong password” API response, not just “Unavailable” with the correct name of the device being registered in Home Assistant.
The climate configuration block is the same as the documentation, but in a different order. It has a device: airconwithme entry too. The order should not matter, however.
Well it always better to post your configuration, it helps to move forward with the issue.
Also, set integration log level to debug to obtain more detailed logs.
configuration.yaml
logger:
logs:
homeassistant.components.intesishome: debug
This is the exact configuration I have used. (As you can see the order matches the documentation.)
climate:
- platform: intesishome
username: athroughz
password: CapitalLettersAndNumbers32
device: airconwithme
The error I get is:
homeassistant-2022.2.9/lib/python3.9/site-packages/homeassistant/components/intesishome/climate.py", line 214, in async_added_to_hass
await self._controller.add_update_callback(self.async_update_callback)
TypeError: object NoneType can't be used in 'await' expression
I tried replicating your configuration, but it still works fine for me in HA 2022.4
Try adding quotes between both username and password, for example:
climate:
- platform: intesishome
username: "USERNAME"
password: "PASSWORD"
device: airconwithme
If that does not help, enable debug logging for IntesisHome integration, that I mentioned in my comment above.
My IntesisHome integration logs after HA restart with debug logging enabled:
2022-04-06 17:31:18 DEBUG (MainThread) [homeassistant.components.intesishome.climate] Added climate device with state: {'name': 'Kondicionierius', 'widgets': [15, 3, 5, 7, 17, 9, 13], 'model': 550, 'power': 'off', 'mode': 'cool', 'fan_speed': 3, 'vvane': 'swing', 'setpoint': 230, 'temperature': 230, 'remote_controller_lock': 1, 'working_hours': 1149, 'alarm_status': 0, 'error_code': 0, 'quiet_mode': 'off', 'setpoint_min': 180, 'setpoint_max': 300, 'outdoor_temp': 30, 'error_reset': 0, 'config_mode_map': 63, 'runtime_mode_restrictions': 0, 'config_horizontal_vanes': 0, 'config_vertical_vanes': 1054, 'config_quiet': 0, 'config_confirm_off': 0, 'config_fan_map': {1: 'quiet', 2: 'low', 3: 'medium', 4: 'high'}, 'external_led': 'on', 'internal_led': 'off', 'internal_temperature_offset': 0, 'temp_limitation': 'off', 'cool_temperature_min': 240, 'cool_temperature_max': 280, 'heat_temperature_min': 230, 'unknown_uid_50008': 1, 'unknown_uid_50009': 3, 'unknown_uid_50010': 255, 'rssi': 198}
2022-04-06 17:31:18 DEBUG (MainThread) [homeassistant.components.intesishome.climate] Connection to airconwithme API was restored
2022-04-06 17:31:18 DEBUG (MainThread) [homeassistant.components.intesishome.climate] airconwithme API sent a status update for device None
Also, you could try deleting whole climate block from your configuration.yaml and then restart HA. After restart, go to Configuration → Devices & Services → Entities → Search for your old air conditioner entity → Click on it → Delete (steps could be different, because you’re on older HA version). Then re-insert your climate configuration block again, and once again restart HA.
This suggests that part of it works, but then it dies with the error as shown before.
DEBUG (MainThread) [homeassistant.components.intesishome.climate] Added climate device with state: {'name': 'Name_As_In_App', 'widgets': [15, 3, 5, 7, 17, 9, 13], 'model': 550, 'power': 'off', 'mode': 'heat', 'fan_speed': 4, 'vvane': 'manual2', 'setpoint': 210, 'temperature': 230, 'remote_controller_lock': 0, 'working_hours': 0, 'alarm_status': 0, 'error_code': 0, 'quiet_mode': 'off', 'setpoint_min': 180, 'setpoint_max': 300, 'outdoor_temp': 100, 'error_reset': 0, 'config_mode_map': 63, 'runtime_mode_restrictions': 0, 'config_horizontal_vanes': 0, 'config_vertical_vanes': 1054, 'config_quiet': 0, 'config_confirm_off': 0, 'config_fan_map': {1: 'quiet', 2: 'low', 3: 'medium', 4: 'high'}, 'external_led': 'on', 'internal_led': 'off', 'internal_temperature_offset': 0, 'temp_limitation': 'off', 'cool_temperature_min': 240, 'cool_temperature_max': 280, 'heat_temperature_min': 230, 'unknown_uid_50008': 1, 'unknown_uid_50009': 3, 'unknown_uid_50010': 255, 'rssi': 204}
I tried adding adding quotes, but it doesn’t make any difference.
Strange. Try to override integration with new version, that I mentioned in 1st reply.
I have also done that (and upgraded to a recent HomeAssistant version). I still get the NoneType issue.
Not sure if you’re still stuck here - but I think it might work if you exclude the “device” part? I remember having trouble initially.
Otherwise, there’s a an alternative version with a config flow here:
jnimmo/hass-intesishome: Experimental fork of the IntesisHome integration for Home Assistant (github.com), which is what I’m currently using with the same Intesis module as you.
Thanks a lot for replying to this thread. The current integration still fails randomly after a few days (their mobile app works fine, however).
So, the author of that module has it wrong when it says that it isn’t working?
Which exact configuration are you using?
I’ve realised that I found this because I was looking for things re: the specific wifi module, but I’m actually using Intesis AC Cloud rather than airconwithme, which may be the difference here. Anyway, just to be certain I’ve switched back from HACS to the standard integration, my configuration.yaml is as follows:
With username and password being those for AC Cloud.
Once that’s saved, restart HA and I magically had a new Living Room climate entity (no integrations or devices visible, just the entity) climate.living_room, which I can use to control the system.
I realise that I may have filled you with false hope (sorry!), but I’ve included everything just in case it helps.
I don’t really get it; you use the exact same IS-ACX-WIFI-1 module, but yet there are two different clouds?
It might also just be a white label thing, but then one would expec the integration to be compatible.
Comparison: Intesis AC Cloud vs Airconwithme suggests that they are different things.
Yeah, it’s strange - I was actually expecting to get a completely different module when ordering (this one doesn’t seem to support the local connection), but it’s working otherwise. Those two apps have the same developer (HMS), and looking through the pyIntesisHome code it looks like the only different is the API endpoint.
May I suggest trying hass-intesishome as a next step? It’s not only a bit easier to set up (once you download the files, anyway) but also has a couple of extra compatibility and bug fixes.