Any way of modifying reporting of sensor changes which are possibly flooding the event bus

ESPHome
1

I am troubleshooting a problem but at the moment I think I have some SCreek devices flooding home assistant and causing short inturruptions in sensing.

So I did some searching and it points to their device's sensors.

Looking at the logs - every 100-200ms, I have multiple Screek sensors sending the exact same TextSensorStateResponse with key 2896559318 and state "null". These may be flooding my event bus.

The debug logs were just full of a flood of repeat sensor messages.

  • 5 different Screek sensors (f2-d131bc, f2-d169c8, f2-501a28, f2-d143b0, plus l13-4131f0)
  • Each sending every 200-300ms the same "null" text sensor update
  • That's 15-20 updates per second just from these text sensors

The key 2896559318 appears to be a text sensor that Screek firmware uses for something like "LD2410 Debug" or "Radar Raw Data". Even though it reports "null", ESPHome may still be processing it and sends each update to HA.

I don't use ESP Home Builder because I'm not that familiar with ESP Home and I haven't need to. But I installed it and these devices don't show up there. I see my 7 Apollo Automation sensors, but not the SCreek ones.

So I don't know if I have any way to modify the way ESPHome sends messages. Logging is not the issue. I've used my configuration.yaml file to block writes to the logs, but the messages are still being process.

Does anyone have any ideas? I'm using HAOS, 2026-6.

2

Since you bought a product that maybe includes esphome, but doesn't appear to include any information about what they did with it, it is probably best to start with their support:

To be clear, esphome has many ways of limiting the update frequency of sensors. It appears screek has a fairly fast update rate and no obvious way of changing it (but their support might be able to help).

But, I have some sensors that update at a faster rate (magnetometer for gas/water meter) and have never had a problem.

3

Screek Workshop publish the yaml for all their sensors on Github. Maybe have a look there - you may spot the issue and be able to customise your sensor:

That will be the only way you can customise - by overriding the yaml currently compiled onto the device.

4

I am not a tech hacker. I absolutely wouldn't have the skills to do this.

5

You then need to get support from the company that sold you the device that you believe is not working correctly.

Are one way to limit the number/frequency of updates. But, you need to be able to change the YAML config and rebuild and reload the firmware.

But, I am not convinced that is the problem. It could be a contributing factor and causing your system to fall over because it can't handle the load.