-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Hass.io #3732
Add support for Hass.io #3732
Conversation
FWIW I See you've taken great care to provide a lot of things to make this a well-behaved and functionality-complete config. I worry that the supported architecture is very limited. In hassio.sh@32 it might be worth noting that You've clearly looked closely at details, and I expect this is running on your person system? It makes me want to try it on my avoton. I notice you're commenting on #3731 as well. |
|
@chickenandpork When can I expect this to be merged? |
Often that depends on who else has time to test and verify. The builds for Synology are really expensive in terms of time and test tiers, so they get scheduled when there are some ready and the personal projects are also complete. My original python3.5.6 work took so long, 3.6.8 was out. Maybe needed more cross-platform verification. I do think we need a way to automate some portion of testing so that we can check for compatibility a bit more autonomously. I’m used to working at companies that do this automatically, trying to think on how we can move to something a bit more efficient. I’ve got some work in that area to explore. Personally, I’m curious to try your work in a week or so when I get back from travels. |
I have 16 ❤️ here not sure if that means users that have tested and verified but at least it's something 😄 Tack your time and enjoy your travels @chickenandpork Edit: I've also got 40 ⬆️ here |
Well, if this can help, I use it on my xpenology NAS for 2 weeks. |
@fredrike Thanks for this contribution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it is our first Docker-based package, many questions...
Then improvement proposal to reduce maintenance effort.
@ymartin59 When a package is upgraded, will the files in the new package replace the old ones (in my case the What is the best way to ensure that the |
@fredrike @chickenandpork Thank you both! |
After 6 months are we finally going to see this merged 😳 |
Congratulation team! |
Thank you all! |
It is still not merged so I'm not super optimistic.. |
@chickenandpork @ymartin59 We all would very much appreciate your attention on getting this PR close out. Thank you very much! |
I think the existing work still suffers from lacking the restart that happens on a hassio on a RaspPi: when HA stops in a Pi, IIRC the Pi restarts. This means it doesn't need to get right the shutdown of addons and such. I want to clarify that I don't see this as a failing: there's a previous comment about being similar to upstream, but upstream has some luxuries :) I really appreciate @fredrike 's work here. Stop and Start are cleaner than I saw before; this is awesome.
"Updating" 20191224-1 to 20191224-1 seems to make no change. Delete and install looks OK if I manually stop and delete my add-ons. Unlike previous runs, this is good in the mode of "just reinstall and it'll do the right thing". More people using this will clarify what circumstances images might still be running or any other issues. I accept but I can't speak for @ymartin59 Be aware that accepted PRs become mergeable but there's a lag between that and building a release (based on space and cycles on a CI I think) but this one is a quick build so not as bad for this SPK. |
Uninstall of the package should remove the dns container. It would be fairly easy to make sure that all containers are stopped when stopping the package. Together with removing all related images.
@fxstein, do you have an idea of how to detect the missing |
@ymartin59 I think this resolved the four issues you raised 2019-11-30:
Looking for your OK with this work, and that any remaining issues can be pushed to a bug fix, so that @fredrike can get this merged. |
docker network rm hassio | ||
|
||
if [ "${wizard_remove_addons}" == "true" ]; then | ||
# Remove addons |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chickenandpork, so you are saying that this doesn't work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I publish for x64 architectures as beta for a first revision.
STARTABLE = yes | ||
DISPLAY_NAME = Hass.io | ||
CHANGELOG = "" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BETA = 1 |
Great, thanks! Docker is only supported on x64. May i ask why beta and why you are so skeptical on this? |
Due to popular demand: When can we expect this to become available through the package manager? |
|
||
service_poststop () | ||
{ | ||
docker stop hassio_supervisor homeassistant |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ADDONS=$(jq -r '.user| keys| map("addon_"+.)| join(" ")' $(jq -r '.data + "/addons.json"' ${CFG_FILE}))
docker stop $ADDONS
At the moment, publish fails. A fix in spkrepo or in package is required: SynoCommunity/spkrepo#39. Investigations in progress. |
@fredrike May you please register here with your github username: https://synocommunity.com/register so that I declare you as package owner. |
is home assistant development still active? I see the package as beta and cant seem to find much development/progression? I could be looking in the wrong places though. Thanks. |
Well, I don't have any bugs to solve..
It is @ymartin59 that requested it to be BETA, #3732 (review). I would be happy to remove the BETA flag but have not been following the https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559 thread closely but it seems like @BeardedConti manages to get most configurations to run flawlessly. |
Well when removing the package it doesn't remove all the created containers. Like hassio_dns and hassio_cli and some more I cannot remember atm |
I've updated the package, but I don't see the BETA flag.. |
I've checked few time and also don't see BETA flag. |
Your Package Center has not yet updated content: https://synocommunity.com/package/hassio |
I readded the community to my package manager but for me it is still showing up as beta as well ;) and I do not see the new version.
edit: |
Motivation: The Home Assistant package runs HA natively in Python, the preferred way is to run hass.io and let it manage HA via Docker.
Checklist
all-supported
completed successfully