v0.9.0

[3dg1luk43]

[0.9.0] - 2026-01-23

[List of issues (0.9.0)](https://github.com/3dg1luk43/ha_creality_ws/issues?q=is%3Aissue+milestone%3Av0.9.0

Added

• CFS Support (Creality Filament System) (@buzato):
  • Comprehensive Sensors: Added sensors for each CFS box (temperature, humidity) and slot (filament type, color, percentage, active status).
  • Native UI Card: Introduced the Creality CFS Card with a built-in visual editor.
    • Renders tiles for all slots (up to 4 boxes x 4 slots) + external filament.
    • Dynamic UI: Active filament pulses, humidity color coding (Green/Orange/Red).
    • No YAML required: Fully configurable via entity mapping in the UI.
  • New Services: Added request_cfs_info (manual refresh), cfs_load, and cfs_unload for programmatic filament management.
• Safety Features:
  • Confirmation Dialog: Added a "double-check" modal for destructive actions like "Stop Print" to prevent accidental cancellations.

Fixed

• K2 Base Compatibility (@PavelStoyan0v):
  • Chamber Control: Fixed chamber temperature control by implementing a Moonraker fallback for fetching accurate targets when the primary method fails.
  • Data Accuracy: Suppressed erroneous targetBoxTemp:0 values.
  • Threshold Removal: Removed the hardcoded 40°C threshold for chamber heating, allowing for more flexible control.
• go2rtc Custom Configuration: Fixed an issue where custom go2rtc URL and Port settings were ignored.
• Coordinator & Stability:
  • Refactored the central data coordinator for efficient high-frequency WebSocket updates.
  • Resolved merge conflicts and sync issues for reliable state tracking.
• Frontend Assets: Improved resource loading and fixed loading issues for custom card resources.

---

This discussion was created from the release v0.9.0.

[chairstacker]

I installed v0.9.0 yesterday and my camera access went awry - while this might be a Home Assistant issue (I cannot find a go2rtc integration to install or any activity on ports 1984 or 11984 provided by the 'built-in' integration) I'd appreciate it, if the previous camera access could be used as a fallback so that I can upgrade.

Another thing I noticed - in the short period I had v0.9.0 installed - was, that the chamber target temperature was not available; not sure what happened there either.

Fun Fact:
When I originally installed v0.8.0 two weeks ago, the chamber target temperature 'number' was shown, but two days later the integration did not provide it any more, so I disabled/deleted it.

Is this anything you'd want me to raise an issue for?

Edit:
I saw that issue #65 was raised for the camera access between me noticing the problem and writing this comment.