would it be possible for vt to recover from central boiler being offline?

[doubledrat]

Today my nest boiler control was offline for a few minutes. During that time, vt tried to turn up the heating g and failed, so the heating stayed off for the rest of the day.

Would it be possible for vt to realise the command to start or stop the boiler has failed and therefore have it try again on next cycle?

Here's the log entries -

because regulation_period (0) is not exceeded
2025-01-14 15:41:09.726 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall climate.set_temperature (c:01JHJQKJKZWEX9A2XZG1YQKGQ9): temperature=24.5, entity_id=['climate.hallway']>
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/google_nest_sdm/auth.py", line 201, in _raise_for_status
    resp.raise_for_status()
    ~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client_reqrep.py", line 1161, in raise_for_status
    raise ClientResponseError(
    ...<5 lines>...
    )
aiohttp.client_exceptions.ClientResponseError: 400, message='Bad Request', url='https://smartdevicemanagement.googleapis.com/v1/enterprises/f7d74bd7-ab91-4711-b6d7-6082f7ed596e/devices/AVPHwEuXjP9dlt6PVZOgVLYnjjNbu5KXQxNeo6rOCS3g2Lr-qxSMwX15PiJqzF3SHGueR1ju8kvQvJK_TifZAaWUXugWBA:executeCommand'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/nest/climate.py", line 300, in async_set_temperature
    await trait.set_heat(temp)
  File "/usr/local/lib/python3.13/site-packages/google_nest_sdm/thermostat_traits.py", line 111, in set_heat
    return await self.cmd.execute(data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/google_nest_sdm/traits.py", line 55, in execute
    return await self._auth.post(f"{self._device_id}:executeCommand", json=data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/google_nest_sdm/auth.py", line 170, in post
    return await AbstractAuth._raise_for_status(response)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/google_nest_sdm/auth.py", line 212, in _raise_for_status
    raise ApiException(error_message) from err
google_nest_sdm.exceptions.ApiException: Bad Request response from API (400): FAILED_PRECONDITION (400): Device is offline.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2815, in _run_service_call_catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 2838, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1006, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1078, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 954, in async_service_temperature_set
    await entity.async_set_temperature(**kwargs)
  File "/usr/src/homeassistant/homeassistant/components/nest/climate.py", line 302, in async_set_temperature
    raise HomeAssistantError(
        f"Error setting {self.entity_id} temperature to {kwargs}: {err}"
    ) from err
homeassistant.exceptions.HomeAssistantError: Error setting climate.hallway temperature to {'temperature': 24.5, 'entity_id': ['climate.hallway']}: Bad Request response from API (400): FAILED_PRECONDITION (400): Device is offline.
2025-01-14 15:41:16.777 INFO (MainThread) [custom_components.versatile_thermostat.thermostat_climate] VersatileThermostat-VT Bedroom - Underlying climate climate.trv_bedroom_east have changed. new_hvac_mode is heat (vs heat), new_hvac_action=heating (vs idle), new_target_temp=16.0 (vs 16.0), new_fan_mode=None (vs None)
2025-01-14 15:41:16.778 INFO (MainThread) [custom_components.versatile_thermostat.thermostat_climate] VersatileThermostat-VT Bedroom - underlying just switch ON. Set power and energy start date 2025-01-14T15:41:16.777324+00:00
2025-01-14 15:41:32.772 INFO (Thread-13 (_run)) [google.api_core.bidi] Re-established stream
2025-01-14 15:44:41.878 DEBUG (MainThread) [google_nest_sdm.event] EventMessage raw_data={'eventId': 'cc25b5f6-f90d-40f1-bb87-adfcf84c2516', 'timestamp': '2025-01-14T15:44:39.742Z', 'resourceUpdate': {'name': 'enterprises/f7d74bd7-ab91-4711-b6d7-6082f7ed596e/devices/AVPHwEuXjP9dlt6PVZOgVLYnjjNbu5KXQxNeo6rOCS3g2Lr-qxSMwX15PiJqzF3SHGueR1ju8kvQvJK_TifZAaWUXugWBA', 'traits': {'sdm.devices.traits.Connectivity': {'status': 'ONLINE'}}}, 'userId': 'AVPHwEtDraAOoBu1BtxBK8y1cMrCs-mXRaXAMwL76XBG', 'resourceGroup': ['enterprises/f7d74bd7-ab91-4711-b6d7-6082f7ed596e/devices/AVPHwEuXjP9dlt6PVZOgVLYnjjNbu5KXQxNeo6rOCS3g2Lr-qxSMwX15PiJqzF3SHGueR1ju8kvQvJK_TifZAaWUXugWBA']}
2025-01-14 15:44:41.878 DEBUG (MainThread) [google_nest_sdm.device] Processing update cc25b5f6-f90d-40f1-bb87-adfcf84c2516 @ 2025-01-14 15:44:39.742000+00:00
2025-01-14 15:44:41.878 DEBUG (MainThread) [google_nest_sdm.device] Trait update {'sdm.devices.traits.Connectivity': {'status': 'ONLINE'}, 'name': 'enterprises/f7d74bd7-ab91-4711-b6d7-6082f7ed596e/devices/AVPHwEuXjP9dlt6PVZOgVLYnjjNbu5KXQxNeo6rOCS3g2Lr-qxSMwX15PiJqzF3SHGueR1ju8kvQvJK_TifZAaWUXugWBA'}

[jmcollin78]

Hello,

If you have Scheduler, the next scheduler command will do the trick for you. When it changes let's say the preset, then a new command is sent to the underlying device.

In over_switch there is a keep-alive feature which does this but not for over_climate.
Maybe it is possible to catch the Unavailable state and catch when the underlying comes back to life. I should have a look.

[doubledrat]

I do have a scheduler, but worst case scenario I could have the heating running all night in comfort mode

[jmcollin78]

Hello, transformed into a Feature request to listen the unknown -> known transition and resend the state.
You can do it manually with a automation if it is frequent:

1. trigger : transition from unknown,
2. action: turn-off Vthrem, wait 5 sec, turn-on Vtherm.

VTherm should then resend the last state to the underlying.

[doubledrat]

thanks :). I've done an automation to monitor it. To see how often it happens

…

On Wed, 15 Jan 2025 at 15:43, Jean-Marc Collin ***@***.***> wrote: Hello, transformed into a Feature request to listen the unknown -> known transition and resend the state. You can do it manually with a automation if it is frequent: 1. trigger : transition from unknown, 2. action: turn-off Vthrem, wait 5 sec, turn-on Vtherm. VTherm should then resend the last state to the underlying. — Reply to this email directly, view it on GitHub <#824 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZMGBOZA7WCYK4SSPKXOZT2KZ623AVCNFSM6AAAAABVF4S37KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBUGQ2TSMQ> . You are receiving this because you authored the thread.Message ID: <jmcollin78/versatile_thermostat/repo-discussions/824/comments/11844592@ github.com>