Yeah, although I love the RPi support community, for example the ASUS Tinker Board S look very similar in both formfactor, price and spec’s but cheaper.

The Asus TB S has:

• 2 GB RAM
• 16 GB on-board SD
• GB Ethernet
• 1.8 GHz CPU
• 4K HD (AFAICR)

My guess is that the remote query must be an asynchronous task and thus the values you get are just the object placeholders for the promise. Somehow, I suspect you need to wait to make sure there actually is any data in your results. (Unless this is already handles automagically in the mysql node package.)

Alternatively, you could just put your sql query in a command line script (Bash or python) and execute that with your node_helper. In that way you could also “pre-format” your output data into CSV or JSON or what have you, and then present it using Tabulator (which doesn’t require any DOM coding, or at least extremely little, since it only need one HTML tag and some css.)

Wow look very cool.

Also you don’t need any third party app to connect to Spotify.

How does it work? Shazam kind of magic?

I’m very frustrated by all the different and poorly maintained/documented MM voice modules “out there”. So to make matter even worse, I’m proposing to create yet another one!

However, this will be “The One” that does all of the above below! Meaning it will work, and be easy to install and well maintained.

What would the features of this MMM be?

• It would concurrently accept wake words for: Google Assistant, Alexa and Snowboy (for MM control).
• It would be more modular so that other new speech technologies can be implemented later, (such as Bixby, Siri and others.)
• It would focus on low CPU usage and memory foot print to be ideal for embedded RPi3 (and above) devices.
• It would be properly integrated so that it is also able to respond to future requests, like:
  • Wake me up tomorrow at 8 am.
  • Set the timer for 20 minutes.
  • …and various follow-up questions, to previous responses.

The project would probably not need to be built from scratch since there are a very few modules that more or less work (such as MMM-Assistant) but they need a lot more TLC, so we might need to fork it up to a higher level of maintenance and perhaps try to repackage it into something more fresh.

What do you guys and girls think?
Who’s interested?

@Goldjunge_Chriz said in New two way community order for all european countries - Open until 03 June 2018:

please read through the old threads, there you will be answered all questions ;)

Well, I’m too lazy to do that…too. ;)

Just want to tell everyone that this module works very well.
I had some initial compile issues and trying to get the correct GA authentication, but after that it worked.

Now, I’m looking at Alexa, since I’d like both Alexa and GA + MM working.
Please see the github issue for solution in case you missed it.

Hi Chriz,

This sound great, but just a few questions:

• What is the material you use?
• What is the thickness?
• What is the benefit of using you as a middleman, instead of ordering directly from the manufacturer? (Seem that ording like this would take much longer. First waiting to fill your deadline, then wait for the order from them to you, then from you to us.)

ALL OK! Seem to have been some kind of glitch in the Matrix. Everyone can go back to their lives programs.

@Mykle1 said in The chat functionality in THIS forum is broken:

@E3V3A

I’m not seeing that. :-/

Hmm, that’s a problem…with my browser adblocker then. What 3rd party sites does this forum rely on?

@sispheor Cool! Thanks a lot for clarifying.

It seem that chat is not working properly. I can’t see any more messages than what fits on the screen. Scrolling up, just repeats all the messages already shown, keep doing this, you’ll get hundreds of the same last 10-40 messages just repeating.

Who’s in charge of fixing this?

Does MMM-kalliope allow or have any Google Assistant or Alexa functionality?
If, yes, how to install it. I didn’t see anything in the neuron list…

Although Kalliope look very nice and surely better documented now, it will be hard to sell without these features. People wanna talk to AI, not only ask to turn your lights on or off, which you can do by your self. Perhaps a phone plugin so you can call it up and talk?

In addition it is a huge obstacle that you have to make plugins (or neurons or synapses or whatever you call it) for just about everything you want to talk to Kalliope about. This learning should be automated by ML, and integrated to the productivity tools you already have, including future Alexa and GA compatibility.

You should not have the pip installation in that script without:

1. checking if it is already installed
2. make sure what python version your using. pip2 or pip3?
3. allow user to cancel that installation, if they know they already have it

