@sdetweil Thanks for the heads up, Sam!

I regularly apply OS updates to my RPi, which runs MM, like on all my other PCs and servers.

sudo apt update
sudo apt dist-upgrade -y

Two days ago I applied the latest Debian Stretch kernel updates which brought an unexpected surprise.
Apparently these updates contain also new configuration files for the screensaver and display control, which overwrite the current ones on the system.
A few hours after the update I went to my MM and it greeted my with the password prompt of the screensaver.
As I didn’t find the documentation anymore which options had to be changed and where, I chose the “lazy camper” route and simply installed xscreensaver.

sudo apt install xscreensaver

In xscreensaver you can not only adjust the screensaver and delay for blanking off, but you can completely disable the screensaver, what I did. Problem solved.
The display switches off as normal and switches on again when the sensor detects proximity as usual without the password prompt.

@sdetweil Thanks for that hint!

@sdetweil I turned many years ago from windows towards macOS and not that familiar with the tools on windows anymore. If winscp provides such support, that’s of course great. I think the OP should provide more details and we will certainly jointly help him.

@luke2102 if your coming from the windows corner, I have a very strong assumption that the problems are caused by the Texteditor you use on your windows system. Typically windows users have the wrong end of line settings for Linux system , CR instead of LF, and/or set the wrong quotation marks. I’ve that so often, that I would bet on that :)

You need to put a 10k pull-up resistor between The GND and data for the DHT11. The AM2302 is identical to the DHT11, but is shipped on a small PCB, which already has the resistor included.

I fully share @sdetweil assement regarding the sensor. Additionally you have to account for the intrinsic inaccuracies of the sensor. You’ll have to conduct several tests and compare the results to get a conclusion if the position of the sensor is is suitable or not.

Excellent build! The many hours you spent were worth it.

@cowboysdude thanks, mate! Your new look is fantastic! I love the clean and structured layout where you get information at a glance. Which home automation system or sensors/actors do you use?

@sparkgap-code I have no Memory issues with this module. What I experienced a few times is that some modules don’t play well together and memory problems occur. I had that with MMM-Rain-Map and MMM-GoogleRoute. Each of the modules was fine alone. As soon as both were activated I ran into memory overflow. Lastly I gave up on GoogleRoute as I had no real need for it.

Well, that means I‘ll have get much much deeper into coding and learn js. But hey, why not? Cold and dark autumn is coming and that’ll be a nice project 🤗

Thanks for this new PIR module! I replaced last night the MMM-PIR-sensor module with yours and it works perfectly, also with my microwave sensor.
Especially the behaviour after the first start is now as expected, as the display is switches off after the countdown, without initializing the sensor first. With MMM-PIR-sensor the display would have stayed on after the first start until the sensor catches once a motion and the start the coutdown. I tweaked the node_helper.js to correct that, but after each module update I had to reapply that tweek. That belongs now to the past. Great job!:clapping_hands_light_skin_tone:

I have a feature request:
I would like to have two configuration options available to adjust the colours of “displayStyle”, as currently it is hardcoded in green:

• One option to adjust the colour of the remaining time (wich is currently green).
• Another option to adjust the colour of the past time (currently dark grey or white).

something like this:

displayStyleRemaining: 'e2e2e2', //RGB value of the remaining time
displayStylePast: '454545', //RGB value of the past time
[...]

I’m using the “Bar” style on “bottom_bar” position, which shows a decent thin line over the hole width of the mirror, which slowly creeps down to the left. But it is hard to distinguish the remaining time (green) and the past time (white) of that bar. I would prefer to adjust the remaining time to white, and the past time to black, as an example.

What do you think?

Oh BTW: I might help other users, if you enhance a little bit the README on GitHub on how to make the display styles visible. It took me some trials until I found out to configure an empty string for the “text” option to make the other styles show up.

@mrmidi that’s a cool module! I‘m check it out in the next few days and control it via my Grove gesture sensor.

@fribse hmmm…I’m not sure if painting is a good option, because it will be difficult to apply the paint accurately and evenly. I took some black foam matte that in which my mirror was wrapped in. That can be cut very accurately. May I ask why black paper or cardboard is not a viable option?

@eniac ich vermute das liegt an der DNS Auflösung. Gib mal bitte die IP Adressen anstatt der Host Namen ein.

@djdocta I don’t use a Spotify module as I have the sonos module which shows every music service it is connected to.

@djdocta Tese are the modules I have currently installed. Thy are distributed over 3 pages:
MMM-pages
MMM-TextClock
alert
updatenotification
clock
MMM-MyCalendar
newsfeed
MMM-withings
MMM-Strava
MMM-Sonos
MMM-DarkSkyForecast
MMM-RAIN-MAP
MMM-DWD-WarnWeather
MMM-MyScoreboard
MMM-Podcast2
MMM-PublicTransportHafas
MMM-Remote-Control
MMM-GroveGestures
netatmo
MMM-Tools
mmm-hue-lights
MMM-Homematic
MMM-PIR-Sensor
MMM-AlexaControl
MMM-page-indicator

@cowboysdude oh no, come on😢! I‘m really sorry seeing you leaving. But I want to thank you so much for your support and inspiration and hope to see you soon again. ☀️🤘🏻

@Philly From what I see in the picture the soldering seems to be OK, but I’m not sure you wired it correctly on the GPIO. The picture is somewhat blurry, so I can’t recognize it well enough.

The red wire should go to the first right pin, which provides +5V. From the picture it seems to go to the first left pin, which provides only 3.3V.
The black wire seems to go to the second right pin, which also provides +5V. It should go to the third right pin for GND.
Finally, the brown wire appears to go to the third left pin, which is provides a SCL signal (serial clock) and is reserved for I2C. Don’t use that, but the forth left pin, which is a digital I/O.
Please check the wireing again according to my description and adjust also the config.js accordingly.

{
			module: 'MMM-PIR-Sensor',
			disabled: false,
			config: {
				sensorPin: 4,
				powerSavingDelay: 30, // (seconds) how long the monitor will be turned on

			}
		},

@Philly Sorry for coming back somewhat late, was ill the last few days. Yes you need to solder the pins to the sensor, as they are then connected with Dupont cables to the GPIO on the RPi. Probably the pins are not soldered cleanly and don’t provide electrical contact.