D1 Mini + 12V PIR from old alarm system

[kwatt (Kenneth Watt)]

Nothing untoward i can see, the latest round of entries there is this:

-----------------------------------------------------------
 Add-on: ESPHome Device Compiler
 Build your own smart home devices using ESPHome, no programming experience required.
-----------------------------------------------------------
 Add-on version: 2024.11.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.2  (aarch64 / green)
 Home Assistant Core: 2024.11.2
 Home Assistant Supervisor: 2024.11.4
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[09:23:59] INFO: Configuring timezone (Europe/London)...
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/30-esphome-fork.sh
cont-init: info: /etc/cont-init.d/30-esphome-fork.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service esphome: starting
s6-rc: info: service esphome successfully started
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service discovery: starting
[09:24:03] INFO: Waiting for ESPHome dashboard to come up...
[09:24:03] INFO: Starting ESPHome dashboard...
2024-11-22 09:24:05,665 INFO Starting dashboard web server on unix socket /var/run/esphome.sock and configuration dir /config/esphome...
[09:24:06] INFO: Starting NGINX...
[09:24:07] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-11-22 12:31:38,112 INFO 200 GET /devices (0.0.0.0) 10.16ms

[Karosm]

while you use it, when it’s getting triggered by PIR…

[kwatt (Kenneth Watt)]

All I can see being added to it is:

2024-11-22 12:31:38,112 INFO 200 GET /devices (0.0.0.0) 10.16ms

[kwatt (Kenneth Watt)]

Ouch, I checked the Logbook and on that single event happening it recoded no less than 35 on/off events for that one sensor.

[Karosm]

I don’t know what is Logbook.
I would like to see your logger log.

I have some doubts about your wiring as well, because if you previously had your sensor configured pulldown: true, there is no way you could get trigger from your sensor while Com is connected to esp32 GND.

Is your wiring like this ? (the count of sensors is not important)

IN1 and 2 are your input pins (Gpio25 …)

[kwatt (Kenneth Watt)]

Yes, that is exactly how it is wired and was for the previous Arduino and Homevision before that.

All PIRs share the same 12V PSU, all share a common ground, only the input of each changes to a seperate pin/terminal.

I am not yet familiar with HA at all, I am learning but it’s a steep curve with a lot going on as I migrate but so long as I get pointed in the right direction, I’ll find stuff. In the core logs I spotted this reported:

Logger: aioesphomeapi.connection
Source: runner.py:189
First occurred: 14:37:25 (1 occurrences)
Last logged: 14:37:25

esphome-web-8733d8 @ 192.168.2.3: Connection error occurred: [Errno 104] Connection reset by peer

I don’t know where else to look for more info.

[Karosm]

@kwatt

Yes, that is exactly how it is wired and was for the previous Arduino and Homevision before that.

All PIRs share the same 12V PSU, all share a common ground, only the input of each changes to a seperate pin/terminal.

So you understand that with pulldown: true the pin is always LOW. Triggered or not. So it’s impossible you got triggers from that pin…

[kwatt (Kenneth Watt)]

I can only report what I see. Even if I don’t completey understand it.

With the code set as above I have a common to ground and the input for the PIR on GPIO 25, I just went and checked that agin, just to be sure and that is exactly how it is wired.

What I don’t get is why it’d see multipe instances then just stop responding.

[Karosm]

You need to observe your runtime log. Do you have Esphome dashboard?

[kwatt (Kenneth Watt)]

No, I don’t seem to only what comes out the box from ESPHome and HA, do you man this:

ESPHome Web Server Dashboard

The current web_server interface is ok for toggling things on and off and reading some sensors, but it’s not looking good nor is it very user friendly. So I created a dashboard, which shows your device data and actions at your regular esphome-device.local:80 - only nicer. And it is a PWA, so each device can be installed on any smart device and accessed via dock or app shortcuts. web_server dashboard [dashboard] No extra components needed, just add in your YAML: web_server: …

[Karosm]

I don’t know that. My setup is standalone.
I mean something like this:

[kwatt (Kenneth Watt)]

I think I found it and the log there says this:

INFO ESPHome 2024.11.1
INFO Reading configuration /config/esphome/esphome-web-8733d8.yaml...
Failed config

binary_sensor.gpio: [source /config/esphome/esphome-web-8733d8.yaml:53]
  platform: gpio
  pin: 
    number: 13
  
  [mode] is an invalid option for [binary_sensor.gpio]. Please check the indentation.
  mode: 
    input: True
    pullup: True
    pulldown: False
  name: Bathroom Ceiling PIR
  device_class: motion

[Karosm]

@kwatt

binary_sensor.gpio:

what is that??

You should have:

binary_sensor:
  - platform: gpio
    pin:
      number: 25
      mode:
        input: true
        pullup: true

[kwatt (Kenneth Watt)]

I can’t find that in the yaml at all, the complete thing is below. I’ll change the other parts of it now.

substitutions:
  name: esphome-web-8733d8
  friendly_name: PIR ESP

esphome:
  name: ${name}
  friendly_name: ${friendly_name}
  min_version: 2024.6.0
  name_add_mac_suffix: false
  project:
    name: esphome.web
    version: dev

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:

# Allow Over-The-Air updates
ota:
- platform: esphome

# Allow provisioning Wi-Fi via serial
improv_serial:

wifi:
  # Set up a wifi access point
  ap: {}

# In combination with the `ap` this allows the user
# to provision wifi credentials to the device via WiFi AP.
captive_portal:

dashboard_import:
  package_import_url: github://esphome/example-configs/esphome-web/esp32.yaml@main
  import_full_config: true

# Sets up Bluetooth LE (Only on ESP32) to allow the user
# to provision wifi credentials to the device.
esp32_improv:
  authorizer: none

# To have a "next url" for improv serial
web_server:

binary_sensor:
  - platform: gpio
    pin: GPIO13
    number: GPIO13
    mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Bathroom Ceiling PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 12
      mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Media Room PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 14
      mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Upstairs Hallway PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 27
      mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Kitchen Ceiling PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 26
      mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Dining Room PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 25
      mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Downstairs Hallway PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 33
      mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Master Bedroom PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 32
      mode: 
        input: true
        pullup: true
        pulldown: false
    name: "Master Bedroom Ensuite PIR"
    device_class: motion

[kwatt (Kenneth Watt)]

Sorry, but I hope this helps as I tried this:

binary_sensor:
  - platform: gpio
    pin: GPIO13
    number: 13
    mode: 
        input: true
        pullup: true
    name: "Bathroom Ceiling PIR"
    device_class: motion

And I get…

INFO ESPHome 2024.11.1
INFO Reading configuration /config/esphome/esphome-web-8733d8.yaml...
Failed config

binary_sensor.gpio: [source /config/esphome/esphome-web-8733d8.yaml:53]
  platform: gpio
  pin: GPIO13
  
  [number] is an invalid option for [binary_sensor.gpio]. Did you mean [name]?
  number: 13
  
  [mode] is an invalid option for [binary_sensor.gpio]. Please check the indentation.
  mode: 
    input: True
    pullup: True
  name: Bathroom Ceiling PIR
  device_class: motion

[Karosm]

it’s not correct yaml…
Copy this:

binary_sensor:
  - platform: gpio
    pin:
      number: 25
      mode:
        input: true
        pullup: true
    name: "Downstairs Hallway PIR"
    device_class: motion

And don’t use Gpio12, it’s strapping pin.

[kwatt (Kenneth Watt)]

Okay.

So now the yaml reads:

binary_sensor:
  - platform: gpio
    pin:
      number: 13
      mode:
        input: true
        pullup: true
    name: "Bathroom Ceiling PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 05
      mode:
        input: true
        pullup: true
    name: "Media Room PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 14
      mode: 
        input: true
        pullup: true
    name: "Upstairs Hallway PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 27
      mode: 
        input: true
        pullup: true
    name: "Kitchen Ceiling PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 26
      mode: 
        input: true
        pullup: true
    name: "Dining Room PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 25
      mode: 
        input: true
        pullup: true
    name: "Downstairs Hallway PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 33
      mode: 
        input: true
        pullup: true
    name: "Master Bedroom PIR"
    device_class: motion

  - platform: gpio
    pin:
      number: 32
      mode: 
        input: true
        pullup: true
    name: "Master Bedroom Ensuite PIR"
    device_class: motion

And when tested I get this which, to me looks good but as I said, I am no expert with no experience with this stuff so can’t say for sure:

INFO ESPHome 2024.11.1
INFO Reading configuration /config/esphome/esphome-web-8733d8.yaml...
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Starting log output from 192.168.2.3 using esphome API
INFO Successfully connected to esphome-web-8733d8 @ 192.168.2.3 in 0.093s
INFO Successful handshake with esphome-web-8733d8 @ 192.168.2.3 in 0.023s
[20:25:18][I][app:100]: ESPHome version 2024.10.3 compiled on Nov 19 2024, 09:22:50
[20:25:18][I][app:102]: Project esphome.web version dev
[20:25:18][C][wifi:600]: WiFi:
[20:25:18][C][wifi:428]:   Local MAC: 3C:E9:0E:87:33:D8
[20:25:18][C][wifi:433]:   SSID: [redacted]
[20:25:18][C][wifi:436]:   IP Address: 192.168.2.3
[20:25:18][C][wifi:440]:   BSSID: [redacted]
[20:25:18][C][wifi:441]:   Hostname: 'esphome-web-8733d8'
[20:25:18][C][wifi:443]:   Signal strength: -30 dB ▂▄▆█
[20:25:18][C][wifi:447]:   Channel: 7
[20:25:18][C][wifi:448]:   Subnet: 255.255.255.0
[20:25:18][C][wifi:449]:   Gateway: 192.168.2.1
[20:25:18][C][wifi:450]:   DNS1: 192.168.2.1
[20:25:18][C][wifi:451]:   DNS2: 0.0.0.0
[20:25:18][C][logger:185]: Logger:
[20:25:18][C][logger:186]:   Level: DEBUG
[20:25:18][C][logger:188]:   Log Baud Rate: 115200
[20:25:18][C][logger:189]:   Hardware UART: UART0
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Bathroom Ceiling PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO13
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Media Room PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO12
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Upstairs Hallway PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO14
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Kitchen Ceiling PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO27
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Dining Room PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO26
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Downstairs Hallway PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO25
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Master Bedroom PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO33
[20:25:18][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Master Bedroom Ensuite PIR'
[20:25:18][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[20:25:18][C][gpio.binary_sensor:016]:   Pin: GPIO32
[20:25:18][C][esp32_ble:391]: ESP32 BLE:
[20:25:18][C][esp32_ble:393]:   MAC address: 3C:E9:0E:87:33:DA
[20:25:18][C][esp32_ble:394]:   IO Capability: none
[20:25:18][C][esp32_ble_server:200]: ESP32 BLE Server:
[20:25:18][C][esp32_improv.component:269]: ESP32 Improv:
[20:25:18][C][captive_portal:089]: Captive Portal:
[20:25:18][C][web_server:153]: Web Server:
[20:25:18][C][web_server:154]:   Address: esphome-web-8733d8.local:80
[20:25:18][C][mdns:116]: mDNS:
[20:25:18][C][mdns:117]:   Hostname: esphome-web-8733d8
[20:25:18][C][esphome.ota:073]: Over-The-Air updates:
[20:25:18][C][esphome.ota:074]:   Address: esphome-web-8733d8.local:3232
[20:25:18][C][esphome.ota:075]:   Version: 2
[20:25:18][C][safe_mode:018]: Safe Mode:
[20:25:18][C][safe_mode:020]:   Boot considered successful after 60 seconds
[20:25:18][C][safe_mode:021]:   Invoke after 10 boot attempts
[20:25:18][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[20:25:18][C][api:140]: API Server:
[20:25:18][C][api:141]:   Address: esphome-web-8733d8.local:6053
[20:25:18][C][api:145]:   Using noise encryption: NO
[20:25:18][C][improv_serial:032]: Improv Serial:

[kwatt (Kenneth Watt)]

The only problem is, i doesn’t seem to register movement.

[Karosm]

You still don’t have runtime log presenting what’s going on while you trigger motion.
Also, for debugging your problem, I suggest to reduce your setup to minimum, both hardware and code. Just Esp and one sensor, no weird configurations.

[kwatt (Kenneth Watt)]

Sorry, I don’t know where to find the runtime log.

I have the yaml file now set to this:

substitutions:
  name: esphome-web-8733d8
  friendly_name: PIR ESP

esphome:
  name: ${name}
  friendly_name: ${friendly_name}
  min_version: 2024.6.0
  name_add_mac_suffix: false
  project:
    name: esphome.web
    version: dev

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:

# Allow Over-The-Air updates
ota:
- platform: esphome

# Allow provisioning Wi-Fi via serial
improv_serial:

wifi:
  # Set up a wifi access point
  ap: {}

# In combination with the `ap` this allows the user
# to provision wifi credentials to the device via WiFi AP.
captive_portal:

dashboard_import:
  package_import_url: github://esphome/example-configs/esphome-web/esp32.yaml@main
  import_full_config: true

# Sets up Bluetooth LE (Only on ESP32) to allow the user
# to provision wifi credentials to the device.
esp32_improv:
  authorizer: none

# To have a "next url" for improv serial
web_server:

binary_sensor:
  - platform: gpio
    pin:
      number: 25
      mode: 
        input: true
        pullup: true
    name: "Downstairs Hallway PIR"
    device_class: motion

On the ESPHome log it gives me this when that’s uploaded:

INFO ESPHome 2024.11.1
INFO Reading configuration /config/esphome/esphome-web-8733d8.yaml...
INFO Starting log output from 192.168.2.3 using esphome API
INFO Successfully connected to esphome-web-8733d8 @ 192.168.2.3 in 0.021s
INFO Successful handshake with esphome-web-8733d8 @ 192.168.2.3 in 0.091s
[21:07:21][I][app:100]: ESPHome version 2024.10.3 compiled on Nov 19 2024, 09:22:50
[21:07:21][I][app:102]: Project esphome.web version dev
[21:07:21][C][wifi:600]: WiFi:
[21:07:21][C][wifi:428]:   Local MAC: 3C:E9:0E:87:33:D8
[21:07:22][C][wifi:433]:   SSID: [redacted]
[21:07:22][C][wifi:436]:   IP Address: 192.168.2.3
[21:07:22][C][wifi:440]:   BSSID: [redacted]
[21:07:22][C][wifi:441]:   Hostname: 'esphome-web-8733d8'
[21:07:22][C][wifi:443]:   Signal strength: -40 dB ▂▄▆█
[21:07:22][C][wifi:447]:   Channel: 7
[21:07:22][C][wifi:448]:   Subnet: 255.255.255.0
[21:07:22][C][wifi:449]:   Gateway: 192.168.2.1
[21:07:22][C][wifi:450]:   DNS1: 192.168.2.1
[21:07:22][C][wifi:451]:   DNS2: 0.0.0.0
[21:07:22][C][logger:185]: Logger:
[21:07:22][C][logger:186]:   Level: DEBUG
[21:07:22][C][logger:188]:   Log Baud Rate: 115200
[21:07:22][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Bathroom Ceiling PIR'
[21:07:22][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[21:07:22][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Upstairs Hallway PIR'
[21:07:22][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[21:07:22][C][gpio.binary_sensor:016]:   Pin: GPIO14
[21:07:22][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Kitchen Ceiling PIR'
[21:07:22][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[21:07:22][C][gpio.binary_sensor:016]:   Pin: GPIO27
[21:07:22][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Dining Room PIR'
[21:07:22][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[21:07:22][C][gpio.binary_sensor:016]:   Pin: GPIO26
[21:07:22][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Downstairs Hallway PIR'
[21:07:22][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[21:07:22][C][gpio.binary_sensor:016]:   Pin: GPIO25
[21:07:22][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Master Bedroom PIR'
[21:07:22][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[21:07:22][C][gpio.binary_sensor:016]:   Pin: GPIO33
[21:07:22][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Master Bedroom Ensuite PIR'
[21:07:22][C][gpio.binary_sensor:015]:   Device Class: 'motion'
[21:07:22][C][gpio.binary_sensor:016]:   Pin: GPIO32
[21:07:22][C][esp32_ble:391]: ESP32 BLE:
[21:07:22][C][esp32_ble:393]:   MAC address: 3C:E9:0E:87:33:DA
[21:07:22][C][esp32_ble:394]:   IO Capability: none
[21:07:22][C][esp32_ble_server:200]: ESP32 BLE Server:
[21:07:22][C][esp32_improv.component:269]: ESP32 Improv:
[21:07:22][C][captive_portal:089]: Captive Portal:
[21:07:22][C][web_server:153]: Web Server:
[21:07:22][C][web_server:154]:   Address: esphome-web-8733d8.local:80
[21:07:22][C][mdns:116]: mDNS:
[21:07:22][C][mdns:117]:   Hostname: esphome-web-8733d8
[21:07:22][C][esphome.ota:073]: Over-The-Air updates:
[21:07:22][C][esphome.ota:074]:   Address: esphome-web-8733d8.local:3232
[21:07:22][C][esphome.ota:075]:   Version: 2
[21:07:22][C][safe_mode:018]: Safe Mode:
[21:07:22][C][safe_mode:020]:   Boot considered successful after 60 seconds
[21:07:22][C][safe_mode:021]:   Invoke after 10 boot attempts
[21:07:22][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[21:07:22][C][api:140]: API Server:
[21:07:22][C][api:141]:   Address: esphome-web-8733d8.local:6053
[21:07:22][C][api:145]:   Using noise encryption: NO
[21:07:22][C][improv_serial:032]: Improv Serial: