PIR false positives

[golles]

After yesterday's video, I wanted to give my EPOs another try, so I reinstalled 1 of them, and I'm still having the PIR sensor giving false positives.

This issue has been discussed before in #64 but that got closed without an actual fix.

Config:

substitutions:
  name: epo-logeerkamer
  friendly_name: EPO Logeerkamer
packages:
  Everything Smart Technology.Everything Presence One: github://everythingsmarthome/everything-presence-one/everything-presence-one.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: !secret epo_logeerkamer_encryption_key

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip:
    static_ip: !secret epo_logeerkamer_static_ip
    gateway: !secret gateway
    subnet: !secret subnet

HA history:

PIR false detections:

• 21:47
• 22:04
• 22:32
• 22:34
• 22:48
• 22:55
• 23:02

When both sensors detected occupancy, it was correct.

[golles]

I had put the device pointing to the wall (~10 cm) during the night, many false positives.

[EverythingSmartHome]

Can you let me know how you power it?

[golles]

I'm powering it with a Xiaomi MDY-11-EP, the 22,5 W max version

[golles]

I've replaced the PIR from another sensor, for about an hour it was fine, but then it started to report occupancy again.

[EverythingSmartHome]

OK if it's facing a wall and still getting detections then please drop us an email through the shop and we can get you sorted

[schneuwlym]

Hi

I've an EP1 since about a week and I also have "semi" random triggers of the PIR. I write "semi" as it often happens during the same time. As an example last night:

• on 2024-12-19T00:29:48.569Z
• off 2024-12-19T00:30:07.300Z
• on 2024-12-19T02:29:49.972Z
• off 2024-12-19T02:30:16.157Z
• on 2024-12-19T03:29:50.569Z
• off 2024-12-19T03:30:17.255Z
• on 2024-12-19T04:29:51.696Z
• off 2024-12-19T04:30:19.574Z
• on 2024-12-19T05:29:48.631Z
• off 2024-12-19T05:30:02.034Z
• on 2024-12-19T05:30:04.308Z
• off 2024-12-19T05:30:14.418Z

At the same time, there is no event from the mmWave.

I know that our power plant overlays some signals to trigger the boilers to start heating. This is also visible as the light sometimes flickers. Could it be related to this?

[phaeton82]

It quite funny. I stumbled upon this when looking into an issue with my Panasonic PIR sensors. Which have the same behavior. But they are not in a EP1. I do have an EP1, so I can test if the same happens in that device.

Some thing I looked into:
Pull down resistor added to esphome yaml. (Didn't work)

A few things on my list to check:

• Use a capacitor for more steady power
• External resistor as a replacement of the internal resistor of the esp board
• Esphome as the cause, is this behaviour since the last my update of esphome? I'm on 2024.11.2

[EverythingSmartHome]

Do you have a USB battery bank? If so, could you try and run it on a battery for a while to see if it happens there? Hopefully it should be apparent quite quickly if it's resolved

[schneuwlym]

Do you have a USB battery bank? If so, could you try and run it on a battery for a while to see if it happens there? Hopefully it should be apparent quite quickly if it's resolved

Interesting idea! I'll give it a try the next days...

[BradleyFord]

my solution is quite simple... I only use the mmWave and ignore the PIR. But I'm also in the process of switching out my EP1s to an alternative

…

On Thu, Dec 19, 2024, 17:15 Mathias Schneuwly ***@***.***> wrote: Do you have a USB battery bank? If so, could you try and run it on a battery for a while to see if it happens there? Hopefully it should be apparent quite quickly if it's resolved Interesting idea! I'll give it a try the next days... — Reply to this email directly, view it on GitHub <#230 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACOZ74EIKZH4YKQ4FPXBL32GKMCZAVCNFSM6AAAAABSXZ2736VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTGMZDINJRHE> . You are receiving this because you are subscribed to this thread.Message ID: <EverythingSmartHome/everything-presence-one/issues/230/2553324519@ github.com>

[phaeton82]

Do you have a USB battery bank? If so, could you try and run it on a battery for a while to see if it happens there? Hopefully it should be apparent quite quickly if it's resolved

I'll try!

[schneuwlym]

Do you have a USB battery bank? If so, could you try and run it on a battery for a while to see if it happens there? Hopefully it should be apparent quite quickly if it's resolved

🙈
Well, at least for my case, I can forget about the theory with the noisy power supply. I've powered the sensor with a power bank and it still regularly triggered at half past...

What bothers me is, that it always triggers at half past... Is there anything else I can try?

[nivekmai]

I had the same issue, tried swapping chargers and reseating the sensor as suggested in #64 , none of it worked, so I just taped over the PIR sensor.

My issue may have been that my sensor is actually looking at another PIR sensor (garage door opener that I can't move), so I expect that could be the cause.

[Alexbeard]

I have the same issue and mostly at night with some constant interval, only PIR is affected

[Pingfragger]

Same issue here.
For me at night the PIR detects motion every hour at 1:14, 2:14, 3:14 and so on...

[golles]

Interesting that that most of you see a constant interval, mine look pretty random on both devices.

[schwaboy]

I'm also seeing this issue. It's at random, but very frequent intervals. I've run it off a battery. I've moved it around. I've reseated the mmwave, co2, and PIR modules. Nothing seems to change it.

[mtf169]

Adding to this thread. I'm seeing the same exact thing on two separate EPOs. It's baffling and infuriating. It's hard to tell during the day all the false detections because it may have been valid (they're in my work space). But throughout the night and times I know nobody is around it's picking up a momentary detection. One of them last night at 2:32am for 10 seconds. The other at 9:32pm for 9 seconds, 1:32am for 22 seconds, and 3:33am for 11 seconds. There's no rhyme or reason for it.