-
Notifications
You must be signed in to change notification settings - Fork 878
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 warning that REST API is no longer supported #2150
Conversation
This really needs to be merged so people don't rely on the REST API for new projects and then get burned...not that I would know anything about that! 🙃 In addition, I don't remember seeing any mention of this on the blog. Has there been a post about it? |
Deprecating the REST API is a really bad idea and will put a stop to projects based on cheap hardware (esp32, etc.). Calling the websocket API on such hardware is unnecessarily complicated. |
@sebsebseb1982 I learned today that getting states with the Websocket API is actually impossible on memory-limited platforms like those. I thought there would be a command message to ask the server for the state of a single entity or list of entities, but no, you can only request the state of all entities. This array would take up more memory than embedded devices have, and iterating over an array of a thousand or more entities would take forever even if it fits. I would really appreciate some justification from Home Assistant leadership as to why the REST API is being |
Thank you @Klikini for this warning. |
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.
The rest API is not deprecated, going away, or planned to go away etc.
I just ran into issue home-assistant/core#99820 and spent over an hour banging my head against the wall trying to figure out why it wasn't working. That is frustrating to say the least. I agree it seems like the REST API is EOL, will no longer have features added, or at least the get_forecasts will never be supported in REST. Since at least one of those statements is true, can we at least get a more clear error message to help others who wind up here? |
closing this PR per #2150 (review) |
Proposed change
According to home-assistant/architecture#1074 (comment) the REST API has been superseded by the WebSocket API. There was no mention of this anywhere in the documentation, so I'm adding a warning to let people know.
Type of change
Additional information
get_forecast
service returns 500 on 2023.9.0 core#99820