Reuse QuestDB sender

[CM000n]

The problem: The warning occurred because a new QuestDB sender was created and immediately destroyed for each state-changed event. This led to inefficient connection establishment/termination cycles.

The solution: I changed the architecture so that the QuestDB sender is created once when the QuestDB class is started and reused throughout the entire runtime.

Important changes:

1. New _create_sender() method in the QuestDB class:

• Creates a sender once based on the auth settings.
• Supports both authenticated (TLS) and non-authenticated connections.

2. Sender as instance variable:

• The sender is stored as self.sender and reused.
• It is closed properly during shutdown.

3. Simplified IO functions:

• Removal of _insert_row_with_auth and _insert_row_without_auth.
• A single _insert_row() function that uses the provided sender.
• Updated function signatures for better reusability.

4. Improved shutdown handling:

• The sender is closed properly during the Home Assistant stop event.

Result:

• The warning is eliminated because the sender is only created once.
• Better performance by avoiding repeated connection establishment.
• Clean resource management with proper cleanup during shutdown.

The changes follow the best practices outlined in the QuestDB Python Client documentation and should completely eliminate the warning in Home Assistant logs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New 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 Cloud