integration VS openapi-generator

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/

Disclaimer: We're an early adopter of Stainless at Mux.

I've spent more of my time than I'd like to admit managing both OpenAPi spec files [1] and fighting with openapi-generator [2] than any sane person should have to. While it's great having the freedom to change the templates an thus generated SDKs you get with using that sort of approach, it's also super time consuming, and when you have a lot of SDKs (we have 6 generated SDKs), in my experience it needs someone devoted to managing the process, staying up with template changes etc.

Excited to see more SDK languages come to Stainless!

[1] https://www.mux.com/blog/an-adventure-in-openapi-v3-api-code...

[2] https://github.com/OpenAPITools/openapi-generator

As a result, the following specification can be used to generate clients in a number of different languages via OpenAPI Generator.

Of course you can compile the server from source if you have Go and the OpenAPI generator JAR (https://github.com/OpenAPITools/openapi-generator?tab=readme...)

Follow these steps : https://github.com/c100k/rebootx-on-prem/blob/master/.github...

And then :

(cd ./impl/http-server-go && GOARCH=amd64 GOOS=openbsd go build -o /app/rebootx-on-prem-http-server-go-openbsd-amd64 -v)

By adapting the arch if needed. Not tested, but it should work.

TL;DR: Start generating your HTTP clients and all the DTOs of the requests and responses automatically from your API, using openapi-generator instead of writing your own.

As an alternative, you can also use the official OpenAPI Generator, which is a more generic tool supporting a wide range of languages and frameworks.

I trialed generating SDKs using the OpenAPI Generator package, which was largely unsatisfactory.

If Swagger/OpenAPI is available, save yourself a lot of trouble and generate the client using OpenAPI Generator. If not, use a library like RestEase to make it significantly easier to create the client.

For a run of the mill REST API you should generate OpenAPI (Swagger) info for the API using a library like NSwag or Swashbuckle. You'd want to do this no matter what because it's documentation for the API, but the bonus is that you can use it with tools like OpenAPI Generator to create API client code and models in a variety of languages. You certainly can create an API client library manually, it would entail having a nuget package with a class library that contains the models and client code for calling the endpoints (which I'd create using a lib such as RestEase unless you just enjoy writing boilerplate code by hand). However 95% of the time it simply isn't worth creating your own lib when OpenAPI is available because once you've done it a time or two it takes less than 5 min to run the generator and create (or update) a lib.

Then you can use oapi-codegen or openapi-generator to generate the Go (or other language) SDK for it.