@Cr4z33 OH… All the best! Ralf

I am using the module made by Bugsounet and I noticed that I cannot control my domotics with it like normal Google devices like ie. the Nest Hub 2nd Gen, etc. Is there anything I need to edit or to add to be able to achieve it?

@cr4z33 my upgrade script is a two pass thing test the upgrade, without making any changes. let u know if there are files that would block it. give u opportunity to resolve them actually DO the upgrade. because electron and other things are changing, I also run thru all the modules with package.json files and redo the npm install there (or npm upgrade if they provide one) I do NOT git pull for modules note that in 2.16 (last release) we removed some deprecated libraries. many modules didn’t document that they were used so we get black screen problems. my upgrade does not test for that.

@Bugsounet neither do I usually, but all solutions found around have failed. USB microphones do not get detected anymore from one day to another… 🤷🏽‍♂️ Of course they work perfectly if ie. I connect them to my Windows 10 computer.

@Bugsounet OK thanks.

So I reflashed yesterday my Rpi with the final release of Rasbian Buster. The problem now is that MM is lagging soooo bad at 3840x2160@30 Hz and no matter whether I am using the default modules or some third-party ones… :persevering_face: If the resolution is lower than everything becomes smoother. but please note that this wasn’t happening with previous Buster revisions! Now I don’t know where to start from or what to tweak/edit… Honestly I don’t want to run MM@1080p because this was not the goal for buying a rpi 4 with 4 gigs… :worried_face: @MichMich or someone else has a clue about what’s going on please?

thanks @Cr4z33 , Done! I just wrote to Pilkington!

@ejay-ibm it helps A LOT thanks! 👍🏼

This site was helpful for me. As with everything MagicMirror everyone contributes to help everyone. Just erase the code on this page and copy and paste your code to see where your errors are. Works great for me. https://jshint.com/

I am wondering if someone here has already dealt with a Samsung 2017/2018 line LED TV and image settings for MagicMirror? I ask because I am not a novice with TVs, but the default image menu doesn’t look to give me enough options to increase the brightness as I expected… :expressionless_face: Perhaps I’ve got to access any hidden/service menu to do that? :thinking_face: And if yes how EXACTLY ?

or kill all node related ps -ef | grep node | awk '{print $2}' | xargs kill -9

the design is the MM owns the screen… so you should open a window and show the vlc thru the mirror, i think there is already something that does this…

Wait, you can audit the config file right from NPM? Daaaaaaaaaaaaaaaaaaaang.

@sean said in Alert module is always on: @cr4z33 Remove position field? Not tested. @bkeyport said in Alert module is always on: Position field isn’t supposed to be used. { module: "alert", }, Alert will pop over entire screen when called. Above is as shown within the sample config Ouch my bad. :grimacing_face: Thanks to both of you.