[gdt]

Version: 26.10.16.1

What does this implement/fix?

(Do you really want the instructions/comments to remain?)

Many sensors report faster than one minute. If you have Home Assistant and a single AIR-1, that's probably fine. With lots of sensors, the database grows large. The underlying reality just doesn't change that fast, and I believe that almost all people would not find faster-than-1m to be beneficial.

This change is technically breaking, because someone could be relying on it, but it is a bugfix for everyone who does not want such rapid reports and has a big database. But the frequencies are not documented, so arguably it is not breaking.

20261025: I just force-pushed an amended commit that also sets the Predicted entities to 60s update rate.

Types of changes

• Bugfix (fixed change that fixes an issue)
• New feature (thanks!)
• Breaking change (repair/feature that breaks existing functionality)
• Dependency Update - Does not publish
• Other - Does not publish
• Website of github readme file update - Does not publish
• Github workflows - Does not publish

Checklist / Checklijst:

• The code change has been tested and works locally
• The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

• Added/updated documentation for the web page

Summary by CodeRabbit

• Updates
  • The DPS310, SEN55, and four particulate matter readings now refresh every 60 seconds. Previously, the DPS310 refreshed every 30 seconds, while the SEN55 and particulate matter readings refreshed every 10 seconds.
  • Predicted room temperature and humidity readings now refresh every 60 seconds instead of every 10 seconds. This changes how often updated sensor values become available in the integration.

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 339cd1a8-ca91-4aaf-ac04-c58734abc465

Commits

Reviewing files that changed from the base of the PR and between 299d39b and 107906b.

Files selected for processing: 2

• Integrations/ESPHome/Core.yaml
• Integrations/ESPHome/Predicted_Room.yaml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

Walkthrough

The ESPHome configuration sets 60-second update intervals for the DPS310, SEN55, four particulate-matter template sensors, and predicted room temperature and humidity sensors.

Changes

Sensor Update Intervals

Layer / File(s)	Summary
Set core sensor update intervals Integrations/ESPHome/Core.yaml	The DPS310 interval changes from 30 to 60 seconds. The SEN55 and four particulate-matter template sensor intervals change from 10 to 60 seconds.
Set predicted-room update intervals Integrations/ESPHome/Predicted_Room.yaml	The predicted room temperature and humidity sensor intervals change from 10 to 60 seconds. Their calculation and validation logic is unchanged.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related PRs

• ApolloAutomation/AIR-1#135: Adds the predicted room sensors that use SEN55 and DPS310 readings. This change updates the intervals for those sensors and their source sensors.

Suggested reviewers: trevorschirmer, bharvey88

Merge Risk: Minimal · up to 10790

The interval changes are consistent with the PR’s stated database-growth reduction goal and are ready to merge.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: increasing sensor update intervals from 10 or 30 seconds to 60 seconds.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the sensor pace,
Sixty seconds mark each place.
Air readings wait, then start anew,
Room predictions follow too.
The rabbit hops and checks the view.}

_{Comment @coderabbitai help to get the list of available commands.}

[gdt]

I'm now running beta plus this, plus two unrelated fixes, and it's working fine.