From 5f6fcb727e60103d90157d67cbed79b20e0e1712 Mon Sep 17 00:00:00 2001 From: Allen Porter Date: Sat, 11 Jun 2022 12:02:52 -0700 Subject: [PATCH] Propose an exception handling criteria for Silver integration quality (#1344) Co-authored-by: Martin Hjelmare Co-authored-by: Teemu R. --- docs/integration_quality_scale_index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/integration_quality_scale_index.md b/docs/integration_quality_scale_index.md index a25ffbdb..5ef38e48 100644 --- a/docs/integration_quality_scale_index.md +++ b/docs/integration_quality_scale_index.md @@ -26,6 +26,7 @@ This integration is able to cope when things go wrong. It will not print any exc - Handles expiration of auth credentials. Refresh if possible or print correct error and fail setup. If based on a config entry, should trigger a new config entry flow to re-authorize. ([docs](config_entries_config_flow_handler.md#reauthentication)) - Handles internet unavailable. Log a warning once when unavailable, log once when reconnected. - Handles device/service unavailable. Log a warning once when unavailable, log once when reconnected. +- Operations like service calls and entity methods (e.g. *Set HVAC Mode*) have proper exception handling. Raise `ValueError` on invalid user input and raise `HomeAssistantError` for other failures such as a problem communicating with a device. - Set `available` property to `False` if appropriate ([docs](core/entity.md#generic-properties)) - Entities have unique ID (if available) ([docs](entity_registry_index.md#unique-id-requirements))