SOLVED: Hmm, trying to use tasmotized sonoff rf bridge

[123 (Taras)]

@fribse

No matching payload found for entity

You are getting these errors because the RF bridge uses one topic to represent the states of many sensors (a bad practice). That means each sensor receives its values from that one topic as well as the values intended for other sensors.

One of your sensors expects to receive these two values:

    payload_on: "12345A"
    payload_off: "12345E"

However, it can also receive values used by the other sensor:

    payload_on: "54321A"
    payload_off: "54321A"

So when it receives the other sensor’s values they don’t match either payload_on or payload_off so Home Assistant reports:

No matching payload found for entity

The solution is to use a template. See ‘Strategy 1’ in the following post:

Sonoff RF Bridge. Strategies for receiving data

Here are two strategies for receiving payloads published by a Sonoff RF Bridge (flashed with Tasmota firmware). Strategy 1: value_template In this strategy, all sensors are subscribed to the same topic published by the RF Bridge. The topic's structure depends on how you defined it when you configured *your* RF Bridge. This example will use `tele/RF_Bridge/RESULT`. Change that to whatever you have set for your Bridge. Because all sensors are subscribed to the same topic, a sensor will receive pa…

Your sensor configuration will look like this example:

- platform: mqtt
  name: 'Entré dør'
  state_topic: 'tele/rfbridge/RESULT'
  value_template: >-
    {% if value_json.RfReceived.Data == '12345A' %}
      {{'ON'}}
    {% elif value_json.RfReceived.Data == '12345E' %}
      {{'OFF'}}
    {% else %}
      {{states('binary_sensor.entre_dor') | upper}}
    {% endif %}
  device_class: door

NOTE
I’m not sure how Home Asssitant converts “Entré dør” into an entity_id so I used binary_sensor.entre_dor. You may need to modify that in the example I provided.