From 97a32620153d1bae6f87dff1ff1ae99416d4b034 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ab=C3=ADlio=20Costa?= Date: Tue, 25 Mar 2025 16:26:10 +0000 Subject: [PATCH] Remove info block from IQS parallel-updates page (#2621) --- docs/core/integration-quality-scale/rules/parallel-updates.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/core/integration-quality-scale/rules/parallel-updates.md b/docs/core/integration-quality-scale/rules/parallel-updates.md index d089effd..56aa5908 100644 --- a/docs/core/integration-quality-scale/rules/parallel-updates.md +++ b/docs/core/integration-quality-scale/rules/parallel-updates.md @@ -29,11 +29,11 @@ class MySensor(SensorEntity): ... ``` -:::info +### When using a coordinator + When using a coordinator, you are already centralizing the data updates. This means you can set `PARALLEL_UPDATES = 0` for read-only platforms (`binary_sensor`, `sensor`, `device_tracker`, `event`) and only the action calls will be relevant to consider for setting an appropriate number of parallel updates. -::: `sensor.py` ```python {1,2} showLineNumbers