#Seeking advice on integrating door densors (Keywords: PGST PB-68 EV1527 RF433 RX470-4 ESP32)

1 messages · Page 1 of 1 (latest)

compact swift
#

Hi all,

I intend to put a door/window sensor on about 30+ doors and windows around the house.
In order not to break the bank, I'm looking at a solution with low-cost PGST PB-68 sensors and would want to collect their signals though strategically placed ESP32s with RX470-4 433MHz superhet receivers.

Is this viable? I've been told to "stay away from RF433". Is there perhaps better solution on the low-cost side?

Do I understand the docs and forum posts correctly, that I can either integrate each sensor directly or through MQTT?
Are there more options? What are the advantages and disadvantages?

Is remote_receiver the right platform for this endeavor? It looks to me to be mainly for remote control devices and doesn't seem to have a filter for EV1527.

Is there any documentation on the codes used by the PB-68 for open/closed, battery status, anti-demolition or perhaps existing code or an existing ready-to-use integration that I've overlooked?

Thanks!

tropic latch
#

The challenge with RF is that sensors are send and forget, so you can't tell if they stop working

#

I'm a fan of Zigbee - Aqara's sensors are typically $10 or less

compact swift
#

@tropic latch Thanks, I will look into Zigbee for that. However, as I have several doors/windows that are used frequently and that are not security critical, I can simply correlate their status changes with human presence to tell whether they are still working. Also, from earlier home automation projects, I still have a number of other RF488 sensors that I wouldn't mind integrating. Getting this current hardware integrated is a starting point.

tropic latch
#

As long as you realise the limits, and problems

compact swift
#

Anyway, I've had some success:

# cf. https://esphome.io/components/remote_receiver.html
# RX470-4 connection cf. https://qiachip.com/products/qiachip-433mhz-superheterodyne-rf-receiver-and-transmitter-module
remote_receiver:
  pin: 
    number: GPIO34 # input-only is sufficient for receiver module
    inverted: true # for this type of receiver module
  # cf. https://community.home-assistant.io/t/decoding-433mhz-buttons/724251/6
  # dump: all
  dump: rc_switch
  tolerance: 75%
  filter: 100us
  idle: 8ms```

PGST PB-68 sensor codes observed as RCSwitch Raw: protocol=6:
  <20 ID-bits of sensor 1>1001 # during tamper-pin depressed > action: close
  <20 ID-bits of sensor 1>1001 # during closed > action: depress tamper-pin 
  <20 ID-bits of sensor 1>1001 # during closed > action: release tamper-pin 
  <20 ID-bits of sensor 1>1001 # during tamper-pin released > action: close
  <20 ID-bits of sensor 1>0110 # during tamper-pin depressed > action: open
  <20 ID-bits of sensor 1>0110 # during tamper-pin released > action: open
  <20 ID-bits of sensor 1>0110 # during open > action: depress tamper-pin 
  <20 ID-bits of sensor 1>0110 # during open > action: release tamper-pin 
  Toggling the tamper-pin merely causes a re-send of the current open/close status. There is no tamper status per se.
  Battery-low still to be observed.

 Another # PGST PB-68 sensor:
   <20 ID-bits of sensor 2>0110 # action: open
   <20 ID-bits of sensor 2>1001 # action: close

I might try to simulate low battery with a potentiometer...

remote_receiver dump stops output after some time (maybe half an hour - I haven't timed it). Is that by design?
torpid geyserBOT