Hi,

I have used MMM-MQTT as the basis for my MMM-TeslaLogger module. In MMM-MQTT there is an own local directory node_modules. At first sight this local dir is identical with the dir node_modules in the root directory of Magic Mirror.

I now try to get rid of the local dir node_modules in my module. But I do not succeed.

In MMM-TeslaLogger.js I only found one reference to the local node_modules, namely jsonpointer.js. This is also the case in MMM-MQTT.

But if I change this reference to the node_modules in the Magic Mirror root, the module doesn’t run anymore and partly generates error messages. The pm2 log also shows error messages for the node_helper. These seem to refer to the line after the last line of the file ???

I am a JavaScript Newbee and can’t get any further. Can someone please take a look at this?

Unfortunately I don’t have access to the error messages right now - sorry. I will deliver them later.

I would be very grateful for any help.

Regards
Josef

Hi, Mat,

my wife and I are very happy with our mirror and we would both not want to miss it anymore. The mirror is a little darker than a normal mirror. But it is perfectly adequate as a bathroom mirror. My wife has never complained about the (missing) brightness. And I myself am also very satisfied.
But before I bought the mirror, I had built a “sample mirror” for my wife from the sample glasses that you can get from the supplier. At that time the direct comparison was possible and the conversion was officially “approved”.

Grüße
Sepp

Hi, I’ve tried several options:

• Motion detector in the mounting arm of the lamp
• Radar sensor behind the glass
• Radar sensor inside near the frame
• Radar sensor outside on the lower frame

Actually, only the latter works well. And that’s how it’s stayed now. The foil of the mirror shields just about everything. Actually the motion detector in the lamp arm should do the job. But apparently it is also shielded by the aluminium so that it didn’t work.

So not yet an optimal solution …

@sdetweil thank you very much again!

@sdetweil
now it worked, my MagicMirror is on the current version .

Many, many thanks for your patient help. It was a somewhat more difficult birth. But the end is good and so everything

I have a lot of respect for you, who created such a complex script and patiently provides support. Thank you very much!

One last question:
During the update there was another message:

npm WARN deprecated @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.

Is there anything else I should do?

@sdetweil
OK, now I have another problem . The upgrade script ran and I think it upgraded some stuff.

At some point, I must have gotten my permissions mixed up. There were a number of directories that were root:root. Here there was Permission denied.

I have now corrected the owners. But now the upgrade script doesn’t run anymore, because it assumes that I am already on 2.10.

Can I force another upgrade?

no, I didn’t say I was on 2.10.

i have now run the script in apply mode. The output is very long and apparently it was not updated, right?

Link Text

Sorry, I’ve always done the update via git. Now I am confused …

@sdetweil Sorry if I misunderstood something. Should I have corrected something on my own?

OK, I started the script again. Now the output is as follows:

curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash
On branch master
Your branch is behind 'origin/master' by 117 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
Untracked files:
  (use "git add ..." to include in what will be committed)

        core
        installers/dumpactivemodules.js

nothing added to commit but untracked files present (use "git add" to track)

And the update script returns the following output:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
the log will be /home/pi/MagicMirror/installers/upgrade.log
No LSB modules are available.
doing test run = true
update log will be in /home/pi/MagicMirror/installers/upgrade.log

saving custom.css
upgrading from version 2.9.0 to 2.10.0
fetching latest revisions
processing dependency changes for active modules with package.json files

processing for module MMM-Remote-Control please wait
----------------------------------
skipped processing for MMM-Remote-Control, doing test run
processing complete for module MMM-Remote-Control

processing for module MMM-NetworkScanner please wait
----------------------------------
skipped processing for MMM-NetworkScanner, doing test run
processing complete for module MMM-NetworkScanner

processing for module MMM-DWD-WarnWeather please wait
----------------------------------
skipped processing for MMM-DWD-WarnWeather, doing test run
processing complete for module MMM-DWD-WarnWeather

processing for module MMM-SystemStats please wait
----------------------------------
skipped processing for MMM-SystemStats, doing test run
processing complete for module MMM-SystemStats

restoring custom.css

So it all worked out now, right?

Thanks for your help @sdetweil and @evroom

@sdetweil Hi, I run the script just now again. The output is the same I guess:

curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash
Auf Branch master
Ihr Branch ist zu 'origin/master' um 117 Commits hinterher, und kann vorgespult werden.
  (benutzen Sie "git pull", um Ihren lokalen Branch zu aktualisieren)
Unversionierte Dateien:
  (benutzen Sie "git add ...", um die Änderungen zum Commit vorzumerken)

        core
        installers/dumpactivemodules.js

nichts zum Commit vorgemerkt, aber es gibt unversionierte Dateien (benutzen Sie "git add" zum Versionieren)