gndean / home-assistant-hypervolt-charger

Home Assistant integration for Hypervolt EV charger
47 stars 3 forks source link

Updating state for select.hypervolt_charge_mode took 0.942 seconds. #26

Closed RedNo7 closed 1 year ago

RedNo7 commented 1 year ago

Hi,

I had this in my logs this morning:

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:742 
First occurred: 01:32:05 (1 occurrences) 
Last logged: 01:32:05

Updating state for select.hypervolt_charge_mode (<class 'custom_components.hypervolt_charger.select.ChargeModeSelect'>) took 0.942 seconds. Please report it to the custom integration author.

Hypervolt warnings happen relatively often, but this one asked me to report it.

I also had these in the logs:

2023-07-29 20:35:01.406 WARNING (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket sync, Task-11263, iterator exited. Socket closed, code: 1000, reason: Bye
2023-07-29 20:35:01.415 WARNING (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket session/in-progress, Task-11264, iterator exited. Socket closed, code: 1000, reason: Bye
2023-07-29 20:35:06.639 WARNING (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket session/in-progress, Task-11264, iterator exited. Socket closed, code: 1000, reason: Bye
2023-07-29 20:35:07.625 WARNING (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket sync, Task-11263, iterator exited. Socket closed, code: 1000, reason: Bye
2023-07-29 20:35:14.853 WARNING (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket session/in-progress, Task-11264, iterator exited. Socket closed, code: 1000, reason: Bye
2023-07-29 20:35:17.835 WARNING (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket sync, Task-11263, iterator exited. Socket closed, code: 1000, reason: Bye
2023-07-29 20:35:28.064 WARNING (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket session/in-progress, Task-11264, iterator exited. Socket closed, code: 1000, reason: Bye
gndean commented 1 year ago

Thanks for reporting! I'm not sure there's anything I can do about the "Updating state" message. If it's not occurring regularly, I wouldn't worry about it.

Regarding the Socket and iterator exited messages, this is due to the connection to the HV APIs being closed. The integration will try and reconnect with a few seconds after. So long as you find your integration working most of time, this may have just been a transient condition.