Open fermulator opened 4 years ago
It shouldn't (TM) require on spotify but it will increase the score of the match if "on spotify" is used.
It is not normal to have to specify "on spotify", it should be able to match even without it (and does on my reference devices).
where is the "music service skill" output coming from? Could you have another Common playback skill that is returning a higher score than Spotify and using "on spotify".
There could also be a playback control skill issue at play here, I've seen it once or twice that it gives up waiting for the CPS skills to reply too soon in some cases (the "I've not been configured..." could indicate some such issue)
This is a default install mostly, I've not added any other "music" or "playback" skills other than this spotify skill itself.
Here's my best attempt at proof:
mycroftai@mycroftai ~/mycroft-core/bin $ ./mycroft-msm list -i
INFO - building SkillEntry objects for all skills
INFO - building SkillEntry objects for all skills
INFO - invalidating skills cache
fallback-wolfram-alpha [installed]
mycroft-pairing [installed]
mycroft-support-helper [installed]
mycroft-spelling [installed]
mycroft-stop [installed]
mycroft-configuration [installed]
mycroft-playback-control [installed]
mycroft-wiki [installed]
mycroft-stock [installed]
fallback-unknown [installed]
mycroft-version-checker [installed]
mycroft-timer [installed]
mycroft-hello-world [installed]
mycroft-personal [installed]
homeassistant [installed]
mycroft-audio-record [installed]
mycroft-singing [installed]
mycroft-reminder [installed]
mycroft-joke [installed]
mycroft-spotify [installed]
mycroft-speak [installed]
mycroft-alarm [installed]
mycroft-ip [installed]
mycroft-npr-news [installed]
mycroft-date-time [installed]
mycroft-volume [installed]
mycroft-naptime [installed]
mycroft-installer [installed]
mycroft-weather [installed]
fallback-query [installed]
mycroft-fallback-duck-duck-go [installed]
dismissal-skill [installed]
There is no such "music service skill". hm.
mycroftai@mycroftai ~/mycroft-core/bin $ ./mycroft-msm list -i | egrep "music|play|spotify"
INFO - building SkillEntry objects for all skills
INFO - building SkillEntry objects for all skills
INFO - invalidating skills cache
mycroft-playback-control [installed]
mycroft-spotify [installed]
I am using old Dell hardware (this is a PoC/playground for me before moving to a Pi). The CPU is fairly pegged all the time. It's ~25% idle (1.4-1.5x BUSY on a dual core system).
Thanks for verifying, I'll do some more experiments and see if I can trigger the behaviour.
A few comments and general ponderings over the report and my code:
The skills.log looks a bit weird for the second attempt... like it got the first request and played that:
2020-04-26 11:16:01.673 | INFO | 543 | SpotifySkill | Handling "some classical music" as a genric query...
Since it's a generic query quite far down on the check list it could be a timeout thing the first time around... Going to see if I can handle that in a more async way.
Since switching over to picroft, I'd say this has improved; but on occasion I noticed a few instances where it didn't automatically attempt to use Spotify (same skill/installation as last time, there are no other playback skills installed) - I'll continue to use and monitor - next time it happens will try to snap some more logs.
To note is that the issue in the news skill overmatching was resolved by @krisgesling so that can be part of the improvement.
Hi @forslund , wanted to report this issue "as is" in the current state (looking for guidance on debug/isolation - can provide quick turnaround)
So my last "working state" was roughly the situation described in https://github.com/forslund/spotify-skill/issues/135#issuecomment-615878220.
For about a week now, starting early last week, suddenly when I asked mycroft to play some music using spotify, it says it is not configured to do so. A contradiction is that if I ask it to list the available devices, it still knows about the "some_other_device" in my spotify network.
Here is some clarity I've found. (summarizing)
(1)
, logs:
OK darn, that didn't work? Confusing. If we are more specific to use "spotify", then it does key off it properly
(2)
Is it normal to have to specify "spotify" as the playback service/skill? I cannot remember if I've always (previously) specified "on spotify" or if this behaviour changed on me ...