Repository navigation
Troubleshooting
Check that the verified RC.1 module is registered once as a JavaScript module resource. Open a fresh browser document after changing its URL. The picker entry is Thermal Intelligence Thermostat · RC. Keep legacy TI resources separate.
Tap the LED to see which observation or restriction needs attention. RC.1 displays an explicitly null VT Off reason or Mode reason as None reported. Missing fields, unknown/unavailable observations, malformed values and real lock/readiness restrictions remain visible. An amber detail warning does not itself change command permissions.
Check the selected entity, connection, provider readiness, advertised capabilities and VT lock scope. Missing readiness cannot enable fallback controls. Lock actions also require a verified administrator and complete provider capabilities; see VT lock control.
They describe different observations: temperature response, temperature slope and thermostat/valve activity. A room can keep warming after its valve closes. A falling room temperature does not establish active HVAC cooling. See Reading the card.
Use the exact module and resource procedure in Installing the release candidate. Retain the previous file and configuration. A frontend rollback cannot undo a provider command.
Use the issue forms with your TI, HA, provider and browser/Companion versions, installation method, reproduction steps and a minimal redacted configuration. Include screenshots only after removing private names and entities.
Report vulnerabilities privately through GitHub security reporting.
Explore our other projects
Humidity Intelligence →