It didn’t used to do this. I suspect it started after some update a month or so ago. Not sure when exactly and I’m still early in the troubleshooting.
I have 1 Daikin Skyport integration that provides four “climate” entities for the four indoor units of a mini-split system.
Every hour, on the hour, the whole thing goes “unavailable”. I see it in the history graph of the entities as a very short break in coverage and in the logbook will be a line that reads “became unavailable”. Looking into the logs, I see the same four lines repeated every hour. I turned on DEBUG logging and it provides a bit more context. Every hour, this:
2023-10-05 13:56:47.626 DEBUG (MainThread) [custom_components.daikinskyport] Daikin Skyport tokens expired
2023-10-05 13:56:47.626 DEBUG (MainThread) [custom_components.daikinskyport] Refreshing Daikin Skyport tokens and updating config entry
2023-10-05 13:56:48.353 DEBUG (MainThread) [custom_components.daikinskyport] Daikin Skyport data updated successfully
2023-10-05 13:56:48.353 DEBUG (MainThread) [custom_components.daikinskyport] Update listener: <homeassistant.config_entries.ConfigEntry object at 0x7f83f99216c0>
2023-10-05 13:56:48.354 DEBUG (MainThread) [custom_components.daikinskyport] Unload Entry: <homeassistant.config_entries.ConfigEntry object at 0x7f83f99216c0>
2023-10-05 13:56:48.381 INFO (MainThread) [custom_components.daikinskyport] Daikin Skyport Starting
2023-10-05 13:56:48.381 DEBUG (MainThread) [custom_components.daikinskyport] Using email: <my_email_address>
2023-10-05 13:56:54.232 DEBUG (MainThread) [custom_components.daikinskyport] Daikin Skyport data updated successfully
2023-10-05 13:56:54.232 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.daikinskyport
2023-10-05 13:56:54.232 INFO (MainThread) [homeassistant.components.weather] Setting up weather.daikinskyport
2023-10-05 13:56:54.233 INFO (MainThread) [homeassistant.components.climate] Setting up climate.daikinskyport
Do I have something configured incorrectly? Why would that token be expiring every hour? If that is the right time period for that token, why wouldn’t it update just before it expires so the device doesn’t go unavailable during the refresh? Am I the only one seeing this?