Releases: fondberg/spotcast
v5.0.0-b21
v5.0.0-b20
v5.0.0-b19
Note
See v5.0.0-b0 for more detail about the v5
beta
- Implemented a retry supervisor to manage retry attempts when the Upstream Gateway for Spotify is unreachable
v5.0.0-b18
Note
See v5.0.0-b0 for more detail about the v5
beta
- Added filter for Internal Server Error when refreshing token. Will no longer expire credentials for integration. Currently will log errors. Working on a full implementation for wait and retry on gateway error.
v5.0.0-b17
Note
See v5.0.0-b0 for more detail about the v5
beta
New features
- Added service
like_media
- Added websockets endpoints:
spotcast/liked_media
spotcast/search
spotcast/tracks
spotcast/view
- Added ability to start playback from a podcast episode
- Improved services definitions
Bug fixes
- #501: Removed bad logger from
play_from_search
service - #502: Fixed issue with transfering active playback
- #503: Improved handling of token error on private api token refresh
Thank you @mikevanes for your contribution
v5.0.0-b16
Note
See v5.0.0-b0 for more detail about the v5
beta
- Added ability to make search queries on multiple types
- Ensure profile match between public and provate API on configuration
- Ensure entry not already in Home Assistant during configuration
- Add ability to restart playback from an empty context
- Make
start_media
service able to change media playback on active device when no device provided
v5.0.0-b14
Note
See v5.0.0-b0 for more detail about the v5
beta
- Added ability to resume playback for long gone playback (when the API no longer reports the playback information)
- Currently only works for albums or playlist at the moment.
- Custom context do not work and will raise an error
v5.0.0-b13
Note
See v5.0.0-b0 for more detail about the v5
beta
- Fixed issue with registering chromecast to spotify
v5.0.0-b0
Warning
This is a pre-release build. Do not install without reading the changelog and expect bugs. If you encounter any bugs, please fill out a Beta Reporting Ticket. Debug logs are expected from the user in these cases. Be ready to actively engage in any ticket opened.
This one was something to build. This here is the first pre-release for Spotcast Version 5. This new version of Spotcast is a complete rewrite of the application to modernise the project to current expectation from Home Assistant and also remove our dependency on the main Spotify Integration as much as possible. There are still a few items to solve, but I feel the code is at a place where testing by a larger audience will be a benefit. For anyone wanting to test out this new version.
Roadmap
- Rewrite of the core system with its own OAuth manager
- Separation of spotcast functionalities is separate services
- Rebuild of the websocket API
- Creation of spotify connect device media_players
- Creation of Service Sensors
- Creating our own media library browser
- Creation of a dedicated podcast service
- Creation of a yaml config import
- Creation of a configuration flow to enable configuring Spotcast from the UI
- Creation of an option flow to permit modifying options without restarting Home Assistant
- Creation of a reauth process for when credentials expires
- Provide a comprehensive UI text definition
- Provide translations for the different Spotcast Interfaces
- Creation of a logo and icon for Spotcast
- Register the icons and logos in Home Assistant branding
Configuration
The configuration for Spotcast has changed drastically in this build. YAML configuration is no longer available and has been replaced with a UI configuration. Expect the following:
- As there is no YAML import at the moment, you will have to remove your entry for spotcast in the
configuration.yaml
- A Spotify Developper Application is now required to manage the OAuth token. If you have the official Spotify Integration, you can use the same.
- All documentation about the new version of spotcast can be found in the dev branch
- Expect frequent change in the coming weeks.
Thank you in advance for anyone wanting to test out this pre-release. I have been stress testing it for a bit now and have had very good result, especially in terms of performance for starting playback. I'll be waiting for bugs report, as I am sure there are a lot of edge cases that I did not anticipate