You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
system has been running since "2021-05-06 01:15:03.787" per the 'bus.log' [a long time for me]
system was basically useable ['news' & wakeword - excepted]
put unit to 'sleep' Fri night :: but 'woke' it Saturday and had issues with LED ring indications
troubleshooting the LEDs - ran into an issue with the 'Volume' skill
To Reproduce
Steps to reproduce the behavior:
long running on latest(s) ???
* @11:19 ish UTC - played with volume switch [to see the LEDs] but no led-indication - volume did change !!
while it was timing out on a "what time is it" told it to "set volume to 50%" - RESponded with 'setting BRIGHTness to 50%"
Environment (please complete the following information):
Device type: Mark2-Dev_kit , on network cable, uSDC
OS: default Ubuntu
Mycroft-core version: 20.08.1 -per Device setting @ home.mycroft account
Other versions: latest 05-13 02:22:00 on top of MarkII_arm-rpi64_Prod_005-stable_2021-04-08.img.gz
Additional context
have not changed any git-hub settings or manual configs (except web settings),
not on 'dev' afaik - unless it is part of a 'latest'
Chat channel response: [might provide a clue]
sgee_ 9:02 AM
the brightness/volume problem is likely to be found in the intent construction (here/here(Adapt->scattered))
a too loose intent tend to mix up things
The text was updated successfully, but these errors were encountered:
based on input for gez-mycroft - files were missing from the skill folder, reinstalled and volume now responds properly
His question (and mine) is how did those files come up missing - my suggestion was that part of the 'fix' for the missing '8' led/volume bug issue may have done an incomplete replacement.
'
i consider this issue closed - but the 'skill-volume#74 did catch an other issue with the STT engines
it would be hard to diagnose why my files were missing..........Gary
Describe the bug
system has been running since "2021-05-06 01:15:03.787" per the 'bus.log' [a long time for me]
system was basically useable ['news' & wakeword - excepted]
put unit to 'sleep' Fri night :: but 'woke' it Saturday and had issues with LED ring indications
troubleshooting the LEDs - ran into an issue with the 'Volume' skill
To Reproduce
Steps to reproduce the behavior:
long running on latest(s) ???
*
@11:19 ish UTC - played with volume switch [to see the LEDs] but no led-indication - volume did change !!
while it was timing out on a "what time is it" told it to "set volume to 50%" - RESponded with 'setting BRIGHTness to 50%"
checked the "https://github.com/mycroftai/skill-volume/tree/d6527214faf8797b06c8db7ca271f9884c4fa01f' and used it's example to set it to 7 --STILL got a 'brightness' response
Expected behavior
Volume skill to respond with the new setting it was commanded
Log files
mycroft-05-15_am_multiple.tar.gz
Environment (please complete the following information):
Device type: Mark2-Dev_kit , on network cable, uSDC
OS: default Ubuntu
Mycroft-core version: 20.08.1 -per Device setting @ home.mycroft account
Other versions: latest 05-13 02:22:00 on top of MarkII_arm-rpi64_Prod_005-stable_2021-04-08.img.gz
Additional context
have not changed any git-hub settings or manual configs (except web settings),
not on 'dev' afaik - unless it is part of a 'latest'
Chat channel response: [might provide a clue]
sgee_ 9:02 AM
the brightness/volume problem is likely to be found in the intent construction (here/here(Adapt->scattered))
a too loose intent tend to mix up things
The text was updated successfully, but these errors were encountered: