refactor: parallelizing sensor fetches for improved loading performance

[ardevd]

No description provided.

[Copilot]

Pull request overview

This pull request refactors the get_dimo_sensor_data method to parallelize sensor fetches using asyncio.gather, improving loading performance when multiple sensors need to be fetched. The change is part of an optimization effort to reduce initialization time by fetching sensor data concurrently rather than sequentially.

Changes:

• Refactored get_dimo_sensor_data to use parallel execution with asyncio.gather instead of sequential fetches
• Introduced a nested fetch_sensor function to handle individual sensor fetches
• Updated the method's docstring to reflect the parallel execution behavior

Comments suppressed due to low confidence (1)

custom_components/dimo/init.py:190

• When hasattr returns False, the new implementation stores None in self.dimo_data[key], whereas the previous implementation would not store any value for that key. While this behavior change is likely acceptable since entity code handles both missing keys and None values identically (using .get()), it's worth verifying this is intentional. Consider only storing the value if result is not None to maintain the previous behavior more closely.

        for key, value in results:
            self.dimo_data[key] = value

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[redbird-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube