Hello!
The new version of MMM-APOD allows to display the image of the day in the background!
Please read the documentation to customize and update MMM-APOD on your MagicMirror :winking_face:
Grena
Hello!
The new version of MMM-APOD allows to display the image of the day in the background!
Please read the documentation to customize and update MMM-APOD on your MagicMirror :winking_face:
Grena
Hello everyone,
MMM-VigilanceMeteoFrance 2.2 was released and uses the simplified authentication system from Météo France .
A single Application ID is now required instead of 2 keys for the module to work, please update your configuration! More info here
Grena
@grena
Bonjour,
Bonjour @Philip-0,
Je ne comprends pas à quoi correspondent les 2 informations à renseigner : apiConsumerKey et apiConsumerSecret
Il semble y avoir eu une évolution du portail API de Météo France sans communication particulière en direction des utilisateurs (je découvre donc les nouveauté suite à ton message). Actuellement, seul un Application ID est nécessaire pour générer un token Oauth2 permettant d’accéder aux données contrairement aux 2 clés utilisées précédemment (procédure qui semble toujours fonctionnelle).
La durée de validité est d’1 heure dans le 1er cas et il faut indiquer une durée (laquelle pa ex. ?) dans le second. Est-ce à dire qu’après cette période, le module ne fonctionne plus ? Dans ce cas, que faut-il faire ?
Il n’y a rien à faire, le module va régénérer un nouveau token Oauth2 avant de récupérer de nouvelles données !
Je vous remercie par avance pour votre aide
Bref, j’ai préparé une mise à jour du module et de sa documentation pour prendre en compte ces évolutions et permettent à tous les utilisateurs (nouveaux et anciens) d’utiliser MMM-VigilanceMeteoFrance. Je dois encore tester cela avant de pousser la nouvelle version !
Hello everyone,
MMM-VigilanceMeteoFrance 2.0 was released and uses the new vigilance API (v1) from Météo France which provides more complete data.
Free keys are now required for the module to work! More info here
Grena
Got everything to work perfectly…
:thumbs_up:
The following page is very useful to test the functionality of the sensor before you implement the change to mirror config file (thanks to @sdetweil for posting the link in a different thread): https://projects.raspberrypi.org/en/projects/parent-detector/3
Yes, You can also run the python script of the module: python3 -u ~/MagicMirror/modules/MMM-PIR-Sensor-Lite/pir.py SENSOR_PIN
another user noticed this only worked for the 1st HDMI port on the pi4.
Yes, I add this point of vigilance at the beginning of the readme :white_heavy_check_mark:
Hello everyone,
The module is ready for the new season which starts on November 21! Think about:
Grena
:fire: MMM-PIR-Sensor-Lite 1.2 has just been released! It’s allows you to manage monitor on Debian 11 Bullseye :sign_of_the_horns_medium-light_skin_tone:
Learn more in ReadMe
MMM-PIR-Sensor is not maintained (GitHub repo has been archived) but you can use MMM-PIR-Sensor-Lite!
I assume your Raspberry Pi is running Bullseye (the latest Raspberry Pi OS)?
If yes, monitor’s management has changed since Buster but it should soon be supported in my module :grinning_face_with_big_eyes: It’s currently being tested…
@Volkae said in MMM-PIR-Sensor-Lite does not switch HDMI off:
yes, I did but I did not run RTSPStream while running the testing branch, sorry.
No problem, I’ll try to reproduce this issue!
MMM-RTSPStream is no longer being actively developed :neutral_face:
So, I refer you to the advice of the author of MMM-RTSPStream to find another solution:
:warning: This module is no longer being actively developed. I will accept PRs and leave the repo active, but will not be directly supporting any issues. If anyone is interested in assuming ownership of the module, please contact @shbatm. :warning:
Why?
I am no longer using this module on my own mirror. After several years, I found that I use the snapshots much more frequently than I streamed the actual cameras, which can be performed by much simpler modules and methods. To enable streaming, WebRTC (like MMM-HomeAssistant-WebRTC) is a newer and better standard with much lower server overhead and latency for delivering RTSP Streams to the frontend than any of the options used here, in the future, this will be the method I focus on and I will not try to shoehorn another technology into this module.
@Volkae, have you updated the module from the testing branch since your last message that it worked?