[card:E3V3A/MMM-FlightsAbove]

I have now updated to the Google Assistant and MM Voice Control module: MMM-Assistant. AFAICT it all works now. So now we can focus on improvements, but any help or testing is always appreciated.

[card:eouia/MMM-Assistant]

PS. I am not original developer of this module, I just help maintaining it.

@Mykle1 Thank you! Not sure there will be that many… But now I can focus to also add Alexa!

Wow! This is great. Too bad I’m living in a shitty-weather country. (You got an app for that?) But summers are great. It’s a small city, soon summer nights we can see a lot of crap spinning around in the sky. I’m a big fan of the HeavensAbove app, which I now realize, inspired my name choice for FlightsAbove.

Very good question!

Other people have asked about this.
I have asked about this.
The answer is no.

It would really help the project (and possibly development) to have that.
I’ve worked on this for ~3 months now, and I’m still clueless as to how it all hang together…
Therefore, there will not be much contribution from my side…

Just added a colored legend to the table footer.

I don’t think you have installed the module according to the README.
It seem that you never did npm install.
But there are some other trouble with that script, that I am trying to fix as we speak…

I’ve just pushed all new updates to the MMM-Assistant. GA and MM control now works. Please test.

I would also like to implement the Alexa service so I could always use some help for that.

Cheers,
E:V:A

[card:eouia/MMM-Assistant]

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

@chef said in How I used the ‘Alert’ system as a call display:

Darn can’t post all the code, forum won’t let me.

If anyone is interested in this project I’ll give you the code.

why don’t you post it on github?

@mrcoffee
Try this: https://github.com/shivasiddharth/GassistPi/tree/master/audio-drivers/USB-MIC-JACK/scripts

@MrCoffee I don’t think resetting it is gonna be helpful, unless you know you have installed a bunch of other apt packages, and messed with system settings without writing down what you did.

@idoodler said in MMM-Loxone:

I just implemented vcgencmd it looks like it is a bit quicker. I will check it out the next few days and will push it if everything works.

Yeah, but that only work with Rapsberry Piss , so if you want it to work on other devices, you need to use xset, and if you want to use xset on the Pi, you now also need to tell it that the blank screen should be black, with xsetroot -display :0 -solid black.

@chef
You project sound awesome! IS it private, or will you share it with us?

dtparam=audio=off

@hsukup1
Download their Android app and extract the APK file. then search for their URL (and API key if any).

@mrcoffee
I have seen solutions to this here: https://raspberrypi.stackexchange.com
search there.

Also, only use ONE sound card for AUX (ouput) and MIC (input). Otherwise you will get confused and so your Pie will be unhappy too. It is also highly recommended to disable the internal broadcom sound card when using a USB card. That you can do in the boot config IIRC.

@cdelaorden

• How can we check the video driver without using rapsi-conf?
  in dmesg? in systemd journal?
• How/where do you set the: ELECTRON_FORCE_WINDOW_MENU_BAR=1.
• What would be the easiest way for users to check electron version from command line?

@baldrick
After a fresh reboot and just after starting MM and getting a black screen.
Run with:
'cd $HOME/MagicMirror/installers/; pm2 flush && rm ~/.pm2/logs/mm-* ; pm2 start mm.sh

And make sure that your mm.sh reads:

cd ~/MagicMirror
DISPLAY=:0 npm start

Can you please (open a new issue on Github) and post the output of:

1. uname -a
2. dmesg -x -d -T
3. journalctl -b
4. sudo cat /var/log/Xorg.0.log
5. sudo cat /var/log/lightdm/lightdm.log
6. systemctl list-unit-files -t service -all
7. cat ~/.xsession-errors
8. cat ~/.pm2/logs/mm-error-0.log
9. cat ~/.pm2/logs/mm-out-0.log

Many many modules rely on using a remote “font” source for displaying various icons. However, most icons we ever use, are the same and are very few, throughout the module lifetime.

For example, I have been thinking about all those calls to the font-awesome site that is being continually generated every time a module refreshes or MM is reloaded. Just to re-fetch the same few icons…

This seem crazy to me!

It would be great to hear from someone more knowledgeable how this works with cache in practice and how to best avoid all these calls that are also use to track you.

As I see it, I would prefer that the icons used could be downloaded upon installation or first run, and then prevented from getting requested again. Any ideas how to make this work?