While testing the HA server communication I've noticed that the Home Assistant WebSocket connection timeout configuration is used as request timeout. The TCP connection timeout is always using the default 5s. (This is the max time allowed to connect to remote host, including DNS name resolution).
For certain setups this could be an issue and not enough time to successfully connect. It might even be a reason for the reported TLS connection issues.
Tasks:
[x] enhance configuration with a request timeout
[x] the awc::Client setup in new_websocket_client requires an awc::Connector setup for the TCP connection timeout:
While testing the HA server communication I've noticed that the Home Assistant WebSocket connection timeout configuration is used as request timeout. The TCP connection timeout is always using the default 5s. (This is the max time allowed to connect to remote host, including DNS name resolution).
For certain setups this could be an issue and not enough time to successfully connect. It might even be a reason for the reported TLS connection issues.
Tasks:
awc::Client
setup innew_websocket_client
requires anawc::Connector
setup for the TCP connection timeout: