Read the statement by Michael Teeuw here.
MMM-Hotword,MMM-AssistanMk2 Hotword no Funktion
-
@guongthongminh I dont think this is your problem
you have two models: [] sections above
one that says the hotword is smart_mirror
and one that says “tin_tuc”
I don’t know which became active…
just take the{ hotwords: "tin tuc", file: .., sensitivity: "0.5" },
and put it into the the models array above
-
@sdetweil The hot word is “hotword” for using mmm-asisstantMK2
hot word “tun tuc” to call mmm-pagereader
The result I want it like this https://www.youtube.com/watch?v=xdLz0bdxO58
Can you help me because I don’t know much about this! -
@guongthongminh sorry, I cannot help…
-
@Sean
I really need your support !!! Please -
@guongthongminh
You did definemodels
twice, so previous one (“smart_mirror”) is ignored.
do like this; (I wroteYou can add more models here
but you might not see.)models: [ { hotwords: "smart_mirror", ... }, { hotwords: "tin_tuc", ... }, ],
-
@Sean I fixed this but still could not get the MMM-PageReader module to appear on the screen. Could the cause be from the MMM-PageReader modules?
-
@guongthongminh
Don’t do what you can’t understand.I wrote in my earlier answer, payload was something like this;
payload: "URL TO OPEN",
But in your last post, you did like this;
payload: (detected, afterRecord) => { ... }
It doesn’t make sense.
-
@Sean Sorry, I tried this but the result is still the same
-
@guongthongminh
Let’s check. See the backend logs and the frontend logs.- Hotword
tin_tuc
was caught normally? (You can check the result on backend log)- If so, notification was emitted normally? (You can check it on frontend log)
- if so, well, that’s not my business. Maybe MMM-PageReader has some issue about using notification.
- If not, you probably have some error(s) on frontend to prevent working of module. Solve them first.
- If not, you should solve the hotword issue first. maybe your
tin_tuc.pmdl
was not catchable.
- If so, notification was emitted normally? (You can check it on frontend log)
- Hotword
-
@Sean The mirror receives and answers like this: “This feature is not yet supported on this device”. I cannot determine the cause.