MMM-awesome-alexa

bumrocks

@vlatko_jordanov I am trying to set this up but my brain cannot figure out what I am supposed to put in as the return url in the AVS setup…
…
edit: DOAH… read the instructions!!! lol… it is EPEXCTED to FAIL to connect… read the text from the failing url

got that… BUT then next step fails for me…
 Enter your Authorization code (from previous step): ANMJShcLPpSKjJkKLbzj
  ◡ Getting response from Amazon...(node:2772) UnhandledPromiseRejectionWarning: StatusCodeError: 400 - {"error_description":"The request has an invalid grant parameter : code","error":"invalid_grant"}

@sdetweil , man am I happy to see you in here…First things first, I searched within your github page for a way to make a donation to you fir your help and efforts but found nothing…Point me in the right direction to do so please! Once you do, I will gladly show some appreciation to you ;)

Once that is done I hope you might help in the above situation. I get to this point in the Configuration Helper Tool and have no clue as to what I should enter for a Redirect uri and I never read anywhere about it supposed to fail. And then in advance I’ll ask about the next part you mention where you say the next step fails for you. Did you figure that out?

Thank you!

Note: I do have an echo dot device in my home and from reading numerous comments, this seems to help in some way…

Also, when adding the recommended line to the elctron.js file is it supposed to simply look like this?

});

// Start the core application if server is run on localhost
// This starts all node helpers and starts the webserver.
if (["localhost", "127.0.0.1", "::1", "::ffff:127.0.0.1", undefined].indexOf(config.address) > -1) {
	core.start(function(c) {
		config = c;
	});
app.commandLine.appendSwitch("autoplay-policy", "no-user-gesture-required");
}

It does not appear so…As if it is too simple…

sdetweil

@bumrocks you don’t need that line anywhere, we added it back in 2.9 as part of the base.

as for the alexa thing, the way the process works, you use the client id/and secret, and some uri to call back to when the authorization is comnplete…

but there is nothing running on your pi to call, so it errors out,

BUT the url it is trying to call is right there with the code you need to copy

SO, knowing there is nothing to call back to, just use http://localhost:1234

then the web page will come up, you give permission, and then it tries to call http://localhost:1234 with the access code, and fails, but the code is show on the address bar line

ps… I don’t take contributions… I do this cause I like it.

bumrocks

@sdetweil , you are a good guy. Much appreciated all that you obviously do and in areas that you don’t necessarily have to. Thank you very much 😁

uok825

Can anyone fix this pm2 issue?

sdetweil

@uok825 i don’t see any info on a pm2 issue

uok825

@sdetweil
First Page

PM2 problems
For some reason, running MagicMirror on PM2 with this module doesn’t seem to work on Raspberry Pi. The mic does not pick up. If anyone has a solution or cause for this, it would be greatly appreciated. I would recommend to start the MagicMirror the traditional way of npm start.

I have that issue.

sdetweil

@uok825 can u show the pm2 logs during this kind of launch

pm2 stop  0
pm2 flush
pm2 start 0

do your tests

pm2 logs --lines=100
pm2 info 0

uok825

pm20|mmstart | X.Org X Server 1.19.2
0|mmstart | Release Date: 2017-03-02
0|mmstart | X Protocol Version 11, Revision 0
0|mmstart | Build Operating System: Linux 4.9.41-v7+ armv7l Raspbian
0|mmstart | Current Operating System: Linux raspberrypi 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l
0|mmstart | Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=1440 bcm2708_fb.fbheight=900 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:C2:8B:EA vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=00dad306-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
0|mmstart | Build Date: 18 October 2017 04:55:30PM
0|mmstart | xorg-server 2:1.19.2-1+rpt1+deb9u2 (https://www.debian.org/support)
0|mmstart | Current version of pixman: 0.34.0
0|mmstart | Before reporting problems, check http://wiki.x.org
0|mmstart | to make sure that you have the latest version.
0|mmstart | Markers: (–) probed, (**) from config file, (==) default setting,
0|mmstart | (++) from command line, (!!) notice, (II) informational,
0|mmstart | (WW) warning,
0|mmstart | (EE) error, (NI) not implemented, (??) unknown.
0|mmstart | (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Jun 26 14:34:56 2020
0|mmstart | (==) Using system config directory “/usr/share/X11/xorg.conf.d” 0|mmstart | Fontconfig warning: “/etc/fonts/fonts.conf”, line 100:
0|mmstart | unknown element “blank”
0|mmstart | [5863:6076:0626/143511.431135:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are “tcp” and on UNIX “unix”)
0|mmstart | [5863:5890:0626/143514.718350:ERROR:simple_backend_impl.cc(118)] Failed to create directory: /dev/null/Default/Cache
0|mmstart | [5863:5890:0626/143514.729068:ERROR:simple_backend_impl.cc(728)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Default/Cache
0|mmstart | [5863:5882:0626/143514.730785:ERROR:cache_util.cc(140)] Unable to move cache folder /dev/null/Default/Cache to /dev/null/Default/old_Cache_000
0|mmstart | [5863:5882:0626/143514.731049:ERROR:disk_cache.cc(184)] Unable to create cache
x0|mmstart | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mmstart | [1:8:0626/143529.824588:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.

sdetweil

@uok825 said in MMM-awesome-alexa:

pm20|mmstart | X.Org X Server 1.19.2
0|mmstart | Release Date: 2017-03-02

what is all that?

what device is this on? pi 0?

I don’t see the alexa module being loaded

uok825

@sdetweil Yes pi0 and not desktop system.