OpenVoiceOS / skill-ovos-common-play

Mycroft AI official Playback Control Skill - providing Intents for other Skills to use common playback functionality (via Common Play)
https://mycroft.ai/skills
Apache License 2.0
1 stars 3 forks source link

FWIW - Mark 2-devkit loses several functions #2

Open Olzeke51 opened 3 years ago

Olzeke51 commented 3 years ago

installing this skill on a stock Mycroft 20.2 / latest version08-03 [Dev-Kit] causes the loss of all the LEDs on top - yes the 'temp' & 'mic' also the standby Face looses the timestamp of the latest the time is displayed temporarily (on the black screen) every minute any speaker output is terribly LOUD get mixed messages at boot up about network connection status [cuts off in mid sentence & both mimics] I may have contributed to some of this failure! a) attempted to 'blacklist' mycroft's playback control - - in the ~/.mycroft/mycroft.conf file b) rebooted and then loaded this skill via the (.venv) msm install github_url noted that : prolly had some typo, BUT after the recommended reboot - the changes were removed c) found a better example of 'blacklisting' and found the right place to put it - - /etc/mycroft/ folder !! I also blacklisted the 'volume' skill - no change - still LOUD and other symptoms (never uninstalled this skill - btw) d) upon reboot -- GOT the above failure indications removed the blacklisted portion in the mycroft.conf file - but both playbacks are still installed rebooted and all is back to normal


not really looking for a fix - just kind of an update - wanted to play with some of the OVOS stuff * skills_short.txt - log portion of this skill installation and subsequent issues also all full logs skills_log_ovos-playback.txt mycroft-ovos-better-playback.tar.gz

JarbasAl commented 3 years ago

thanks for the report, i will look optimizing this for the mark2, i have only been testing on the mycroft-core dev branch, but the mark2 uses a different branch and i am not sure what is different

Maybe the mk2 playback skill that is blacklisted includes more functionality than previously, this is a larger symptom of compatibility issues, in the future a best approach would be to emit the appropriate bus messages to disable the intents from the regular common play, this way the skill is not blacklisted and only the conflicting intents are disabled