@zydecat74 great job! Im just wondering what type of mirror you used?

Los Angeles

@d3r Yes you are correct.

I have tried out both wake word engines with the Alexa pi sample app and for me the sensory engine performed much better in picking up the wake word. For some reason with snowboy (kitt.ai) I always seem to have to be very close to the mic for it to be picked up.

@darrene hey no worries at all on the typo. I can’t thank you enough for helping out and providing the comprehensive step-by-step guide in plain english to noobs like me. I don’t know how I would have got the voice module working without your help so thanks again!

@SexyTrogg damn…ok i assume you double checked your access token and client ID in the config match up perfectly with what you received from Wunderlist? Other than that I can’t think of any other reason why it wouldn’t show the lists.

@SexyTrogg you have a typo on “accessToken:” in the config file.

@Pieps perfect that fixed the issue. Now the notifications come in with the right name. Thanks again for the quick solution!

@alexyak great work on creating this module! This is the only voice module that works for me on MM2.

I was wondering if its possible to customize the sensitivity settings? On the snowboy website when training voice models it gives you this option when testing so wasn’t sure if that feature could also be added into the module itself. Right now with the default settings I need to speak very close to the mic for it to trigger the wake word.

@strawberry-3.141 Thank you for the tip! Now it makes perfect sense.

It does still work with the multiple else if statements but for the sake of cleaner code I like the idea of using the or condition.

@carteblanche said in Peek-a-boo...:

@darrene thank you for sharing your calendar.js file because that is where I found where the issue was…it was the name for the function notificationReceived: – needed to have a lower case “n”.

Now it works perfectly!! And as you predicted I experienced a massive grin.

update:
I’ve been testing this out with other modules and it works like a charm. I also discovered (after trial and error) that its possible to combine the hide/show with the hide all/show all command simply by revising the if statement on the notificationReceived function with an “or” condition specifying both commands . See below is an example of the revised code:

notificationReceived: function(notification, payload, sender) {
if (notification === “HIDE_CALENDAR” || “HIDE_ALL”) {
this.hide();
} else if (notification === “SHOW_CALENDAR” || “SHOW_ALL”) {
this.show();
}
},

update: while this worked for a short period, upon further testing this code seems to cause some issues with HIDE_ALL auto suspending all modules on launch. So the or condition if statement doesn’t appear to be a viable solution, the only way to include hide/show all is the way you have the code now @darrene with the multiple else if statements.

@Pieps Thanks for making a quick fix! Once github is back online I will definitely do the pull and let you know the result.

@darrene I saw the module from whyjustin but didn’t want to try it because it required downgrading electron.

@d3r Yes you are correct.

I have tried out both wake word engines with the Alexa pi sample app and for me the sensory engine performed much better in picking up the wake word. For some reason with snowboy (kitt.ai) I always seem to have to be very close to the mic for it to be picked up.