Filter 433 commands so that not all are published to MQTT.

[wimpie007]

I get a lot of 'rubbisch' 433 commands on my gateway. Polution you might call it. All these events are published to MQTT, wich leads to a lot of activity in my nodered/ HA-automations wich actually do nothing. Also, for this reason, HA-autodiscovery is unusable: i used it a week, and got HUNDREDS of unused switches in HA.

Describe the solution you'd like a filter-mechanism. (whitelist for example protocol-length(s). 24 would - in my case - work in almost all cases)

Describe alternatives you've considered dirty-hack the code myself. :) You don't like that!:)

[1technophile]

Indeed we could replicate the mechanism used for white & black list management of BLE devices

[jumika]

+1 for this. My mqtt boker is flooded with all the unknown 433mhz device signals.