v1.0.38

[ 1.0.38 ] - 2024/06/27

• Corrected various services that use float values that were incorrectly defined as strings by the service schema.
• Updated underlying spotifywebapiPython package requirement to version 1.0.71.

v1.0.37

[ 1.0.37 ] - 2024/06/27

• Updated underlying spotifywebapiPython package requirement to version 1.0.70.

v1.0.36

[ 1.0.36 ] - 2024/06/26

• Added support for Spotify Connect LoginID specification in configuration options.
• Updated underlying spotifywebapiPython package requirement to version 1.0.69.

v1.0.35

[ 1.0.35 ] - 2024/06/26

• Updated underlying spotifywebapiPython package requirement to version 1.0.68.

v1.0.34

[ 1.0.34 ] - 2024/06/25

• Updated underlying spotifywebapiPython package requirement to version 1.0.67.

v1.0.33

[ 1.0.33 ] - 2024/06/25

• Updated underlying spotifywebapiPython package requirement to version 1.0.66.
• The underlying spotifywebapiPython update changes the way the Spotify Connect Zeroconf API processes the status and spotifyError response values. Some Spotify Connect devices return them as strings, while other return them as numerics. Spotify Zeroconf API specifically says they should be returned as integer values.

v1.0.32

[ 1.0.32 ] - 2024/06/25

• Updated underlying spotifywebapiPython package requirement to version 1.0.65.
• The underlying spotifywebapiPython update changes the way the Spotify Connect Zeroconf API addUser call is processed to account for "ERROR-INVALID-PUBLICKEY" statuses returned for some devices. This will retry the connection request with the PublicKey value returned from the initial request.

v1.0.31

[ 1.0.31 ] - 2024/06/24

• Updated underlying spotifywebapiPython package requirement to version 1.0.64.
• The underlying spotifywebapiPython update changes the way Spotify Connect Zeroconf API return codes are processed. It now processes the Spotify Zeroconf API status code from the JSON response instead of processing the HTTP request status code. It has been found that some Spotify Connect manufacturers return different HTTP status codes than other manufacturers; but the Spotify Connect status, statusString and spotifyError JSON properties seem to be consistent across the board.
• The underlying spotifywebapiPython update also filters out duplicate Spotify Connect Device entries for devices that have been grouped together. For example, the "Bose-ST10-1" and "Bose-ST10-2" are grouped as a stereo pair; there will be two Zeroconf discovery result entries with different instance names, but their Zeroconf getInfo endpoint url will be the same. This was causing two entries to appear in the device list, when there should have been only one.

v1.0.30

[ 1.0.30 ] - 2024/06/22

• Updated config_flow to utilize the HA shared Zeroconf instance.
• Updated underlying spotifywebapiPython package requirement to version 1.0.62.
• The underlying spotifywebapiPython update fixes a potential memory leak with the Zeroconf discovery process.

v1.0.29

[ 1.0.29 ] - 2024/06/21

• Fixed a bug due to SpotifyConnect addon not properly returning a "Content-Type: application/json" header in it's Spotify Zeroconf API responses. This was causing an error when trying to retrieve the Spotify Connect device list, and returning errors in the configuration options form.
• Updated underlying spotifywebapiPython package requirement to version 1.0.61.