-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Spotcast can't find Spotify integration even if it's installed #258
Comments
Have the same issue Workaround is to completely restart your virtual or real machine because you can't do soft reboot configuration check show issue in the config pull the plug ;) @mfabiani53 |
@snp88 you mean i must turn off completely my raspberry and then turn on again? |
Possible regression of #255 @Darkfull-Dante |
@mfabiani53 i have my HA in virtual machine but in short word yes if you unplug your raspberry and turn on again it should be ok this is what i do with my HA but my instance is on Virtual machine @hmmbob @Darkfull-Dante its look like some condition race ;) and sometimes Spotify integration fail this race |
thank you for the report @snp88 && @hmmbob, during testing I never add that race condition come up. We are releasing a new feature today from a PR we receive, we will simply keep the error message for the time being to be able to troubleshoot. I'll look into a more elegant way to test the presence of the Spotify integration |
I did a quick check of the manifest file and dev documentation and we could try and add spotify in the after_dependencies section of the manifest. For the current release I will go with simply the quick fix (not aborting the setup). This potential solution still need testing before implementing |
#259 was merged with v3.6.19. @hmmbob @snp88, I will keep this issue open for the moment, please report if the problem persists. I will work and test the after_dependencies solution. If I release a beta with the fix is any of you able to test under your setup? My current dev env only permits me to test the Docker install |
@snp88 it is normal, v3.6.19 only reverts the aborting of the setup for the moment, I still maintain the error log as a check, I'll be working on a beta release that contains the potential fix. I'm currently running that fix in my dev env without problem, sadly it doesn't mean much because I never had the race condition you had. Only the first 2 logs (timewize) are related to the regression in #255. The 2 after that indicate the spotify integration wasn't able to get the playlists, because of taht spotcat playlist sensor fails. That could potentialy be another bug different than the one. Possibly a change in the spotify api on how to get playlist. |
@snp88 can you confirm the issue with loading Spotcast integration is gone following v3.6.20? You should now have no error logs regarding finding the Spotify integration |
On my system I still get errors in loading spotcast integration also with 3.1.20 custom_components.spotcast.helpers] spotify integration not found And the spotcast service is not working... |
@snp88 ok, thank you for the information, so even with forcing spotcast to load after spotify there is still a possible race condition for certain user. I'll remove the abort setup for following releases. Will simply keep it a debug log for the moment. |
#258 still a problem, will keep error message as debug for future release
@Darkfull-Dante are you referring to my latest message? |
@mfabiani53 and @snp88: I wonder what will happen if you:
As we only see 2 reports now (from you both), and Spotcast is used quite a bit, I am thinking it might be something locally. It's worth trying to see if it fixes the issue. |
oh sorry @mfabiani53, I referred to the wrong user, yes I was talking about your last message. Can you verify if the problem still persist in 3.6.21? |
Yes asap I'll let you know... |
Hi All sorry for late response |
No problem, thank you for the testing. I'll keep this ticket around so we can eventually have an elegant way to test for the presence of the spotify integration |
Describe the bug
After installing the latest release (v. 3.1.18) the integration is not loaded with the following errors:
It seems spotcast is not recognizing the spotify integration regularly installed as you can see:
and also from /.storage/core_entity_registry it is completely loaded:
When reverting back to the 3.1.17 release all is working ok !
I am trying to use the using latest version of spotcast v. 3.1.8
I am using latest stable version of Home Assistant
The text was updated successfully, but these errors were encountered: