Sometimes one of my GSM/SIM card sensors goes rogue (due to a loose connection that’s complicated to fix, will get round to it…) and publishes extremely frequent state changes. This is both annoying and uses up valuable/expensive data. It also pollutes my HA log db etc.
Is there any way (other than setting lots of timers and spider’s web if,if,if logic) that I can detect a sensor which is sending “too frequent” state changes? I could then
a) disregard the state changes
b) notify myself that the sensor has gone rogue
c) remotely disable it
Thanks, but not sure it will, unless I’m misunderstanding something. Looks like that would be useful if a sensor sends too much bona fide data - in this case it’s when my sensor is sending very frequent updates that I know something’s gone pear shaped.
Something like what @arsaboo is doing here might be the answer, but I’m not sure if I’d need to create lots of extra binary sensors and timers for the sensor which seems excessive - if there’s a simpler way