oh thats brilliant! thanks.
EDIT: 15 minutes in, and things are working well.
fast forward 7 days, and things are going really well. This feels more like a mature beta than an alpha 
Hey @ludeeus, Iām currently running HA in Docker, but got v2 up and running (albeit on a temp install to be safe). It correctly found my existing custom integrations and front-end modules and I was able to install a few additional ones as well, so I think everything is working correctly.
Besides the extra steps needed to clone & configure the integration within the container, are there any other pitfalls (e.g. any potential changes to schema, etc.) that would be specific to this type of installation? Or if I was able to install the new version correctly and am keeping both the front-end & integration repos up-to-date, will this be generally equivalent to the currently supported install methods?
Not really. The only reason I kept it to OS/Supervised for now is that they have add-ons that make the download/bundle step run in a controlled way without many variations.
1 Like
Did anyone try this that did not run experimental features before?
Was there something that was missing from being noted in the OP?
Nah, I was running experimental.
Iād love to use that switch, but in the listings I cant find any hidden entityā¦
all I see is this:
while running this version:
That is 3 weeks oldā¦
The switch was merged today.
sorry for that, I had not seen an update (the add-on want runningā¦)
this is better now:
somehow several are enabled even while this is in the docs:
By default, these switch entities are disabled
was there some previous setting being imported?
edit
nvm, it must have been the beta toggleā¦ sorry.
very nice indeed!
Yes, the documentation is more aimed at new users.
For those upgrading, it will be enabled by default if you previously had the beta toggle set to True.
1 Like
Is there no option to download the latest commit? Main/master? Is it just releases?
1 Like
If I try master, it tries to download the following, which doesnāt work since there is no āmasterā release.
https://github.com/al-one/hass-xiaomi-miot/releases/download/master/xiaomi_miot.zip
Neither does the latest SHA work. Tries downloading from here:
As the documentation say, not everything will work, and you should not be doing this without instructions from the author.
In this case it will not work because of these https://github.com/al-one/hass-xiaomi-miot/blob/eae059c209496bcfc516d179664ca70e708f041d/hacs.json#L4-L5
1 Like
just to confirm, this pre-release button is for beta/pre-release versions that may be available for the intergrations, etc.
Yes, there is example in the docs
1 Like
So do I have to use the addon to get the latest release or can I use HACS to update HACS?
Because the addon logs say:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:26:52] INFO: ------------------------------------
[09:26:52] INFO: Starting HACS download...
[09:26:52] INFO: Channel: development
[09:26:52] INFO: ------------------------------------
[09:26:52] INFO: Downloading the integration source...
Cloning into '/tmp/hacs'...
fatal: unable to access 'https://github.com/hacs/integration.git/': The requested URL returned error: 502
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
And HACS wants to download v1.34.0
EDIT: tried restarting the add-on again. Now it just hangs at:
[09:33:00] INFO: Downloading the integration source...
Cloning into '/tmp/hacs'...
Eventually:
remote: Internal Server Error
fatal: unable to access 'https://github.com/hacs/integration.git/': The requested URL returned error: 500
Guessing that was likely to do the large-scale Github outage earlier today. Curious to see if you got it working now. Looks like Github is back up and running.
1 Like
Yeah looks like that was the reason. All good now.
[10:53:02] INFO: ------------------------------------
[10:53:02] INFO: Starting HACS download...
[10:53:02] INFO: Channel: development
[10:53:02] INFO: ------------------------------------
[10:53:02] INFO: Downloading the integration source...
Cloning into '/tmp/hacs'...
[10:53:03] INFO: Installing the frontend...
Looking in indexes: https://pypi.org/simple, https://wheels.home-assistant.io/musllinux-index/
Collecting hacs-frontend==20240729171855
Downloading https://github.com/hacs/frontend/releases/download/20240729171855/hacs_frontend-20240729171855-py3-none-any.whl (16.6 MB)
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā 16.6/16.6 MB 10.0 MB/s eta 0:00:00
Installing collected packages: hacs-frontend
Successfully installed hacs-frontend-20240729171855
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
[10:53:07] INFO: Injecting a version...
[10:53:07] INFO: Version set to: 2.0.0-dev-a34d9c4
[10:53:07] INFO: Copying the integration source...
[10:53:07] INFO: Download complete...
[10:53:07] INFO: Remember to restart Home Assistant before you configure it...
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
My question is now - can I enable that switch for the HACS integration and no longer need the add-on? 
No, that switch uses github preeesleases.
These are not releases, which is why the add-on must be used.
With that said, i do not expect much if any change now until then release.
1 Like