Unable to install latest beta version using HACS as a fresh install

[Kars-de-Jong]

When selecting a beta version, it can’t be installed. I believe this is caused by the rename of evohome_cc to ramses_cc. As you can see from the log below, HACS still tries to use the old name.

Deze fout is ontstaan door een aangepaste integratie.

Logger: custom_components.hacs
Source: custom_components/hacs/websocket.py:286 
Integration: HACS (documentation, issues) 
First occurred: 07:53:10 (6 occurrences) 
Last logged: 09:36:45

No manifest.json file found 'custom_components/evohome_cc/manifest.json'

[zxdavb]

This the one that currently says: DO NOT INSTALL? :)

Have a look at it's release notes, which include:

Via HACS, check that Show beta versions is enabled for the Evohome RF integration. If you get an error message, No manifest.json file found, you can ignore it. Then restart HA.

[zxdavb]

You can by my first tester.

[Kars-de-Jong]

This the one that currently says: DO NOT INSTALL? :)

Yes, that one. It’s a new install, so it doesn’t really matter for me. And I need the new Orcon stuff ;-)

Have a look at it's release notes, which include:

Via HACS, check that Show beta versions is enabled for the Evohome RF integration. If you get an error message, No manifest.json file found, you can ignore it. Then restart HA.

Hm, OK. I thought I already did that.

[Kars-de-Jong]

Nope, sorry, it doesn’t install it. It’s not in the custom_components folder, and doesn’t show up in integrations.

[zxdavb]

Hmmm.. Try installing 0.18.x then upgrading?

[zxdavb]

I have a suspicion that this issue will persist until 0.20.x is not a pre-release.

[Kars-de-Jong]

Can’t you make a new stable release with the rename?

[zxdavb]

No. it is too big a change - it wont be 'stable' - it is a breaking change, and a one-way migration. No-one has done it successfully, except for me!

I have just tested the process I suggested above: just enable Show beta versions, download 0.18.8 and reboot HA.

Have you tried it?

[Kars-de-Jong]

Yes, that procedure works. It does leave the old version in the evohome_cc directory, can I safely remove it?

[Kars-de-Jong]

I removed evohome_cc, because the logs of HA suggested the integration was started twice.

[zxdavb]

It does leave the old version in the evohome_cc directory, can I safely remove it?

Correct x2: It will, and you can.

[zxdavb]

I removed evohome_cc, because the logs of HA suggested the integration was started twice.

Hmmm... As long as the integration, evohome_cc:, is missing from configuration.yaml, then the evohome_cc folder will be ignored.