Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Startup delay in Home Assistant add-on #364

Closed
0xygen8 opened this issue Jul 24, 2020 · 6 comments
Closed

Startup delay in Home Assistant add-on #364

0xygen8 opened this issue Jul 24, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@0xygen8
Copy link

0xygen8 commented Jul 24, 2020

**zigbee2mqtt add-on version 1.14.2
**Operating environment homeassistant/intel-nuc-homeassistant:0.112.4
Description of problem:
When I restart the system (due to OS upgrades) the plugin never starts ok, (all states in HA stay Unknown) when I restart the plugin it works all right (race condition?)
This would could be a easy fix to start the container with a delay (configurable from frontend)
@fufar
Copy link

fufar commented Sep 2, 2020

same problem, it will be nice

@ciotlosm
Copy link
Collaborator

ciotlosm commented Sep 17, 2020 •
edited

Can you use the watchdog feature from Home Assistant to make sure add-on is up?

Watchdog
This will start the add-on if it crashes

@ciotlosm ciotlosm changed the title [Feature request] Startup delay in HASS.IO plugin Startup delay in Home Assistant add-on Sep 17, 2020
@ciotlosm ciotlosm added the enhancement New feature or request label Sep 17, 2020
@0xygen8
Copy link
Author

0xygen8 commented Sep 17, 2020

Today I retested this with watchdog enabled (on v1.14.4) and it started OK -- have to test more to see if it is magically resolved... @fufar can you retest also?

@ciotlosm
Copy link
Collaborator

I will close this for now. If something still not working after using watchdog please reopen.

@ciotlosm
Copy link
Collaborator

@0xygen8 @fufar I've also added #393 as this might improve things as well.

@0xygen8
Copy link
Author

0xygen8 commented Sep 19, 2020

That sounds like a real fix in opposite to the startup delay, thank you!

@ciotlosm ciotlosm mentioned this issue Sep 19, 2020
Closed
4 tasks
@ciotlosm ciotlosm added bug Something isn't working and removed enhancement New feature or request labels Sep 19, 2020
@ciotlosm ciotlosm mentioned this issue Sep 19, 2020
Merged
4 tasks
ciotlosm added a commit that referenced this issue Sep 22, 2020
@ciotlosm
Fixes and documentation updates (#394)
23661bf 
- Fixes #146, #229, #364 and #392
- Updates changelog
- Add changelog for `edge`
- Moves part of documentation in DOCS.md for `stable`
- Adds Readme.md for `edge`
- Added logo.png to display on add-on page automatically
- Fixes add-on startup according to docs
- Fixed commit unknown in plugin
- Removed some centre styling for titles and added warning emoji
- Removed some centre aligns for consistency
- Simplified change log header and move details to root readme
- Cleaned up change log completely to show only changes and move rest of meta to root readme
- Updated change log with better details
- Added docs for supporting new devices using new method
- Updated changelog based on diffs in tags on the repo
- Improved visibility of breaking changes in change log
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes addon startup according to docs
3 participants
@ciotlosm @0xygen8 @fufar