@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?