@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.