XiaomiGateway3 VS integration

Following the recommendation from u/flaquito and u/CorgiFinancial, and since I did not want to spend any additional time or money on getting new hardware, I ended up with the following. - Booted up my old laptop, which hasn't been used for 2 years, and set up the docker version of HASS. It was indeed very straightforward. In hindsight, I might redo the process and install either a VM or the supervised version, just so I can have the addons (seems like a cool thing to have). - Adding all WiFi-related things was super easy! TV, PS4, Chromecast, etc. For Yeelight, I had to enable "LAN Control" to all my lamps. - The Xiaomi Smart Home Hub is not offered by default on HASS. I found a custom integration on hacs.xyz (adding HACS integration was also straightforward). The custom Smart Home Hub can be found [here](https://github.com/AlexxIT/XiaomiGateway3). - Enabling the telnet mode was non-trivial for me, as I did not want to change the Mi server to China (seems it loses all current setup?). Note that most online guides tell you to swap over to China to get the "About" menu option so you can enable the telnet. Instead, I found [this](https://gist.github.com/zvldz/1bd6b21539f84339c218f9427e022709), which worked like a charm with the custom integration: first add the gateway using the Mi credentials (it reads the mappings and tokens from the Mi Cloud), then add the gateway *again* by selecting the direct IP + the above definition. You can then delete the cloud-based gateway.

I have HACS[0] installed in my Docker image, I use it for exactly one integration and the initial setup seemed a little dodgy but it's been pain-free for a couple of years now.

[0]: https://hacs.xyz/

Yeah! So first, get HACS if you don’t already have it (https://hacs.xyz), then the custom Tesla integration (https://github.com/alandtse/tesla) - side note: you’ll need to be able to get a refresh token for your account (iOS app: https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613)… once you have the integration setup, create an automation. It should trigger when your vehicle tracker enters home zone and you can set device > myQ to open. Lmk if you need more help or have questions

Adaptive lighting is not a default for Home Assistant. It's an addon. You can install it through HACS (which is an addon itself) https://hacs.xyz/

Once you have that, you can also install a lot of additional services that would require separate docker containers from the Addon Store (like PiHole) or HACS, which is where you'll get all the unofficially supported integrations. Frigate is an option in the latter, so I don't think you need a separate PC application, unless it's just to view.

Error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/job.py", line 411, in run await self.future File "/usr/lib/python3/dist-packages/middlewared/job.py", line 446, in __run_body rv = await self.method(([self] + args)) File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1140, in nf res = await f(args, *kwargs) File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1272, in nf return await func(args, *kwargs) File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/chart_release.py", line 481, in do_create await self.middleware.call( File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1345, in call return await self._call( File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1305, in _call return await self.run_in_executor(prepared_call.executor, methodobj, *prepared_call.args) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1206, in run_in_executor return await loop.run_in_executor(pool, functools.partial(method, *args, *kwargs)) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(self.args, *self.kwargs) File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/helm.py", line 44, in helm_action raise CallError(f'Failed to {tn_action} chart release: {stderr.decode()}') middlewared.service_exception.CallError: [EFAULT] Failed to install chart release: Error: INSTALLATION FAILED: template: home-assistant/templates/common.yaml:5:3: executing "home-assistant/templates/common.yaml" at : error calling include: template: home-assistant/charts/common/templates/loader/_apply.tpl:20:5: executing "tc.common.loader.apply" at : error calling include: template: home-assistant/charts/common/templates/spawner/_configmap.tpl:16:10: executing "tc.common.spawner.configmap" at : error calling include: template: home-assistant/charts/common/templates/class/_configmap.tpl:33:6: executing "tc.common.class.configmap" at : error calling tpl: error during tpl function execution for "configuration.yaml.default: |-\n # Configure a default setup of Home Assistant (frontend, api, etc)\n default_config:\n\n # Text to speech\n tts:\n - platform: google_translate\n\n group: !include groups.yaml\n automation: !include automations.yaml\n script: !include scripts.yaml\n scene: !include scenes.yaml\nhttp.default: |2-\n\n http:\n use_x_forwarded_for: true\n trusted_proxies:\n {{- if hasKey .Values \"ixChartContext\" }}\n - {{ .Values.ixChartContext.kubernetes_config.cluster_cidr }}\n {{- else }}\n {{- range .Values.homeassistant.trusted_proxies }}\n - {{ . }}\n {{- end }}\n {{- end }}\ninit.sh: |-\n #!/bin/sh\n if test -f \"/config/configuration.yaml\"; then\n echo \"configuration.yaml exists.\"\n if grep -q recorder: \"/config/configuration.yaml\"; then\n echo \"configuration.yaml already contains recorder\"\n else\n cat /config/init/recorder.default >> /config/configuration.yaml\n fi\n if grep -q http: \"/config/configuration.yaml\"; then\n echo \"configuration.yaml already contains http section\"\n else\n cat /config/init/http.default >> /config/configuration.yaml\n fi\n else\n echo \"configuration.yaml does NOT exist.\"\n cp /config/init/configuration.yaml.default /config/configuration.yaml\n cat /config/init/recorder.default >> /config/configuration.yaml\n cat /config/init/http.default >> /config/configuration.yaml\n fi\n\n echo \"Creating include files...\"\n for include_file in groups.yaml automations.yaml scripts.yaml scenes.yaml; do\n if test -f \"/config/$include_file\"; then\n echo \"$include_file exists.\"\n else\n echo \"$include_file does NOT exist.\"\n touch \"/config/$include_file\"\n fi\n done\n\n cd \"/config\" || echo \"Could not change path to /config\"\n echo \"Creating custom_components directory...\"\n mkdir \"/config/custom_components\" || echo \"custom_components directory already exists\"\n\n echo \"Changing to the custom_components directory...\"\n cd \"/config/custom_components\" || echo \"Could not change path to /config/custom_components\"\n\n echo \"Downloading HACS\"\n wget \"https://github.com/hacs/integration/releases/latest/download/hacs.zip\" || exit 0\n\n if [ -d \"/config/custom_components/hacs\" ]; then\n echo \"HACS directory already exist, cleaning up...\"\n rm -R \"/config/custom_components/hacs\"\n fi\n\n echo \"Creating HACS directory...\"\n mkdir \"/config/custom_components/hacs\"\n\n echo \"Unpacking HACS...\"\n unzip \"/config/custom_components/hacs.zip\" -d \"/config/custom_components/hacs\" >/dev/null 2>&1\n\n echo \"Removing HACS zip file...\"\n rm \"/config/custom_components/hacs.zip\"\n echo \"Installation complete.\"\nrecorder.default: |2-\n\n recorder:\n purge_keep_days: 30\n commit_interval: 3\n db_url: {{ ( printf \"%s?client_encoding=utf8\" ( .Values.postgresql.url.complete | trimAll \"\\"\" ) ) | quote }}": template: home-assistant/templates/common.yaml:19:18: executing "home-assistant/templates/common.yaml" at <.Values.ixChartContext.kubernetes_config.cluster_cidr>: nil pointer evaluating interface {}.cluster_cidr

Yup! There's a community integration you can install called Alexa Media Player. The easiest way to install it is by using HACS.

There's also an extended 'store' called HACS (Home Assistant Community Store) which basically has third-party, but still FOSS so you can audit the code, integrations which further expand. https://hacs.xyz/

[HACS](https://hacs.xyz/