spotcast: Not able to install spotcast after update of HA to 2024.11.0 error: no module named 'spotipy'

Bug Ticket

Describe the bug

After updat HA to 2024.11.0 I do get spotcast not setup anymore. giving error: image and in the log: image

Troubleshooting

Make sure to validate all the elements before submitting the ticket (Exception to the steps marked as optional)

Environment

  • Installation type: [HA_OS|Container]
  • HA version: [ 2024.11.0]
  • spotcast version: [v3.9.0 ]

Configuration

# please remove any sensitive information like cookies and token keys
<insert configuration here>
spotcast:
  sp_dc: key
  sp_key: key

Service Call

If relevant, provide a yaml of the service call or explain the action taken to replicate the issue.

<insert the yaml of the service call here>

Logs

  • normal|debug
<please insert any relevent logs here>

Additional context

<Add any other context about the problem here.>

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 10
  • Comments: 28

Most upvoted comments

For anyone wanting the fix now, you can do the manual install. The official release will be available tomorrow

Message not only shows up upon installation, but also upon a reboot of HA. So likely impacting all spotcast users.

Hi @canedje, it was requested that I remove the fix for 2024.11 because it was annoying to have an update you couldn’t install. The update will come later. You can look at comments from #470 and #469.

The fix will be release once I have the time, which saddly won’t be today

v4.0.0 released

I was actually really impressed that you had a bug fix released before 2024.11 dropped. Can’t say I’m surprised that people complained about it - there’s always moaners. I doubt they like having it broken more. 😃

Still, I think this is a valid use case - it should be possible to publish version-dependent releases that HA “hides” until the target core version is installed. So I’m going to suggest that. 😃

For anyone running in a container there is a known issue since 2024.10. You need to add an environement variable to your container to set the PYTHONPATH to the deps folder. You can find examples of docker-compose files here

Hi @canedje, it was requested that I remove the fix for 2024.11 because it was annoying to have an update you couldn’t install. The update will come later. You can look at comments from #470 and #469.

The fix will be release once I have the time, which saddly won’t be today

People are the worst sometimes. It was very clear in the notes that it was in preparation for the core update. I thought it was very impressive. Thanks for your hard work.

I was wondering where that update had gone. Sure a little bothersome to have a red dot but surely more bothersome to have a non-working music system following an update. Nice work on getting it ready ahead of time.

FYI For anyone got the same issue ATM, if you’re using HACS, you may try rollback to v3.8.2: image image image

I remove the fix for 2024.11 because it was annoying to have an update you couldn’t install.

can’t you just change the entry in the hacs.json "homeassistant": "2022.3.0", to "homeassistant": "2024.11.0", ?

Edit: That is the minimum version needed. https://hacs.xyz/docs/publish/start/#hacsjson