Most of the time, if you have both Py2 and Py3 installed, pip would apply to Py2 and pip3 to Py3.

@sispheor said in Kalliope assistant + MM:

We have added a single line command install for Kalliope.

Is it for the MMM-kalliope?

Fantastic! Sound like music to our ears!

@Mykle1 ha ha ha! But you have so many modules, you’d get a “D” for effort.

@werdnllac I just managed to get this running!
Please see: https://github.com/eouia/MMM-Assistant/issues/24

@shep99 Can you please post your ALSA config?

cat ~/.asoundrc
cat /proc/asound/modules
cat /proc/asound/devices

Thanks.

At the end of the day year, the biggest hurdle of any of the currently available voice products I have looked at, are:

The useless (at best) or complete lack of installation instructions!

I have no idea what is going through the heads of all these developers who spend weeks and months of hard effort to produce software, that nobody will use, just because, anyone else who are not exact Matrix clones of them, will not be able to install, nor use it. Please understand that these are all wasted efforts if you’re not interested in having other people being able to use it.

I’ve been around long enough to confidently say that the vast majority (~98%?) of failed projects on github are only because of lacking usage instructions and lacking participation of the original developer or repo owner. I’ve seen and follow many great projects and ideas out there, but most will die a slow death of ignorance in the invisible shadows of murky README documentations. People come, look, move-on and forget.

In the current context of voice interaction to your MM, this is particularly disturbing. Although, many MMM’s here are fairly well presented in this forum or in their READMEs, the voice related ones are extremely lacking. This was a bit surprising to me, since people were able to voice interact with their C64’s already in 1985. While 99% of you probably have no idea what a C64 is, its not important. What is important, is that one of the main differences was that SW in the old era was usually extremely well documented. It was a sales advantage. Even yo’ mama could understand it!

So if you have spent countless hours thinking about and developing this great module that could improve the life of all MM owners, and you have a this l33t group of really super awesome developers and hackers, that project will never really make any significant difference, unless you can make it accessible also to the novice, whether or not this person is technically interested or just a plug-and-play grandma.

---

Here are the most important points in writing documentation:

• Don’t assume any previous knowledge!
  This is by far, the number one doc issue and failure!
• Does the software depend on any other, previously installed software?
  • If so make sure to either re-iterate the steps or link to equivalently good installation instructions.
  • Specify exactly what it depend on, and where to find it.
• Are the steps following a logical order of operations?
  You’ll be surprised!
• Is the information you give, correct?
  Don’t guess how things work!
• Are all the steps up-to-date with current master repository code and functionality?
  This is the hardest to keep up, since most SW in github are under some development.
• Are your screenshots up-to-date with how the UI actually look?
  You have screenshots, right!? A million of your words, could never replace them.
• Have you started from scratch and followed your own installation instructions?
  This step is what fails 99.9% of all documentation. Unfortunately developers are incredibly lazy in this regard, since they think it’s a waste of time. I’m sure NASA has something to teach you about this.
• Can anyone complete the steps successfully?
  Can your 9 year old baby sister or grandma follow the steps without asking for help?
• Can anyone raise a question in the github issues?
  • Are you going to answer respectfully, short and concise and point the user to where to find the information, and take into consideration that perhaps something is not clear from your documentation and need more attention. (Perhaps the UI, a dependency or link has changed?)
  • Or are you going to be a cocky ass and give degrading comments?

---

IF YOU WRITE IT GOOD, THEY WILL COME!

Now, available here:
https://github.com/MichMich/MagicMirror/wiki/Documentation-HowTo

@StacheEnthusiast That is a nice instructable, but mostly useless for us MM people. The reason is that it relies on a pre-compiled image:

Next we need to download the Voice Kit microSD card image for the Raspberry Pi.

So there is really very little to learn and will surely not integrate with MM, as you already stated.
The biggest hurdle is always the sound config and the super non-intuitive bureaucratic Google registration process, requiring you to give both phone numbers and credit card numbers, and countless of impossible options while not being able to navigate through their pages in any sensible manner. (Eg. You click a link, then you realize it’s the wrong page, and you hit back button or the back icon, and WTF, you end up at a different page than you came from! Googleism!)