mhansen
[Feature Request] id and channel matcher (strict) mode
Consider adding a "strict" id and channel matcher mode to restrict to only the specific sensors you wish to monitor.
Use Case: I've observed Acurite-Tower sensors occasionally changing the channel they use when they broadcast - even though for instance they are set to channel "A" it shows up as "B" or even "C", leading to extra devices showing up in the metrics that match the same ID. This can lead to an occasional "stuck" metric showing up (showing a static temperature/humidity reading) in Prometheus metrics collection until a restart of the rtl_433_prometheus tool.
If a strict mode that uses both the ID and the channel to determine metrics creation were to be implimented, it would eliminate creating metrics for a device that randomly changes the channel in the transmission and creates new, undesirable metrics to be scraped.
Perhaps something like this as a configuration value? --id_channel_matcher "[device],[id],[channel],[description]" example: --id_channel_matcher "Acurite-Tower,1234,A,Study Balcony"
I see this too sometimes on my network; I guess it's a bitflip somewhere along the way.
On Sun, 14 Jan 2024 at 08:20, prjensen @.***> wrote:
Consider adding a "strict" id and channel matcher mode to restrict to only the specific sensors you wish to monitor.
Use Case: I've observed Acurite-Tower sensors occasionally changing the channel they use when they broadcast - even though for instance they are set to channel "A" it shows up as "B" or even "C", leading to extra devices showing up in the metrics that match the same ID. This can lead to an occasional "stuck" metric showing up (showing a static temperature/humidity reading) in Prometheus metrics collection until a restart of the rtl_433_prometheus tool.
If a strict mode that uses both the ID and the channel to determine metrics creation were to be implimented, it would eliminate creating metrics for a device that randomly changes the channel in the transmission and creates new, undesirable metrics to be scraped.
Perhaps something like this as a configuration value? --id_channel_matcher "[device],[id],[channel],[description]" example: --id_channel_matcher "Acurite-Tower,1234,A,Study Balcony"
— Reply to this email directly, view it on GitHub https://github.com/mhansen/rtl_433_prometheus/issues/27, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZYON5KSLHADDQSHTRJE3YOL3APAVCNFSM6AAAAABBZSRQYGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DANBXHE3TQMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
