Rolling code 433mhz

Joe3 · March 5, 2022, 4:56pm

Not sure if anyone has noticed. Only the last five bits from most 433mhz rolling code transmitters remotes change. The rest of the packet is unique to the button pressed. What that means is if we mask the last 5 bits we can tell if a button has been pushed. I do this with my microchip projects and it works wonderful… Wondering if it is easy enough for someone super smart with HA can add a mask condition to the trigger match method.

#   unique to the button - rolling
data='0000100010100011100  10010'

Maybe less secure but it is barley secure to begin with on the cheap 433mhz stuff.

  - platform: remote_receiver
    name: Button
    rc_switch_raw:  #           mask this.. x=dont care
      code: '1011000010100011000xxxxx'
      protocol: 1

Joe3 · March 16, 2022, 8:29pm

Wondering if this is too hard to implement?

FredTheFrog · March 18, 2022, 1:16am

This would be a good opportunity to use a lambda expression in C code to mask the value to only the desired bits.

Joe3 · April 11, 2022, 6:37am

int number = 0b0001101001001011; /* 0x1a4b */
int mask =   0b0000111000000000; /* 0x0e00 */
/* &'ed:     0b0000101000000000;    0x0a00 */
int extract = mask & number;     /* 0x0a00 */

if (extract == 0b0000101000000000)
/* or if 0b is not available:
if (extract == 0x0a00 ) */
{
  /* success */
}
else
{
  /* failure */
}

Joe3 · April 14, 2022, 2:16am

No body knows how to do this?

pcwii · May 28, 2022, 1:24am

Does the 433mhz device publish an mqtt packet? If so, pretty sure this could be done with the python_script component.

Joe3 · May 28, 2022, 7:24am

Boy I wish these little 3 dollar sensors and remotes had mqtt packets. thanks.

pcwii · May 28, 2022, 1:11pm

Sorry made some assumptions that you were already retrieving the signal in home assistant with an 433mhz RF Bridge. How did you read the code on the sensor?

Mahko_Mahko · May 29, 2022, 10:29am

Is this thread/post maybe getting closer to what you want?

Basically, if you could publish all codes received into a sensor, then you could do further processing on the sensor?

Edit: More crazy examples…

github.com/esphome/issues

Remote Receiver no longer dumps 'rc_switch' to log when using 'on_rc_switch' automation

opened 04:43PM - 14 Mar 22 UTC

closed 08:03PM - 18 Mar 22 UTC

mmotley999

### The problem I'm running a Sonoff RF bridge and using a remote receiver auto…mation so I can get details for Govee water sensors, such as alert type and battery level. I'm using an "on_rc_switch:" lambda automation to break out the code and, while not the cleanest as I'm still testing, functional (and why I love ESPHome so much). I notice that I no longer see rc_switch message dumps, which makes it difficult to add new devices since I can't see the codes they are sending. However, binary sensors using codes outside the lambda still work fine, so everything co-exists. I'm not sure if this is a bug or by design, and whether there is a way to maintain this functionality when using a remote_receiver automation (e.g. some kind of procedure call in the lambda to output the rc_switch codes?) ### Which version of ESPHome has the issue? 2022.2.6 ### What type of installation are you using? Home Assistant Add-on ### Which version of Home Assistant has the issue? 2022.2.9 ### What platform are you using? ESP8266 ### Board Sonoff RF Bridge ### Component causing the issue remote_receiver ### Example YAML snippet ```yaml remote_receiver: pin: number: GPIO4 dump: rc_switch tolerance: 50% filter: 4us idle: 4ms # buffer_size: 1kb on_rc_switch: then: - lambda: |- // Check for Govee water detectors uint16_t addr, event; uint8_t event_type; uint8_t bytes[8], i; uint64_t shift, copy; shift = x.code << 1; copy = shift; // Break it out for (i=0 ; i < 8 ; i++ ) { bytes[7-i] = copy & 0x00000000000000FF; copy = copy >> 8; }; // Address addr = (bytes[2] << 8) | bytes[3]; // Event type, nibble of byte 4 // 0xC is battery event_type = bytes[4] & 0x0F; // Full event, strip off upper nibble event = (bytes[4] << 8) | bytes[5]; event &= 0x0FFF; // Check for water heater sensor if (addr == 0x4fde) { if (event_type == 0xc) { // Battery update id(leakwhbat).publish_state((float)bytes[5]); } if (event == 0xafa) { // Button Press, reset water leak id(leakwhdetect).publish_state(false); } if (event == 0xbfb) { // Water leak id(leakwhdetect).publish_state(true); } } return; remote_transmitter: pin: GPIO05 carrier_duty_percent: 100% # Battery Level Sensor sensor: - platform: template name: "Water Heater Leak Battery Level" unit_of_measurement: "%" accuracy_decimals: 0 id: leakwhbat # Binary Sensors binary_sensor: # Water leak detected, updated by lambda - platform: template name: "Water Heater Leak Detected" id: leakwhdetect # Test DOOR using contact sensors # These binary sensors still function normally when contact sensor activated - platform: template name: "Test Door" device_class: door id: testdoor - platform: remote_receiver name: "Test Door Open" internal: true on_press: then: - binary_sensor.template.publish: id: testdoor state: ON rc_switch_raw: code: '111100100010000000001010' protocol: 1 filters: - delayed_off: 500ms - platform: remote_receiver name: "Test Door Close" internal: true on_press: then: - binary_sensor.template.publish: id: testdoor state: OFF rc_switch_raw: code: '111100100010000000001110' protocol: 1 filters: - delayed_off: 500ms ``` ### Anything in the logs that might be useful for us? ```txt Messages like this are no longer in the logs: Received RCSwitch Raw: protocol=1 data='01001111110111101111101111111011111110001011111' ``` ### Additional information _No response_

Joe3 · May 29, 2022, 4:45pm

I just have a bunch of sensors around the house that all ready that pump out a protocol 1 or 2 packet and I pick that up with these cheapo RF receivers that work great.

Cheapo

On a ESP8266 running ESPhome with a generic RF receiver.

# Setup Stuff         RF Rec
remote_receiver:
  pin: 4
  dump: rc_switch  #just the packets found
  #: raw      #pulse width data   TOO much on rf just noisey
  tolerance: 50
  filter: 4us
  idle: 4ms

switch:
  - platform: remote_receiver
    name: Button
    rc_switch_raw:  #           mask this.. x=dont care
      code: '1011000010100011000xxxxx'
      protocol: 1

All kinds of cheap devices use send out simple packets.

Harbor

remote

But some of the newer but still cheap Motion sensors added Rolling code chips and the last 4 bits are different 16 times or so.

If those last 4 bits could be ignored we could still use them with our cheapo RF receivers.

Mahko that looks like that will help figure out a cool mask. Thank you!

pcwii thanks for the thoughts

ragde22 · October 11, 2022, 12:35am

How about how to send the rolling codes, I have a couple fan with RF 433Mhz rolling code on each button are 8 codes.
I am not sure if send all the codes at the same time will work.
And how I do that in ESPHome!!

Joe3 · October 11, 2022, 2:40am

That would be a super idea !! I wish I knew how to code it.