[WIP] Add homeassistant-supervisor container to improve Home Assistant Voice Assistant stack onboarding on Jetson devices
#505
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…with twine upload
…rate package with twine upload
|
This is awesome @ms1design, good luck in your mission! 🙏 The crew from Seeed Studio would also probably be interested to help you with this if you didn't already show it to them. |
|
It's funny—I discussed it with Elaine, but back then, I advised against using supervisor because I found it too complicated to support or use. 🙈 Welcome to my world 😆 |
May 15, 2024 updateLogs: _hassio_supervisor_logs.txt
|
May 16, 2024 UpdateI'm happy to share a significant breakthrough: the successful setup of the This bringing us one step closer to harnessing the power of edge computing for AI/ML Home Assistant solutions 🦾 🤖 The next step would be streamlined install and uninstall process for Jetson devices. 
How it WorksThe journey to this milestone has been marked by quirks and challenges, but overall idea was to:
Quick Start Guide
Before launching the Jetson Host Machine Configuration
Initiating ContainersExecute the following command to launch the docker run -d \
--name hassio_supervisor \
--hostname supervisor \
--privileged \
--cap-add=ALL \
--security-opt seccomp=unconfined \
--security-opt apparmor=unconfined \
-p 80:80 \
-v ha-config:/config \
-v ha-share:/share \
-v ha-media:/media \
-v ha-supervisor:/data \
-v ha-supervisor-share:/tmp/supervisor/data \
-v /usr/bin/docker:/usr/bin/docker \
-v /run/docker.sock:/run/docker.sock:ro \
-v /etc/docker/daemon.json:/etc/docker/daemon.json:ro \
-v /var/run/dbus:/var/run/dbus \
-v /run/NetworkManager:/run/NetworkManager \
-v /etc/NetworkManager:/etc/NetworkManager \
-v /run/dbus/system_bus_socket:/run/dbus/system_bus_socket:ro \
-v /run/udev:/run/udev:ro \
-v /etc/udev/rules.d:/etc/udev/rules.d:ro \
-v /run/audio:/run/audio:ro \
-v /etc/asound.conf:/etc/asound.conf:ro \
-v /etc/pulse/client.conf:/etc/pulse/client.conf:ro \
-v /sys/fs/cgroup:/sys/fs/cgroup:ro \
-v /etc/systemd/resolved.conf:/etc/systemd/resolved.conf \
-v /run/systemd/system:/run/systemd/system \
-v /var/log/journal:/var/log/journal:ro \
-v /run/log/journal:/run/log/journal:ro \
-v /etc/machine-id:/etc/machine-id:ro \
-v /etc/localtime:/etc/localtime:ro \
-v /etc/timezone:/etc/timezone:ro \
--device /dev/snd:/dev/snd \
--device /dev/bus/usb \
ms1design/homeassistant-supervisor:latest-r36.2.0-cu122-cp312
Logs
|
|
Wow, okay! This is awesome @ms1design ! Hopefully this makes things a lot easier for everyone 🙏 That docker run command 🤣 If making those |
|
@dusty-nv, I’m rolling hard on this docker run command too 😂 it's a huge roll forward 🤣 especially when we realise how complicated it is to port all HA repositories and integrate them together. I was trying to make it work with almost no changes to the host machine, which leaves us with one critical error regarding udev permissions, among many other warnings as shown in the previous screenshots. These are not the best results from a user perspective. I’m tempted to extend the jetson-containers API to support installation and uninstallation scripts for host machines, which would essentially make the Dockerfile unnecessary for this container. We can tackle that with a little reorganisation:
My ideal plan is for the user to issue just one command on the host machine, which will install HA Supervisor with all system dependencies and optionally the full Wyoming Voice Assistant pipeline from jetson-containers. This might take some time :) |
|
Sounds like a good plan @ms1design. Thank you for looking into this - that's okay if it takes time, I appreciate you wanting to go about it the right way that is easiest for users. My guess/hope is this will all come together nicely around the time we have the more advanced agents operating and hopefully the new AI API's defined by HA. I have been working with the Anyways, yea - your HA Supervisor repo could include jetson-containers as a submodule if that aids in the one-click/one-command scripted setup. Others in the group have been using jetson-containers as a submodule in their projects and that design seems to be working well for them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
homeassistant-supervisorHi @dusty-nv 👋
To keep Home Assistant on Jetson project progressing, I'm revisiting the experiments with the Home Assistant Supervisor container. My aim is to simplify the onboarding process for Home Assistant and Wyoming add-ons on Jetson devices based on our experiences during the latest Jetson AI Research Group meeting.
While I'm not sure whether containerizing Supervisor and making it work with all its system dependencies is feasible, I'm willing to give it a shot. Below is what I tried yesterday and what should be done or fixed based on the
homeassistant-supervisorlogs.All questions and advice are warmly welcomed!
Updates:
May 8, 2024
Logs: _homeassistant-supervisor_logs.txt
homeassistant-supervisorcontainer.ciso8601andpsutil-home-assistant) to standalone, reusable containers in thesmart-home/dependenciesdirectory.homeassistant-supervisordependencyeudevin thesmart-home/dependenciesdirectory.403errors when fetching RAW files from GitHub injetson_containers/utils.js. This was achieved by switching fromurllib.request(which still usesHTTP/1.1) to therequestslibrary, enabling the use ofHTTP/2requests.jetson_containers/utils.py:handle_json_request,handle_text_request,github_latest_tag, andget_json_value_from_url.config.py.homeassistant-corecontainer'sbuild.shscript.homeassistant-supervisedcontainer.Quick Start
hostmachine runningdockerusing sameuser:docker-compose.yamlexampleTODO
Based on
homeassistant-supervisorlogsinstall.shscript forhostmachine if conterization is impossibleEnsure thathomeassistant-corecan detect thehomeassistant-supervisorcontainer and vice versahomeassistant-supervisorcontainer docker volumes & pathseudevdependency container to support independent build & install stages to allowdpkguploadFix theSUPERVISOR_MACHINEvalue to properly configurecoresys(generic-aarch64is used for now) to enable OTA updates:INFO (MainThread) [supervisor.bootstrap] Setting up coresys for machine: generic-aarch64WARNING (MainThread) [supervisor.updater] Can't process version data: 'generic-aarch64'~Fix thedockeravailability:WARNING (MainThread) [supervisor.resolution.evaluations.base] The configuration of Docker is not supported (more-info: https://www.home-assistant.io/more-info/unsupported/docker_configuration)CRITICAL (MainThread) [supervisor.supervisor] Can't setup Supervisor Docker container!WARNING (SyncWorker_0) [supervisor.docker.manager] Can't get None for cleanupdockerdeamon onhostmachine to support required method of logging (or find an easy way of doing that for users):WARNING (MainThread) [supervisor.resolution.evaluations.docker_configuration] Docker logging driver json-file is not supported!AppArmor(but where? in container or on host?):WARNING (MainThread) [supervisor.host.apparmor] AppArmor is not enabled on hostWARNING (MainThread) [supervisor.resolution.evaluations.base] AppArmor is required for Home Assistant. (more-info: https://www.home-assistant.io/more-info/unsupported/apparmor)WARNING (MainThread) [supervisor.resolution.evaluations.base] Supervisor does not run in Privileged mode. (more-info: https://www.home-assistant.io/more-info/unsupported/privileged)CRITICAL (MainThread) [supervisor.hardware.monitor] Not privileged to run udev monitor!Sort out trusted content security:WARNING (MainThread) [supervisor.resolution.evaluations.base] System run with disabled trusted content security. (more-info: https://www.home-assistant.io/more-info/unsupported/content_trust)WARNING (MainThread) [supervisor.security.module] Disabled content-trust, skip validationSort this out (could be because of useSUPERVISOR_DEV: 1):0.00s - Debugger warning: It seems that frozen modules are being used, which may make the debugger miss breakpoints. Please pass -Xfrozen_modules=off to python to disable frozen modules. Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.Fix the missingclidockerplugin in container:INFO (MainThread) [supervisor.plugins.base] No cli plugin Docker image None found.WARNING (MainThread) [supervisor.plugins.base] Error on installing cli plugin, retrying in 30secUnknown issue:INFO (MainThread) [supervisor.docker.interface] Found None versions: [<AwesomeVersion CalVer '22.04'>, <AwesomeVersion SpecialContainer 'latest'>, <AwesomeVersion SpecialContainer 'latest'>, <AwesomeVersion SpecialContainer 'latest'>, <AwesomeVersion SpecialContainer 'latest'>, <AwesomeVersion SemVer '2.19.4'>, <AwesomeVersion SpecialContainer 'latest'>]docker-composeexample: