Hello-Lucy

TheGeekfather

 0 [ALSA           ]: bcm2835_alsa - bcm2835 ALSA
                      bcm2835 ALSA
 1 [Device         ]: USB-Audio - USB Audio Device
                      C-Media Electronics Inc. USB Audio Device at usb-0000:01:00.0-1.1, full speed

Mykle1

@TheGeekfather said in Hello-Lucy:

It seems all my modules are in
modules/default/

We went over this earlier, I think. Only the default MM modules go there. All other modules go on the root of the modules folder

TheGeekfather

@Mykle1

Other modules installed there are working but had to change paths for icons to work

Mykle1

@TheGeekfather said in Hello-Lucy:

Other modules installed there are working but had to change paths for icons to work

I don’t even know how to reply to that. Modules belong in the modules folder

cowboysdude

@TheGeekfather The problem is when you try to change things you also are changing the way the mirror works and this will lead to issues…the kind you are having LOL.

Default modules are wired to work out of that directory - /modules/default
3rd party modules are wired to work out of the modules directory. /modules

Seems like a lot of extra work and if you miss something then you will have issues. So my suggestion is that if you get a module from github you do this:

in the MagicMirror/modules directory
git clone https://github.com/mykle1/Hello-Lucy.git

Then go to the dir you just cloned the repository in ie MagicMirror/modules/Hello-Lucy
[typically from there if a module has dependencies you’d run ‘npm install’… for Lucy you have to be in the MagicMirror/modules/Hello-Lucy/installers directory and you would run a bash command]

Put the module in your config and you’re off an running…

This will put your modules in the correct place to run without having to change the module itself… Where you are going to run into issues is when a developer hard codes something you can’t find…
It’s already happened and that creates issues that are VERY difficult to solve…

But I am glad you are trying to learn something and seem very enthusiastic about it :)

TheGeekfather

@TheGeekfather

I guess the best thing is to re-install all my modules in the correct folder. Is that the only way to get Lucy to work.

Thank you again for all your help

TheGeekfather

@cowboysdude

OK, here is what I did

deleted Hello-Lucy folder from default directory
cloned hello-lucy in modules directory
cd installers and ran bash dependencies.sh
npm start

in modules/default directory In the defaultmodules.js file I added

var defaultModules = [
	"alert",
	"calendar",
	"clock",
	"compliments",
	"currentweather",
	"helloworld",
	"newsfeed",
	"weatherforecast",
	"updatenotification",
	"MMM-Swipe",
	"MMM-NHL",
	"MMM-BMW-DS",
	"modules/Hello-Lucy",
	"MMM-iFrame",
	"MMM-Astro",

lucy started and microphone icon no longer had “undefined” error but icon not flashing and commands like “show clock” or hide “clock” don’t seem to be working

cowboysdude

@TheGeekfather Well in all honesty what you’re doing is just making a huge mess. You need to delete ALL the modules that don’t belong in the default folder. ANY changes you made to any files undo…

Install modules as they are intended and we can help you, other then that I have no answers for you.

TheGeekfather

@cowboysdude

I understand - and yes I will re-install

One last question - should the mic icon flash when you speak?

Again, THANK YOU for all your help :)

cowboysdude

@TheGeekfather Yes, green :)

TheGeekfather

@Mykle1

Hi, you mentioned you were going to fix the install problem after noticing microphone not working with a fresh install.

Any progress?

Thank you for updates

cowboysdude

@TheGeekfather The mic is an easy fix if you’re using a pi…

Open terminal and type in ‘arecord -l’ it will give you all the info on your mic… more than likely if your using a USB mic it will be most likely 1,0.
In your config in Hello-Lucy in the ‘config’ section of Hello-Lucy you would put:
"microphone: “1,0”,

That’s it…pretty simple. Yes I realize simple if you know it LOL.

TheGeekfather

@cowboysdude

:) Knowledge is Power - That is what I always told my students

This is the mic I have

**** List of CAPTURE Hardware Devices ****
card 1: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

cowboysdude

@TheGeekfather I went to school to be a teacher but never taught… I’m not real good with touchy feeling kinda things I tend to be more direct and that’s not a good thing in Schools LOL

Yes you could add:

 {
  disabled: false,
  module: "Hello-Lucy",
 position: "top_right",
 config: {
   keyword: 'HELLO LUCY',             
   microphone: "1,0",                   
   timeout: 15,                        // timeout listening for a command/sentence
   defaultOnStartup: 'Hello-Lucy',
   standByMethod: 'DPMS',              // 'DPMS' = anything else than RPi or 'PI'
   sounds: [ ],         
   confirmationSound: "ding.mp3", 
    startHideAll: true,                 // if true, all modules start as hidden
  pageOneModules: ["Hello-Lucy", "MMM-Insults"],    / 
  pageTwoModules: ["MMM-BMW-DS", "MMM-Events"],     // modules to show on page two
  pageThreeModules: ["MMM-Lunartic"],               // modules to show on page three
  pageFourModules: ["MMM-PC-Stats"],                // modules to show on page four
  pageFiveModules: [],                              // modules to show on page five
  pageSixModules: [],                               // modules to show on page six
  pageSevenModules: [],                             // modules to show on page seven
  pageEightModules: [],                             // modules to show on page eight
  pageNineModules: [],                              // modules to show on page nine
  pageTenModules: []                                // modules to show on page ten
  }
 },

That is an example config… the ONLY thing you need to change is the modules listed on the ‘pages’… it should work on a pi with a usb mic… Please note there will be about a 4 to 5 second delay… the pi is small and this is heavy weight it’s lifting.

As soon as @Mykle1 tests this on a pi4 we’ll let everyone know :)

Mykle1

@cowboysdude

As you know, the installer was not at fault. The automatic identification of the microphone was not happening, at least on the Pi. Thanks for stepping in while I was busy troubleshooting and thanks for testing

cowboysdude

@Mykle1 Who are you and what are you doing here? LOL

Mykle1

@cowboysdude

Uhh, I was hoping you’d tell me. :-)

cowboysdude

@TheGeekfather If you have any other questions I’m sure @Mykle1 will be happy to help you :) I’m not on that often… the last couple days I’ve been on more then I have been in 3 months LOL

TheGeekfather

@Mykle1

Thank you for all your help. Started fresh install - put modules in correct folder

added "microphone: “1,0”,

AND

Hello-Lucy works GREAT :)

Mykle1

@TheGeekfather

Well ok then! You’re happy? I’m happy! Lucy’s happy! :-)

Seriously, I’m glad you’re up and running and I’m glad you’re pleased. :thumbsup:

Now, can you do something simple for me? Can you please tell me:

Your hardware ( Pi3? 4? whatever)
Your microphone (including if it’s USB or analog)
Your OS (if not using a Pi?)
Your response time from the time you issue a command until Lucy responds or you hear the confirmation sound. Instantly? 1 second? 3? 5?