Offline
@karsten13 No worries! I just wanted to let you (and others) know that the config entry does not solve the issue.
I made a little research around CORS and -at least for me- it doesn’t seem to be trivial to configure electron in a way that specific origins are allowed without disabling the CORS policy completely.
Anyone around with more knowledge?
@mumblebaj I have the same issue with the same error, but with MMM-Homematic since the update to MM 2.18. MM cannot connect to my CCU2 controller to get the device statuses.
@karsten13 your proposal unfortunately didn’t work :-( But thanks anyway!
@oberfragger Congrats to your wonderful built! It’s very impressive how much effort you put into that! Wished I had knew a few years earlier about MM…that would have saved me lots of discussion with my better half about which mirror should have been installed in our new bathroom. :grinning_face_with_sweat:
@jon4s Are you running Bulls Eye? If so, then it won’t work (see https://github.com/paviro/MMM-PIR-Sensor/issues/123).
Obviousl you should stick with Buster.
@mithgar
Have you tried to enter the new IP-address in the config?
ccuHost: "xxx.xxx.0.2",
Depending on your network and router the name resolution might not be always reliable. As you gave the CCU a fixed IP, you can also use that fixed IP in the config.
- I’m a VERY BAD guys in this forum
…and in your own forum, too.
@oberfragger Der AM312 funktioniert genauso gut (oder schlecht) wie die anderen PIR-Sensoren. Es könnte aber sein, dass du Interferenzen auf den Sensorleitungen hast, die vom WiFi-Modul des RPi herrühren könnten. Abhilfe schafft hier eine Ferrit-Perle, durch die du einfach die Leitungen ziehst. Wenn du keine Ferrit-Perle gerade zur Hand hast, kannst du auch eine alte VGA-KAbel kanibalisieren und die Perle vorsichtig vom Kabel abtrennen. Ich habe hier neulich erst was dazu gepostet.
@thgmirror said in PIR Sensor: false positive detections:
It is not a step-down/up … it is called Pull-Up, resp Pull-Down.
Are you dealing with 3D printing? Just asking, because step-down converters are quite popular for modding cooling fans in that hobby :beaming_face_with_smiling_eyes:
@kastore I am very confident that the module is using seconds, not minutes, to determine the powerSavingDelay. This is what I recognize from the code in node_helper.js. As the module is still not working as expected, there is still something going on.
My proposal is to delete the module and re-install it from scratch AND follow the 5 points as described in the installation description on Github. Click.
Further, try to use a different pin than 17.
Here is how I wired my PIR-sensor and my config:
{
module: "MMM-PIR-Sensor",
disabled: false,
//position: "top_bar",
config: {
sensorPin: 4,
powerSavingDelay: 90, // (seconds) how long the monitor will be turned on
//supportCEC: true,
//presenceIndicator: "fa-bullseye",
//presenceIndicatorColor: "red",
}
},
Another posibility is that the WiFi module on the RPi is causing interferences, which lead to the problem you have. A ferrite bead over the sensor wires or a low pass filter can help. It is not uncommon that the WiFi module can be the culprit.
In the last days there was a disussion about false positives with the PIR sensor. Maybe you check that thread, too.
@mz-ber If you remove the resistor completely without any replacement the sensor won’t work any more.
@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.
@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:
@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.
@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)
@kastore Check following things:
sensorPIN
It should be
sensorPin
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.
@majorc Versuch’s mal mit diesem Eintrag in der custom.css:
.MMM-NINA .nina-wrapper .nina-alert.severity-Fine{
text-align: right;
}
@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 of apply
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.
@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
@Fozi wins!
Probably my first and only time :beaming_face_with_smiling_eyes: