Sounds about right (screensaver and all). Thank you for the pointer. I just ran it and will see how it does.

Update works with the http:// /remote?action=update Restart does the same error as above regardless of URL.

@trawson I’m the one that submitted the compliments changes, but it shouldn’t have affected any date/time selection . If u send me the js file and your config/file I will see if I can fix what’s wrong Same userid as here, at gmail

@DæmonEyes said in Something went wrong after updating MM: how do I update a module when the top banner comes up saying there is an update? in the terminal, navigate to that modules folder then run git pull

@kellogg76 also, the first script u listed is raspberry.sh which is new install. Upgrade-script is the one that does version upgrades of existing installations (get rid of that message)

I received this error while building opencv: make[2]: *** [modules/videoio/CMakeFiles/opencv_videoio.dir/build.make:128: modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_ffmpeg.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:8811: modules/videoio/CMakeFiles/opencv_videoio.dir/all] Error 2 make: *** [Makefile:163: all] Error 2 It was after entering “make -j4” in the command line. There were a few red marked words before the code up here. Let me know if you would like to take a look.

@racampbellky Rename your current Hello-Lucy folder. (just in case) Open a new terminal window Type cd MagicMirror/modules and Enter Type git clone https://github.com/mykle1/Hello-Lucy and Enter Type cd Hello-Lucy/installers and Enter Type bash dependencies.sh and Enter This does NOT solve your issues with github but it does get you the most recent Lucy.

I saw that - the new fitbit module looks great, I am going to try it later today. Thanks!

@nakulbende there is no ‘error’… just warnings and dumb warnings (no package.json file, yeh so what!),. sadly it looks like this module is way out of date and not updated… there was another user here creating a new fitbit module see here https://forum.magicmirror.builders/topic/12029/what-is-the-procedure-for-reviving-a-dead-module

i finally achieve the installation and configuration of the module but when i run the mirror i got this error WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module './snowboy/lib/node/index.js' and yet in my config.js I don’t specify any path. In the package.json of my snowboy folder the path specified in the main is lib / node / index.js so I don’t understand where the problem may come from

@Hubschra01 yes, askimet is a pain… thanks for your information… I suspect the other bad failure info is reboot after just npm start

hi everyone who could explain to me how to set up the voice control modules. The one I would like to use is MMM-Hotword and I am already having trouble integrating the library. I manually copied the downloaded files on snowboy.kit.ai but its use created problems when importing dynamic modules j have corrected some files and I am correcting those which remain but once finished how to make interact the modules between them starting from the voice command?

@vinck6927 look at the output of two commands list recording devices (microphones) arecord -l list output devices (speakers) aplay -l which device did u use for MMM Assistant config? see https://www.raspberrypi.org/forums/viewtopic.php?t=110302 for speakers

@sdetweil Well the issue with the Pi being stuck at the splash was already happening before the console… maybe it was multiple things? The pi started up and forced me to log in suddenly (no clue why). That is what got me started on checking the SD card. Since i didnt get access via remote (“wrong” username) I had to swap to console, deleted files and couldnt figure out how to get back. It works again ^^ – Regarding the disk-space. I got a 16 gb sd card. However it was the 3-4 previous versions of MM2 I forgot to delete from the bin. I will keep an eye on it and hopefully never run into that problem ^^’ – Really appreciate the help! Thanks alot and big thumbs up to the community here! Also added the “solutions” to the first post so people may be able to find a quick solution as well.

@Varguit and @sdetweil thank you very much

If you have a git hub account you can fork the module’s repo to your own github account and then install/clone it to your modules folder from your own git. Make the change, push it to your remote repo. When there’s an update, you can merge the update with your changed code on github and update the module afterwards. Or not even bother with updates anymore at all, if you want that.

Thanks that was really useful. My revised config is: (start and end date/time, one of many possible formats) config: { dateFormat: "llll", // dateEndFormat: “YYYY-MMDDTHH:mm:ss”, dateEndFormat: “llll”, timeFormat: ‘absolute’, showEnd: true, urgency: 0, getRelative: 0, fetchInterval: 2 * 60000, calendars: [ { I found this site a bit easier to follow: https://devhints.io/moment

@jorgnyg this is a bug in the run-start.sh script get a new one here cd !/MagicMirror curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/run-start.sh >run-start.sh

@iorifly said in erro MMM-HASS: I haven’t tested the spotify model yet. it won’t fail for the run-start script problem… can’t guarantee anything beyond that