@Mykle1 LOL ha ha ha u are still the champion

The last few month’s i tried to find out which voice module is the best for me. It was a hard work but
i never gave up so i tested Alexa, MMM-voice and also Kaliope. So here is my personal result:

First of all it was not easy to get all this diff. modules to work but finaly i did. I think all of them are
good in their own way so Alexa can access lots of diff. stuff and it speaks german (i am german, but its a very hard job to integrate with MM and other modules) same as Kaliope (it supports many languages so the best for international users, but hard to understand and no good documentation). MMM-voice is for english users the very best choice, good understanding and easy to integrate (for ex. MMM-Lucy).
So what do i prefer, to be true none of them my MM is part of my bathroom so for me and my family its important in the morning to listen to the radio (news, traffic and music) this works fine BUT also its the end of all voice recognation cause the modules listen more to the radio than to my voice.
For my needs i wrote a little module to control the mirror by touchscreen or mouse (in my case i use a cheap mouse pad which fits to my bathroom) so i can do all the things that can be done with voice.

I hope i could help some of u nice people with ur own decisions.

@cowboysdude I like this new style… for german translation, of course i can help and im sure other users would love to help too

Hallo freut mich auch mal Deutsch hier zu lesen, ich habe alle meine Module in MMM-voice integriert aber das funzt gut nur in Englisch. Seit ein paar Tagen experimentiere ich mit Kalliope das gibts in versch. Sprachen und bisher sind die Ergebnisse ganz gut. Ich kann euch informieren wenn ich weitere Tests abgeschlossen habe.

@E3V3A of course no problem gimme a ffew minutes

@E3V3A said in How to best process an [object Promise]?:

I have an API that is returning a JSON object as an [object Promise]. At first I was completely cluless to what this was. I now understand it’s because the API is using some asynchronous function to obtain and present the data. I have spent the last day or two to reading up about this. In particular about Promises, async/await, fetch/catch, and even Generators.

But since I’m completely new to this kind of JS programming, I’m rather overwhelmed by the various kinds of methods used for doing this. I could need a small hint of guidance for what to look into. Basically a super simple crash-course to get people like me started in the framework of MM modules. In addition, I’ve read that even seasoned developers get this wrong regularly.

What I think I need to add in my node_helper is:

• read the config file to get an option to be used in the API call
• make the promised API call
• wait for correct JSON response from API call
• push JSON to MMM-module

All the above need to be repeated on a regular interval. (I’m not sure this “polling” need to be implemented separately here, or if the MM config.js reload mechanism is enough.

What is the simplest method to implement that?
I’d love to hear from what you guys think.

PS. I’ve read that async/await is syntactically simpler to use.

Hi maybe i can help. Have a look at the node_helper.js in the MMM-NOAA modules. Their i use the google translate api which also gives back a promise. U can try the solution i useed.

@pinsdorf Thanks, Bluetooth is no problem cause MyRadio can play on any audio output, u only need the correct config. and also if u want to start radio with a signal from another modules just do it
with
this.sendNotification(‘NEXT_RADIO’);
like i do with the Alarmclock module.

OOOO sorryyyy i didnt want a fight it was a misunderstanding my English :-(
I thought he wants multiple pages on ONE screen
my fault
sorry…

@Joshrobbs1 hi of course u can use multiple screens, take a look at MMM-HelloLucy