For some reason, I’m getting calories displayed, but nothing else. @Vendittelli, does the module have any additional debugging or logging that I can turn on to look through? - I’m not getting any issues in dev mode or in the terminal - it seems that’s the only data I get. When I look in the dev console, I see:

writing steps (data/goal): 0/10000
Writing floors (data/goal): 0/10
writing calories out (data/goal): 1664/2930
writing distance (data/goal) 0/5
writing activeminutes (data/goal): 0/30
writing sleep (data/goal): 0/480

When I clear down my tokens.ini and re-run the setupaccess.py, I can see the scope information for the token results includes u’social’, u’settings’, u’profile’, u’sleep’, u’activity’, u’heartrate’, u’weight’, u’nutrition’, u’location’
if that’s helpful…
As a slight aside: @olliewarren411, would you mind sharing your ‘vertical-layout’ css? I’m still trying to get my head around cascading style sheets!

Glad to read you solved it! :)

Solved! I don’t think my code-hacking is going to win any awards for elegance but it works - I get a different message and journey time depending on whether it’s the week or the weekend! :)

I don’t think it can from what I’ve seen @MichMich - I could be wrong, but it isn’t obvious that it could.

Running the Alexa sample requires 3 terminal sessions -
one runs the companion service which stores the application token information and runs a listener on port 3000
one runs the java client under maven
One runs the wake word agent, running one of two engines - kitt_ai or sensory (I opted for kitt_ai)

I can’t tell at the moment, what information is returned by AVS, so it’s difficult to know if and how usable it is. It does support IFTTT however. Combining it with the MMM-IFTTT module, whilst not elegant, may be a workaround?

For what it’s worth, the install, whilst lengthy was fully automated and incredibly trouble free - it worked straight out of the box on a fresh Raspian install which already had a barebones MagicMirror2 install.

Also of note, every time I need to restart the java client, I am required to re-authenticate my device to get a new bearer/autentication token. These tokens do not seem to last that long and the authentication process involves logging into Amazon through a web page with an image security verification. No doubt that’s down to how this sample is implemented but might be worth knowing about

That’s what it was. Thanks @KirAsh4!

It’s awesome :)

I’ve had Alexa tell me the day, a joke and asked her a maths question.

A quick demo (YouTube)

The detection is spot on and the response time is pretty acceptable

The sooner this can get made into a module the better :)

@d3r not quite - I’m almost there but trying to login to my AWS mirror profile after authorising it and I’m failing their ridiculous ‘type the characters you see in this image’ challenge :)

Edit: At last! through…

Ah, thtat’s great. Thanks @d3r.
All good now

I’ve jsut set up an Amazon dev account and installing the Alexa pi code to have a play with.

During the install, I see
Configuration file ‘/etc/lightdm/lightdm.conf’
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer’s version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** lightdm.conf (Y/I/N/O/D/Z) [default=N] ?

I think I should answer ‘Y’ to keep the installer happy, but thought it worth checking - @d3r can I ask what you chose?

So having realised the simplest approach to a week/weekend commute display would simply be to code the date information into MM-Traffic’s MMM-Traffic.js file, I’ve added the following logic to the getParams function;

getParams: function() {
var params = '?';

-> var d = new Date();
-> var n = d.getDay();

    params += 'mode=' + this.config.mode;
    params += '&origin=' + this.config.origin;

-> if (n < 6) {params += ‘&destination=’ + “Cheltenham”;}
-> else {params += ‘&destination=’ + “Gloucester”;}

    params += '&key=' + this.config.api_key;
    params += '&traffic_model=' + this.config.traffic_model;
    params += '&language=' + this.config.language;
    return params;
},

Which works like a dream :) My first bit of javascript. I’m so excited!

I’d like to round it off by adjusting the
‘current commute is’
and
'origin to destination displays to be along the lines of ‘Work Commute’/‘Town Commute’ and ‘Home to Work’/‘Home to town’ but I’m struggling to find how to inject the logic.

I can see the current commute is in the defaults and symbols section. Ideally I want to change the defaults section.

The other is in the //routename section, but again I can’t work out how to make the alteration.