@diccon yes, a module is missing a required library , you need to run npm install in the module folder for the specific module
this is version 2.28, latest is 2.29, we have added code to catch these failures and continue running, where before we crashed.
@togletree93 thats outside our app…
can you try in server mode and
npm run server
then open browser to http://localhost:8080
this turned out to be a permissions problem. the folder was created w the synology user, but the container is running as user 1000
@Bimtronic ignore the audit reports, nothing you can do about them. part of the reason request is deprecated.
@Bimtronic in the MagicMirror folder
@bugsounet you should make it normal, like the rest of the modules…
@Bimtronic can you show me the config.js, xxx out any apikeys or private info
@canlio weather is done all in browser, so open the developer window, ctrl-shift-i, select the console tab, put weath in the filter field.
openweather has changed their business model, the apikey is backed by a credit card
@canlio cool, but, its not supposed to work. they told us publicly 2.5 was supposed to stop working in October… hmmmm
@cgillinger This is one place where the inherited module functions are not so good
getTranslations()
happens WAY before any code is run so you can’t adjust its response based on other info the config might have provided…
and we don’t expose any functions to do the work not related to the files returned from that function
but your code could do the translations BEFORE giving the content to MM… so there would be nothing to translate
after installing Jan 1 2025 MM version, events broadcast to MMM-CalendarExt3 are clipped incorrectly
apply this fix (til next release)
cd ~/MagicMirror
git fetch origin pull/3679/head:_fix_clipping
git switch _fix_clipping
npm run install-mm
# if you get an error error, rm package-lock.json
# and repeat the git switch
restart MM
this fix has been accepted and added to the next release
you can use that package instead
see https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code
to get the develop branch
#NOTE: using develop requires a new
npm run install-mm
absolutely my fault… BUT
this release has been stable and in test since October… but clearly not enough tested it.
@Lusbueb done… I never copy/paste that instruction… I push the green button to copy the code in this current repo (regardless of the name)
@djkleric erase
rm package-lock.sjon
@KristjanESPERANTO the bane of the internet, old info never dies
no one ever reads the doc
@MDWEBB said in Version 2.30.0 Calendar fix for clipping broadcast events:
_fix_clipping
you need to be on _fix_clipping
do
git switch _fix_clipping
if you get package-lock.json would be overwritten
do
rm package-lock.json
the do the switch again
and then
cd ~/MagicMirror
npm run install-mm
@Klinge if you use the os desktop menu top left, preferences, last entry i think is display configuration, you can rotate there
version 2.30.0 on Jan 1, 2025 requires an updated nodejs version, minimum 20.18.1
we also support node 23 now
use my upgrade script and it handles the upgrade…
For Rasperrby pi 0W users, this looks likk the last nodejs version for the armv6l devices.
no other build has been done for quite some time.
I am sure we will be forced to upgrade nodejs again (soon) as node 20 is getting old… now latest is node 23
@MDWEBB ok
two things
if you comment out a module in config. js with block comment markrrs /* */ then must get the opening and closing braces too
a better way is just to add
disabled: true,
after the module:… line
chsnge back to false to re-enable the module
second
can you show me the output of
cd ~/MagicMirror
git branch
@plainbroke awesome
i should have remembered the path problem