Thanks a lot
Josef

Hi @evgeniy88,
I probably needed a lot less than half a can. The relief of the milling helps to save material and still guarantee stability.

Soon I will start building a bathroom mirror cabinet with a magic mirror. I will post the details in this forum again. :-)

Best regards
Josef

@sdetweil many thanks!

The wrong spelling was the right track. In the installation instructions I had written:

git clone https://github.com/spitzlbergerj/MMM-Teslalogger
cd MMM-Teslalogger
npm install

But it must be called (capital L)

git clone https://github.com/spitzlbergerj/MMM-TeslaLogger
cd MMM-TeslaLogger
npm install

Hi,

I have developed a new module. Everything works wonderfully on my mirror. I uploaded the module to github and offered it there:
https://github.com/spitzlbergerj/MMM-TeslaLogger

Now others have loaded the module via git clone and got an error:

loader.js cannot load /modules/MMM-TeslaLogger//MMM-TeslaLogger.js

I can reproduce the error after a git clone on my mirror too. But I cannot find where the second “/” has crept in.

What could be the reason for this?

thanks a lot

Josef

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 :smiling_face_with_open_mouth_smiling_eyes: :thumbs_up: .

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 :disappointed_face: . 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?