v1.2.4
Security hardening
Following a full security review, one minor issue was identified and fixed:
- API client: removed
content_type=Nonefrom JSON parsing — the API
response content-type is now properly validated, preventing the parser
from silently accepting malformed or unexpected responses.
Security review summary
| Check | Result |
|---|---|
| Hardcoded secrets or API keys | ✅ None |
| Command / template injection | ✅ None |
| Config flow input validation | ✅ Validated |
| Entity ID sanitization | ✅ Safe |
| Sensitive data in logs | ✅ Never logged |
| External dependencies | ✅ None (HA built-in only) |
| HTTPS enforced | ✅ |
This is a stable release
The integration has been thoroughly tested and reviewed.
All core features are working reliably.