@oli1204 There seems to be a problem with the DNS resolution. Just for curiosity… Could you try the MMM-Tankerkoenig Module? It basically does the same as MMM-Fuel.

Is the same error thrown?

BTW: The position is misspelled…it must be “bottom_left”

@MadScientist said in Display not bright enough:

Hi there,
what you want is a display with high contrast. I think VA panels have the best.

I can fully confirm the better contrast on VA panels compared to TN panels.

@elaineezhu maybe a superficious question from my side, but have you checked the module description for compliments?
This gives you all options how to configure the module. You don’t need to customize the module itself. All configurations are done in config.js.

And no, using the Mac terminal and connect to MM via ssh is just good! This is how I configure my MM all the time.:smiling_face_with_smiling_eyes:

Maybe you can post us, what you want to achieve (or how you want to adjust the compliments) and provide your current config or compliments looks. That would lever the chance to provide you concise help.

Edit: I forgot to mention…when you make changes to config.js the MM has to be restarted. Either this is done automatically when you installed MM via @sdetweil script (what I highly recommend!) or you enter in terminal

pm2 restart all

(given that MM is controlled by pm2)

@Alloc Thank you!
I got MMM-withings working just as described in the Redme.md. Double check if you use the CLIENT-ID at the very end of the URI in step 4 and the correct callback address you registered.

The most tricky part cemes later in steps 7/8/9 when you have to copy the token, insert it into the tokens.json file, save it and restart MM…all within 30 seconds. Probably, you’ll have to repeat these three steps a few times before you see the fist time your graphs.

Oh, and another note: The refresh token is valid for 4 hours only. That means if you shutdown your MM for more than 4 hrs and start it then again, then you have to repeat all steps 4-9 again.:unamused_face:

@xdenneboom I have an IKEA frame, too (Ribba), but mounted a second one behind a he first too gain more depth. Here is my mirror where you can see how I managed the power supply for the display and the RPi.
Regarding the brightness of your display try to enhance the contrast instead of the brightness only.

@Lordy merry Christmas 🎄! We had recently a discussion about the same issue here. Maybe that helps you.

@ELMAGO a few weeks ago I tinkered around with MMM-FaceReco-DNN, there are a few very good links to great sources regarding facial recognition on a RPi. But be aware or the fact that facial recognition is a very resource hungry job and may push a RPi to the limits.

@kusselin du musst erst in das /modules Verzeichnis gehen (s. meinen Post oben) und dann den Löschbefehl aus führen

$ cd ~/MagicMirror/modules
$ sudo rm -R MMM-FHEM
...
$ git clone https://github.com/BenRoe/MMM-FHEM
$ cd MMM-FHEM
$ npm install

@09succotash As said, copy the whole MM-folder, eg. via scp to another PC and then reinstall Raspbian.
I’m sorry that I can’t provide a more satisfying solution:disappointed_face:

@Clubjack if you use ‘cp’ then the file is really copied under a new name. The original file will still exist.
If you use ‘mv’ then the file will be renamed, there will no copy of that file.

Thus use ‘mv’ to rename the files. Otherwise you’ll have two .js files in your module.

Edit: @sdetweil was 10 sec. quicker than me:face_with_tears_of_joy:

@kusselin said in a new problem with fhem:

yes than i can see the mirror again and i have the npm install in the fhem directory make.
but so the mirror is not show again

If the mirror is working again after deactivating the module, then remove the module from the /modules directory and re-install it from scratch.

$ sudo rm -R MMM-FHEM
$ git clone https://github.com/BenRoe/MMM-FHEM
$ cd MMM-FHEM
$ npm install

@09succotash Umpf…the last thing that comes to my mind…disconnect the PIR-Sensor from GPIO. Maybe it is not connected to the right pins, which may cause that strange behaviour.

Do you have the MM-software installed? If so, then copy the whole MagicMirror directory to a save place and reinstall Raspbian from scratch. It’s probably the fastest and easiest solution after all, if nothing else is installed on the RPi.

Maybe someone else here in the forum can help? Guys?

@09succotash

If you cant open a terminal directly on you Pi, then try to open a ssh session from another PC. Then you have terminal access and you can start removing the PIR installation. E.g. open a terminal from a windows PC and enter at the prompt:

ssh pi@192.168.0.xx

(means the IP of your Pi)

You’ll be prompted to accept the ssh-key (yes) and then you are prompted to enter the password (keystroke will nor be displayed). Then you should be in.
As you are using Stretch go edit /home/user/.config/lxsession/LXDE-pi/autostart and remove the ‘@/usr/bin/python /home/pi/pir.py’ entry you made before. save the file and reboot.
Then go into your pi’s home folder end remove pir.py, monitor_on.sh and monitor_off.sh.
Basically you do the reverse order when you installed the scripts.

@SirVer
I’d see two options:

1. Disable the update notifikation by inserting

disabled: true, 

in the module config

{
module: "updatenotification",
disabled: true, 
position: "top_bar"
},

But then all update notifications will be disabled.

2. You fork the module into your own github repo, apply the changes you made, and install the module from your own repo. This might require to make also adoptions in the code for references, which point into the original repo.
   But then you will not have automatically update notifications, if the original module has been updated.

What I do is to document my changes in my private repo and to apply them if the module gets updated. That’s for me the easiest and quickest way.

@09succotash Seems like you use @cowboysdude scripts to control the display.
Those are really simple scripts which work usually out of the box.

What I’d guess is that the autostart folder might cause the trouble.
Which Raspbian ver sion do you use?
In Raspbian 9 (Jessie) the autostart folder was in

/home/user/.config/lxsession/LXDE-pi/autostart

(just as written in the above mentioned instructions)

In Raspbian 10 (Buster) the autostart folder has changed to

/etc/xdg/lxsession/LXDE-pi/autostart

If you are on Buster, remove the /autostart folder in /home/user/.config/lxsession/LXDE-pi you may have created. Then go to

/etc/xdg/lxsession/LXDE-pi/

and insert there the the required line in the autostart file

@/usr/bin/python /home/pi/pir.py

Hope this helps.

@kusselin Have you deactivated the module like @thedoorsfanatic recommended? Alternatively you can also comment the module in config.js. Just to make sure that there are no other side-effects.

/*
….
…..
…..
*/

@falke69 Thanks so much! I bookmarked this post for later use, if the MMM-Homeatic module won’t serve as I expect. Very interesting that you have to script the CCU. Great job!

@falke69 What I didn’t like with MMM-ioBroker, was that the door and windows sensor didn’t display “auf”/“zu” but “true”/“false” or “1”/“0”. I couldn’t find a place in the code to modify or translate the status messages, so I dropped it.

@falke69 Damned…Then try port 8087, maybe this is your standard port.

Are you using Homematic components, too? If so, then check MMM-Homematic. I switched to that module as its presentation is much nicer and the readouts of the actuators and sensors are translated and can be coloured if thresholds are met.

@falke69 is “[IPv4] 0.0.0.0 - Alle IP-Adressen zulassen” enabled?
If this doesn’t work, too, the I’d ask bluefox in the ioBroker forum. There is also a very lenghty thread about that issue.