esphome / esphome/feature-requests

More general custom RC protocol for remote transmitter

Open
#1,240 2 comments 0 reactions 0 assignees View on GitHub
component: remote_transmitter
Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**

Remote transmitter rc protocol should allow more than 2 values for sync and other field lists.

**Please describe your use case for this integration and alternatives you've tried:**

I am trying to integrate a BF-301 controlled shade system and it requires a protocol described here:
[BF-301 protocol](https://github.com/akirjavainen/markisol/blob/master/Markisol.ino)

I could use the raw transmit option, but this is tedious and the custom RC protocol would be sufficient and more efficient if I could better customize the sync, one, and zero fields.

**Additional context**

Contributor guide

No contributing guide indexed for this repository

Research direction

Begin with the linked Markisol.ino BF-301 protocol and list the required sync, one, and zero values, then compare them with the existing custom RC protocol behavior. Done means supporting more than two values for these fields so the BF-301 shade protocol can be represented without using raw transmit.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.