From 78f1bb0f92b00651e77e489f60e7818c8624b189 Mon Sep 17 00:00:00 2001 From: Marc Billow Date: Mon, 27 Jul 2026 03:46:55 +0000 Subject: [PATCH] Fix unclosed PROBE_STATUS capability from a bad merge conflict resolution The merge of main into this branch dropped PROBE_STATUS's closing ),\n) and glued issue #74's COOKTOP_MONITORING addition directly onto its entities tuple, leaving an unclosed paren (SyntaxError on import, breaking Pytest and Hassfest CI). Restores the closing parens; no functional change. --- custom_components/localthings/registry/capabilities/range.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/custom_components/localthings/registry/capabilities/range.py b/custom_components/localthings/registry/capabilities/range.py index e7ad0d7..ea77f06 100644 --- a/custom_components/localthings/registry/capabilities/range.py +++ b/custom_components/localthings/registry/capabilities/range.py @@ -189,6 +189,8 @@ PROBE_STATUS = Capability( SensorDesc(key='probe_target_temperature', field='targetTemperature', device_class='temperature', entity_category='diagnostic', unit_fn=lambda rep: normalize_temp_unit(rep.get('temperatureUnit'), '°C')), + ), +) # Some range boards (issue #74's NE63B8411SS) report no /cooktop/status/vs/0 # burner array at all -- their local API only exposes this coarse