@mz-ber If you remove the resistor completely without any replacement the sensor won’t work any more.
Read the statement by Michael Teeuw here.
Posts made by Fozi
-
RE: PIR Sensor: false positive detections
-
RE: PIR Sensor: false positive detections
@mz-ber Just put all wires through the bead.
With the RCWL-0516 you should note that they can be very sensitive (up to 7m on free sight) and detect motion even through walls. First I went the alu foil route, too, but then modded my RCWL-0516 with a trimmer. Now the mirror is triggered when I approach the mirror less than 1m. Check the link in my signature for details, if you like. -
RE: PIR Sensor: false positive detections
@zoltan Really nice build!Congrats!
Yeah, a low-pass filter can solve the interferences from the WiFi module, too, of course. But due to my lazyness and impatience I sacrificed an old VGA cable and re-used the ferrite bead:beaming_face_with_smiling_eyes: -
RE: PIR Sensor: false positive detections
@mz-ber said in PIR Sensor: false positive detections:
HC-SR501 PIR
I’m with @Stefan723. I had used MMM-NewPIR in the past but switched back to MMM-PIR-Sensor again for reasons. MMM-PIR-Sensor is simple, robust and does the job reliably. May be you have some intereferences, too, which trigger false positives.
Due to the proximity of the Vout and GND wires to the WLAN module, unwanted interferences may occur which might prevent the PIR sensor to switch from high (motion detected) to low state (no motion detected). The wires work like an antenna in that case. As a result, the display will stay on. A ferrite bead attached to those wires, e.g. taken from an old VGA cable, reduces the interferences and allows for correct state change.Hope that helps.
-
RE: MMM-Buttons
@johans I guess you need to use a pulldown resistor to avoid floating GND.
Here is a sketch how to use the pull-down-resistor. I had the MMM-Button module installed in the past, but replaced with a gesture sensor (MMM-GorveGestures)
-
RE: PIR-Sensor - not detecting 2nd "motion" - MM stays dark
@kastore Check following things:
- the attribute in you config is spelled
sensorPIN
It should be
sensorPin
- Check the correct wiring on the GPIO. You have to use the BCM notation. In you config you assign pin 17. In BCM notation it is the 6th pin from top on the left row.
If you took pin #17, then it is the 3.3V pin. It is 9th pin from top on the left row. this won’t work.
-
RE: MMM-NINA
@majorc Versuch’s mal mit diesem Eintrag in der custom.css:
.MMM-NINA .nina-wrapper .nina-alert.severity-Fine{ text-align: right; }
-
RE: MMM-NewPIR v3
@djboob66 you’re right…I forgot that there might be potential issues with the latest version. Thanks for the correction!
@philmavedzenge : Generally I’d recommend to use @sdetweil update script when updating to a new MM version. (see here) As you already updated to 2.17.1, use this command with
force
at he end instead ofapply
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
Sam‘s script checks, if the correct node and npm versions are installed and updates them accorgingly if necessary.
-
RE: MMM-NewPIR v3
@philmavedzenge in your home directory execute following two commands:
sudo npm install -g n sudo n latest
This installs the latest node version
Edit: added sudo
-
RE: 2.17.1 error with MMM-DynamicWeather
@Fozi wins!
Probably my first and only time :beaming_face_with_smiling_eyes: