HACS and this fork vs original

[neildsb]

hi @jwillemsen I have a silly/simple NOOB question, I have just installed this fork and removed the original, I have noted the great re-work creating this integration, should we use this fork over the original iteration? and when do you think it will be available on HACS?

[jwillemsen]

See hacs/default#2234 for the PR to add this integration to HACS. I will maintain my fork in the future, I have regular Daikin AC units and an Altherma at home.

[GroGerome]

You can kind of use it trough HACS if you ad the Github as custom repositorie. I've installed it that way and that worked perfectly.

[mihsu81]

After the renaming to daikin_onecta it's not possible to install the master or beta 4.0.0 when added as a custom repository in HACS.
The old name daikin_residential_altherma still seems to be referenced somewhere.
Readding it as a custom repository with the new name doesn't help either.
Any idea?

Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/hacs/repositories/integration.py:173
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 13:28:34 (1 occurrences)
Last logged: 13:28:34

[140220736270400] Error handling message: Unknown error (unknown_error) xxx from 192.168.45.117 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 Edg/121.0.0.0)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
    await func(hass, connection, msg)
  File "/config/custom_components/hacs/websocket/repository.py", line 177, in hacs_repository_version
    await repository.update_repository(force=True)
  File "/config/custom_components/hacs/utils/decorator.py", line 28, in wrapper
    result = await function(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/repositories/integration.py", line 126, in update_repository
    if manifest := await self.async_get_integration_manifest():
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/repositories/integration.py", line 173, in async_get_integration_manifest
    raise HacsException(f"No {RepositoryFile.MAINIFEST_JSON} file found '{manifest_path}'")
custom_components.hacs.exceptions.HacsException: No manifest.json file found 'custom_components/daikin_residential_altherma/manifest.json'

[jwillemsen]

It looks HACS has a problem with a pre release that has a different integration name, I have removed the pre-release tag, can you try again

[PetitBird]

This problem occurred also with the master version before the pre release of the v 4.0 and after the rename of your fork.
I was away from home the last days and could not pull the new master version from HACS.
Had to copy files via samba share on return.

[jwillemsen]

The v4 release is now public, hopefully that resolves the issues with HACS. Waiting on the logo's for daikin_onecta to be merged, after that I can make my PR to add daikin_onecta to HACS again non-draft

[PetitBird]

It works now, both v 4.0 and master version

[eupesco]

Sorry, I am a bit confused now. I now have the Onecta integration (added to HACS as a custom repository) as well as the Daikin Residential for Altherma 3 integration. Should I delete the Daikin residential integration and just use the new Onecta integration? When I remove the Onecta integration as a custom repository, I can no longer find it in HACS.
What is the correct way? Thanks!

[jwillemsen]

The Daikin Onecta integration is not yet available in HACS, you have to add first https://github.com/jwillemsen/daikin_onecta as custom repository in HACS, after that you should be able to download the integration. So, keep daikin_onecta as custom repository in HACS, when you remove it you will not see it