jtricerolph
b6352cf5f7
routes/override.js and ac-control.js's commandAcDevice() got a daikin branch when the driver was built, but scheduler.js's own separate AC_DEVICE_TYPES filter (used for automatic occupied/vacant scheduling at room state transitions) was never updated — so every scheduler tick for a zone with only a daikin device logged "No devices to command" and silently skipped it. Manual control worked fine (different code path), which is why it wasn't caught until a real unit got stuck on after a manual test. Note: this does NOT retroactively fix a unit already stuck from a missed transition — the scheduler only applies at state transitions, not continuously, so a currently-on unit needs a manual off (or the next real transition) to actually turn off. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| Dockerfile | ||
| package.json | ||