@sdetweil

That was my first idea as well. But I was locking for a smarter solution. :)

I discovered a strange conflict in raspian 64x. Before I did always use the 32x variant.

I did some research and testing why the display_hdmi_rotate command in the config.txt apparently didn’t work. It seems there is a conflict with DRM VC4 V3D driver (which is enabled by default). Just un-commenting the line #dtoverlay=vc4-kms-v3d the screen rotates (even the splash picture) as expected. The driver obviously overwrites the display_hdmi_rotate command.

Now the MM and splash have the right orientation. Only the default weather app says loading, but it will be replaced by another module anyhow.

Thanks, andyyy

@sdetweil

In the config.txt I did set display_rotate=3 and/or display_hdmi_rotate=3. It shows no effect.

On the desktop I can rotate screen without any issue but the splash stays in the default orientation.

Hi,

I am setting up a new MM from scratch because my current image got pretty buggy over the last years.

I just installed the MM using the automated installation from @sdetweil. With that you can replace the default splash screen with the MM splash picture. It works.

But I would like to have MM splash picture rotated. I tried to modify the magicmirror.script file but it didn’t work out so far. Can anyone explain how to do it?

Thanks!

@strawberry-3-141

I am on the latest MM version, but something screwed up in the background.

I did load the backup with MM 2.16 and started over again. No success.

Eventually I loaded my oldest available backup with MM 2.9. Interestingly, all modules still worked in this old setup incl. MMM Fuel. From there I updated the MM to 2.17.1 and surprisingly MMM Fuel kept working. :)

Apart from the fuel module 3 other module seem to be incompatible with latest MM version resulting in a black screen on startup. Most likely some required dependencies got removed in the MM core.

It would be great if we could introduce a community maintained compatiblity list of all 3rd party modules. I mean the status “maintained” or not gives a hint, but it does not necessarily mean it will not work any longer.

For now, I am happy. :)

@strawberry-3-141

tankerkoenig I am using from the beginning. In Germany there is no other API I could you I suppose.

I did update to latest MM version 2.17.1, but the MMM-Fuel just says loading (laden). My config hasn’t changed since months.

Any idea?

@sdetweil

Thx, after fixing this the next lib is missing. I just give up using that module.

I have a vision for the future MM development. All modules should run in a separate container/sandbox or capasulated/isolated somehow. So when they fail for whatever reason, the MM stays alive and reporting a specific error message.

Don’t get me wrong I highly appreciate the work/effort of michmich and his team.

@sdetweil

I screwed up my MM entirely. pm2 crashed randomly for an unkown reason.

When did “npm intall” on all modules after the update to 2.16, mostly npm complaints about some vulnerabilites. So I did “npm audit fix” on all them all. Maybe some dependencies broke rather than being fixed.

Another thing; npm complaint that 2.16 is uncompatible with node 10.x and npm version. So upgraded both to the latest one.

Mostly like all that ruined my MM.

Thus, I loaded back last working backup and just did “npm install” on all modules. Npm is still complaints about the node version, but all module run except MMM-MyCalender which seems to be uncompatible with 2.16.

@sdetweil

made it with npm install -g npm@6.14.14.

I still have issues with the default wheater module. The old “currentweather” module works but new default “weather” module just says “loading”.

@sdetweil

How do I revert to npm v6?

@sdetweil

I got electron installed again with specifying a version (sudo npm install electron@6.1.12). No idea, why electron disappeared in the first place.

@Fozi

The MMM-MyCalender has indeed an issue with 2.16. causing a black screen. And MMM-Fuel is saying “undefined” for an unknown reason. Both modules are disabled for now.

My MM boots and shows the all other modules again.

With each MM update something crashes, mostly one of the 3rd party modules because one or more dependencies are lost/changed or deleted.

Thanks for your help. Great community!

@sdetweil

I tried it again. Now the electron does not even start.

> magicmirror@2.16.0 start
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

sh: 1: ./node_modules/.bin/electron: not found

I tried to re-install electron with "sudo npm install electron@latest
", but no change.

@sdetweil

Solved for now :)

I did:

sudo git fetch --all
sudo git reset --hard origin/master
sudo git pull origin master

My system is still very fragile. When do npm install after that, the screen turn black after reboot.

@sdetweil

I did revert to the last working backup and tried your update script. And here it failed updating with same error message in the log file.

Should I delete all the files in the error file as I did?

Hi,

I do have an issue updating to 2.16. As usual I needed to reset the repro (git reset --hard), but few files are there they prevent updating:

Updating 491f5aa7..26a76f80
error: The following untracked working tree files would be overwritten by merge:
        .github/codecov.yml
        .husky/.gitignore
        .husky/pre-commit
        css/custom.css.sample
        modules/default/weather/providers/envcanada.js
        tests/configs/data/calendar_test_recurring.ics
        tests/configs/data/weatherforecast_data.json
        tests/configs/modules/alert/default.js
        tests/configs/modules/calendar/recurring.js
        tests/configs/modules/weather/forecastweather_units.js
        tests/e2e/ipWhitelist_spec.js
        tests/e2e/modules/alert_spec.js
        tests/unit/mocks/logger.js
Please move or remove them before you merge.

Just removing them wasn’t a good idea. Eventually the update went through but I did end up with black screen even with npm install on all modules.

@sdetweil
Unfortunately your update script didn’t work either.

Any advice?

Thanks!

@sdetweil

I tried the method “export ELECTRON_ENABLE_LOGGING=true”.

The command line says:

[3313:0518/105432.610396:INFO:CONSOLE(159)] “Uncaught TypeError: Cannot read property ‘line’ of undefined”, source: http://0.0.0.0:8080/modules/mvgmunich/mvgmunich.js (159)

Interestingly though, it is not written to the log file. In there it states:

(/home/pi/MagicMirror/modules/MMM-Logging/node_helper.js:37 Class.socketNotificationReceived)
[18.05.2021 10:49.32.615] [LOG] 2021-05-18T10:49:32 Browser Error: {
“isTrusted”: true

@sdetweil

yes, I do use ssh to connect to the mirror.

I’ll continue tomorrow debugging.

@sdetweil

Are there some other ways to create the log data?

I run the MM with npm start. Connecting a keyboard is currently not that easy because the MM is build nicely in my picture frame and sealed. :( My development was actually finished (I thought).

Re: no result from mvgmunich modul

Hi,

I do have an issue with the module “mvgmunich”. Out of sudden it has stopped working again.

The module reports “undefined” or nothing at all.

Interestingly I didn’t change anything since ages. The module received no update since 2019 and my config is still the same.

Today I did reinstall the entire module and tried even the default config of (https://github.com/mrVragec/MMM-mvgmunich). No success. The module will be loaded but no stations are shown.

Any idea?

P.S: MM is up-to-date v2.15

Thanks.

@thobach

curl -X POST https://login.microsoftonline.com/common/oauth2/v2.0/token

Length Required

Length Required

---

HTTP Error 411. The request must be chunked or have a content length.

I am sure curl is installed since other modules with OAuth are working as well.