I can confirm that by simply importing the zip file provided by @mhoogenbosch earlier, I am able to get my 3 myanywair wifi devices integrated with HA finally!
Hi all,
I have published a fork of what I believe to be the latest version of the integration to jnimmo/hass-intesishome: Experimental fork of the IntesisHome integration for Home Assistant (github.com). You can drop this into HACS as a custom repository, and then configure it using the user interface (config flow). Any required changes should be submitted as pull requests there. Anything major not working let me know as I may have missed something while resolving conflicts.
This version supports Intesisbox, Intesishome Local and of course cloud control. I should note, Intesisbox support of it hasn’t been widely tested, so if you have issues probably use http://github.com/jnimmo/hass-intesisbox instead. Ideally these would be combined at some stage
When I get a chance I’ll import the proper git history for the code base for version control.
Unfortunately this is the last code I intend to write for integration/pyIntesisHome, and I’m looking for a new maintainer for these projects. I haven’t used Intesis devices for years now and this project is taking me away from other more important priorities. This integration was the reason I learnt Python so it’s always been a bit of a special project for me, but I no longer have time to keep up with changes in Home Assistant Core let alone bug fixes.
Thanks very much for the kind words and to those who have assisted over the years and provided test accounts etc.
This works great for me. I have the DK-RC-WIFI-1B for my Daikin unit. Thanks! Hope someone can pick this project up. Guess I won’t be upgrading HA for a while now.
Glad to hear it’s working, and thanks for the screenshots @Chilling_Silence!
There has only been a handful of changes required over the years for keeping up with Home Assistant or even changes to the Intesis API, and plenty of devs or potential devs out there using it so I’m confident you’ll be able to keep upgrading Home Assistant.
Thanks for pushing all PR’s thus making it work from HACS. Just removed my custom integration which was self-modified and added your repro, it works great! Again; thanks.
Would it be possible to add a very minor change to the readme file? To show which modules are known to work with local integration and which aren’t?
As far as I could see the following are confirmed to work with local:
@jnimmo Many, many thanks. Good work. Runs well for me (MH-AC-WIFI-1) at first glance. The cloud via airconwithme was/is the purest disaster. Finally local control possible.
Please open an issue on https://github.com/jnimmo/pyIntesisHome with debugging information if the cloud control was not working well, it should be stable, and believe is for some people.
Credit to @rklomp for the local integration, I’ve just been unable to get it added to core and haven’t had time to package it up as a separate repo.
I got “Became unavailable” via Home Assistant with the cloud version of IS-ASX-WIFI-1 12 hours ago (and it didn’t get back up). When using the airconwithme app, the data is visible, which means that your integration is not stable.
I am not running your latest code, but you didn’t say you implemented anything to increase reliability. If you did, please provide git hash and repo name such that I can upgrade efficiently and there is no misunderstanding about versions.
For anyone to be able to troubleshoot theee issues, debug logs are required. These can be configured by adding the block below to your configuration file, then you would need to search the log to pull out the integration and pyintesishome lines.
If you’ve patched it yourself then please consider creating a pull request so the rest of the community can benefit from it also.
logger:
default: info
logs:
custom_components.intesishome: debug
homeassistant.components.intesishome: debug
pyintesishome: debug
@jnimmo Thanks a lot! This works great and exactly what I was looking for after the cloud connection of my airconme devices dropped many times last few days. Just 15 minutes ago I came to this page and installed the repo with local connection. Works like a charm. Glad i can now forget about the ‘cloud connection nightmare’ Cheers
Sorry need full debug logging as I specified before. If you review the code you will find there is indeed automatic back off and retry, but clearly something is wrong and without more detailed logging can”t see what the connection is in relation to.
Please raise an issue on GitHub with the full debug logging context, and confirm you are running either the latest HACS release.
However I can’t find anything in the logs relating to it? I’m potentially not looking in the right place, but all I could find that may have been relevant was:
Source: components/websocket_api/connection.py:102
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: August 19, 2022 at 1:48:37 PM (5 occurrences)
Last logged: August 20, 2022 at 4:32:08 PM
[140254918134848] Error handling message: Unauthorized (unauthorized)
[140255337373440] Error handling message: Unauthorized (unauthorized)
[140255040132416] Error handling message: Unauthorized (unauthorized)
[140254747428848] Error handling message: Unauthorized (unauthorized)
[140254961536784] Error handling message: Unauthorized (unauthorized)
Can anyone point me to where I should be seeing the logger entries?
I have this set and have restarted HA since.
Yeah the Return Path Temperature is the “current observed” temperature, as opposed to the target. The target temperature is being updated all good Even after the return path stops being updated.
I take it you can also log in to your WebUI and confirm the discrepancy there too?
At work, I only used the myanywAiR app to join them to the WiFi, and local control only, they never got joined to an account etc so aren’t doing any cloud stuff that could be conflicting. At home though I joined them fully to the app / account so it’s not anything there I would think causing it either given I’m seeing this occurring at both places.
