Copied the files from /homeassistant/components/august into my /custom_components
Changed manifest.json so it referred to py-august==0.10.1
Restarted home assistant
Worked just like it always used to. Now I will just wait until these changes make it back into the mainline Home Assistant code and then I will remove the august folder from custom_components.
I was able to copy the entire august folder into my custom components folder. I did also make the change to the manifest.json. Restarted home assistant and everything is working as expected.
@Mathblais You create the custom_components under the āconfigā folder (the same place you have your config files). you leave the components/august.
@TryingHA
So I just create /custom_components folder same place i have configuration yamlsā¦ then move over the downloaded August folder from the gitā¦
And need update that json file in the folder moved.
Stop - start and all should be goodā¦
Is that correct?
@TryingHA, @Mathblais - note that the fix from BDraco was integrated into dev yesterday. If youāre pulling from that branch thereās no need to modify anything.
It seems that the folks at August were not so thrilled with the number of API calls unofficial integrations were making, which likely lead to the implementation of the HTTP 429s. That might seem understandable given how many requests the current component is making, especially if you have many August devices.
The goal is to make home assistant more sustainable for August, and reduce the amount of load on their servers as much as possible. The hope is that there isnāt any need for them to do any more disruptive rate-limiting, and the component stays working for everyone.
@bdraco is there anything preventing Home Assistant from becoming an officially supported partner? Google, Control4, and a few other usual suspects are listed in the āworks withā section. Maybe those companies pay for the privilege, but maybe not?
I donāt have any insight into Augustās business practices; however Google and Control4 likely more wall known to August than Home Assistant. I think the next step would be to try to establish contact with someone in August who can help build a partnership on moving to an official integration status.
@bdraco Thanks! I had previously written a very friendly letter to August support about the issue, and asking how Home assistant could become an officially supported partner. I did get several responses from 2 different employees and they ultimately suggested starting the process of having an official integration developed for Home Assistant through a partnership. The last response I received below:
Hello Timothy,
Thanks for reaching out to us. We recommend contacting Home Assistant directly to request they begin the process of partnering with us to create an integration. You can reach them by sending an email to: [email protected]
please let us know if you have any further questions or concerns.
Thank you,
Jack
Team August
I donāt think they fully understand the nature of open-source projects, so I guess they would expect to be contacted by an employee of a companyā¦ Iām not sure if it would be out of place for me to contact August on behalf of the Home Assistant project, or if a more experienced contributor should take on that role, but Iām happy to carry the torch if others agree. Is there anyone we should run this by before proceeding? @balloob perhaps?
I did not change anything, I simply updated and the integration started to work. Maybe you should remove the .aufust.conf file and reboot HA and make the authentication process again.
Hi, @bdraco I noticed in https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/august, the version of august still shows py-august 0.8.1. Is this the version that is in 105.3? In the custom component I put 10.1 to get it working in the mean time. I see py-august is at 0.11.0. I know there were a lot of improvements from 0.8.1 to 0.11.0. Thanks again for all your work on that.
