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.

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

/api/bootstrap not available #10404

Closed
choongjoey opened this issue Nov 6, 2017 · 7 comments
Closed

/api/bootstrap not available #10404

choongjoey opened this issue Nov 6, 2017 · 7 comments

Comments

@choongjoey
Copy link

choongjoey commented Nov 6, 2017

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.57.2

Python release (python3 --version):
3.6.3

Component/platform:
frontend

Description of problem:
I noticed /api/bootstrap is removed in #9915

Refer to 6f764c0#diff-f49ba198ea571d90a85013efb63f8f44L297

Is this an intended removal or a side effect due to the consolidation?

Expected:
/api/bootstrap available to invoked - as per API docs.

@danielperna84
Copy link
Contributor

This change also broke some of the functionality of the HASS-Configurator (fetching entities etc.).

@PaulAnnekov
Copy link
Contributor

API was broken, tests didn't fail -> bad tests.

@danielperna84
Copy link
Contributor

Meanwhile it has been removed from the documentation as well: home-assistant/home-assistant.io@7cd00fb
So apparently this was intended. I'm unsure if this should have been mentioned as a breaking change, since internally it might not be used. But for 3rd party tools it's a problem.

@choongjoey
Copy link
Author

So any alternatives to using /api/bootstrap? especially since now its 'officially' removed.

@danielperna84
Copy link
Contributor

For the configurator the relevant parts were the entities, services and events. They all are available via separate API-endpoints. See the docs for what is still available. I don't know what else was part of the bootstrap. But the three I use availalbe in the exactly same format, just not within the containing object anymore.

@tadly
Copy link
Contributor

tadly commented Nov 13, 2017

I f.e. require a list of all entities with both their friendly and entity name.
None of the endpoints documented will provide these kind of information (/api/bootstrap did) afaik.

Edit:
Actually, never mind. /api/states seems to be good enough for my purposes

@danielperna84
Copy link
Contributor

Closing issue since the change seems to be intentional and workarounds are possible.

@home-assistant home-assistant locked and limited conversation to collaborators Mar 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants