Sonoff RF bridge - getting bombarded with No matching payload found for entity warnings

[piyush (Piyush Paliwal)]

Hi, I have Sonoff RF Bridge running tasmota and got a few PIR motion sensors and RF door sensors. These sensors are talking to the bridge and the bridge then relays the messages via MQTT to HA.

Everything is working fine, the sensors show proper data, they work as expected, however I am getting constantly bombarded every few seconds with the message in logs that says

No matching payload found for entity: Bathroom Motion with state_topic: tele/RF_Bridge/RESULT

Can you please help me identify what the problem is here and why are my logs flooded. Here is a screenshot of my logs

[mblaz (Mike)]

Hi. I am having the same problem after upgrading to version 87.1 from 86. Have you managed to find a solution? Thanks

[Silicon_Avatar]

There was a change to the code that triggered this warning back on Jan 20th 2018.

Mqtt.py log warning "No matching payload found for entity"

After upgrading to .63 from .58 I have warnings in the log file every time HASS gets an MQTT message seemingly complaining about no matching payload, even though the message payload matches the definitions in the binary sensor. Log messages: 2018-02-11 14:35:33 WARNING (MainThread) [homeassistant.components.binary_sensor.mqtt] No matching payload found for entity: sensor7 with state_topic: unosensor 2018-02-11 14:35:33 WARNING (MainThread) [homeassistant.components.binary_sensor.mqtt] No matc…

[Geoff571]

I’m facing the same issue.

I have a Sonoff Bridge that sends telemetry messages where the ‘data’ value is the only thing that differs for across multiple PIRs. All the sensors that are monitoring for the telemetry messages spit out the warning as it doesn’t match what they’re checking for.

[HFsi]

I found this, anyone tried?

Mqtt.py log warning "No matching payload found for entity"

I offer another solution to prevent the “No matching payload” message from appearing. For an MQTT Binary sensor, the default for payload_on is ON and for payload_off it’s OFF (i.e. uppercase). On the other hand, the state of a binary_sensor can either be on or off (i.e. lowercase). Keeping this important distinction in mind, we can use it to construct a value_template that ensures the payload always matches something and never nothing. This example assumes Data=2C8D0A indicates the door is ope…