@Mykle1 If you’re on jessie (with pixel), keep reading this post. I think you mentioned you have blueman installed. You don’t need blueman anymore. I would recommend getting rid of it. Pixel comes with pi-bluetooth which is supposed to make things easier for audio. Notice how you have 2 bluetooth icons in your taskbar? They could be conflicting.
Please also see this link https://www.raspberrypi.org/blog/another-update-raspbian/ for how to connect the speaker. It should work.
Of course do back up your card in case something goes wrong.

Raspbian Stretch also changed some stuff about bluetooth, maybe take a look at that if you have a spare sd card lying around. I personally haven’t tried it yet.
https://www.raspberrypi.org/blog/raspbian-stretch/

This is how mine looks

I think there is a confusion about the time limit. Alexa pi comes with 2 wake word engines, Sensory and kitt.ai. Sensory will expire in at least 120 days and will need to be re setup but but the kitt.ai engine doesn’t seem to have a time limit. Kitt.ai is free for personal use but needs to be licensed when used commercial.

Had the same issue. added

address:"0.0.0.0",

to the config and it’s working again.
https://github.com/MichMich/MagicMirror/issues/1036

Congratulations. Well deserved.

@bhepler said in MMM-Globe:

Well, this sucks. I tried to enable the GL drivers on my Raspberry Pi 3 and it crashed the Pi. It installed the drivers, asked me to reboot and then the Pi won’t come back up. I’m going to have to reflash the card and start over.

It’s going to be a long night. If you’re going to try the GL drivers, back up your config.js at the very least. Better yet, image your SD card just in case.

I had the same black screen issue on my pi3. I reflashed my card twice before realizing I could have disabled opengl by editing the boot config.txt file. This might save someone else some time. So if you enable opengl and get the black screen issue remember to edit you config file to fix the issue.

dtoverlay=vc4-kms-v3ddtoverlay=vc4-fkms-v3d
gpu_mem=256
#dtoverlay=vc4-fkms-v3d

#Adding these two lines stopped the black screen issue.
hdmi_force_edid_3d=1
avoid_warnings=2

https://www.raspberrypi.org/forums/viewtopic.php?p=999920#p999920

It’s seems to be getting worse. I just signed in and I see about 20 of them in recent posts. Can something be done?
Maybe prevent posts with Chinese characters from being instantly posted since most of the spam are not in English.

@ronny3050 said in USB Microphone:

@Mitchfarino
This is what I use: https://www.amazon.com/gp/product/B00IR8R7WQ/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

It works absolutely fantastic.

This. Amazon used this mic in their guide to the alexa pi as well.
I ordered mine last week hasn’t arrived yet.

Something must have happened. I didn’t change the code. I’ll check it when I get home.

@Eunanibus

@bhepler said in MMM-Globe:

Now this is curious… It works great on my Windows 10 box (Chrome or Firefox). It works great on my Ubuntu 16.04 box at work (Chrome or Firefox). It works fantastic in Chrome or Firefox no matter the platform.

But when I run npm start it doesn’t render anything to the screen. This is on an Ubuntu 16.04 microPC. Fascinating.

You are describing the same issue I have. I run my mirror in server mode and use chrome on raspbian to access it. For some reason, the module won’t render on my raspbian chrome build but the mirror site works fine from my laptop and phone(any browser). I’ll post some screenshots over the weekend.

Or make new posters go through a 5 post vetting process where their posts would need to be reviewed before being made public.
Not sure how the logistics would work since the mods would still need to review a lot of posts.