You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that the account and device works in the Comfort Cloud App.
This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
This issue is not a duplicate issue of currently previous issues..
What version of Home Assistant Core?
core-2025.1.3
Describe the issue
This might be related to the previous preset bug, but not entirely since the symptoms differ slightly.
The problem is that I can't exit the heat_8_15 preset after it's been active for some time (hours-days). If I try changing preset back immediately after enabling heat_8_15 it works, but every other day I discover that it's stuck in this mode. (I have an automation that switches preset between heat_8_15 and none-preset, as well as set temperature, since I'm on hourly energy rate)
Exiting the preset back to normal (none) isn't working neither through the climate card nor programatically through automations. In automations, I've tried both:
- device_id: xxxx domain: climate entity_id: xxxx type: set_preset_mode preset_mode: none
and
- action: climate.set_preset_mode metadata: {} data: preset_mode: none target: device_id: xxxx
I've seen the following error thrown in the logs intermittently, "Error in get_status Expected status code '200' but received '500' Response body: {"code":5001,"message":"DB system error due to db system"}"
A workaround is to toggle the unit off-on, then the preset change works again. But I feel like that increases wear on the unit. Rebooting HA doesn't have any effect.
Error/Debug Logs
I don't know how related this is:
File "/usr/local/lib/python3.13/site-packages/aio_panasonic_comfort_cloud/panasonicsession.py", line 145, in execute_get
File "/usr/local/lib/python3.13/site-packages/aio_panasonic_comfort_cloud/helpers.py", line 32, in check_response
aio_panasonic_comfort_cloud.exceptions.ResponseError: (get_status: Expected status code 200, received: 502: {"message": "Internal server error"}
2025-01-21 09:19:06.618 ERROR (MainThread) [aio_panasonic_comfort_cloud.helpers] Error in get_status
2025-01-21 09:19:06.619 WARNING (MainThread) [aio_panasonic_comfort_cloud.apiclient] Failed to get live status for device CS-HZ25ZKE+E098812651 switching to cached data.
2025-01-21 09:33:37.257 ERROR (MainThread) [aio_panasonic_comfort_cloud.helpers] Error in get_status
2025-01-21 09:33:37.257 WARNING (MainThread) [aio_panasonic_comfort_cloud.apiclient] Failed to get live status for device CS-HZ25ZKE+E098812651 switching to cached data.
The text was updated successfully, but these errors were encountered:
Checklist
What version of Home Assistant Core?
core-2025.1.3
Describe the issue
This might be related to the previous preset bug, but not entirely since the symptoms differ slightly.
The problem is that I can't exit the heat_8_15 preset after it's been active for some time (hours-days). If I try changing preset back immediately after enabling heat_8_15 it works, but every other day I discover that it's stuck in this mode. (I have an automation that switches preset between heat_8_15 and none-preset, as well as set temperature, since I'm on hourly energy rate)
Exiting the preset back to normal (none) isn't working neither through the climate card nor programatically through automations. In automations, I've tried both:
- device_id: xxxx domain: climate entity_id: xxxx type: set_preset_mode preset_mode: none
and
- action: climate.set_preset_mode metadata: {} data: preset_mode: none target: device_id: xxxx
I've seen the following error thrown in the logs intermittently, "Error in get_status Expected status code '200' but received '500' Response body: {"code":5001,"message":"DB system error due to db system"}"
A workaround is to toggle the unit off-on, then the preset change works again. But I feel like that increases wear on the unit. Rebooting HA doesn't have any effect.
Error/Debug Logs
The text was updated successfully, but these errors were encountered: