v0.3.1

Fixed

• Suggested the compatibility entity ID suffix job_z_thickness for the existing internal job_z_thick layer-height sensor key.
• Added the missing local brand logo file next to the existing local brand icon for Home Assistant 2026.3 and newer.
• Rebuilt the bundled dashboard card so its visible console version matches the integration release.

Notes

• Existing installations can use the anycubic_ha_integration.migrate_entity_ids service to rename an existing job_z_thick entity to the compatible job_z_thickness entity ID after testing with dry_run: true.
• HACS can only offer updates automatically when the integration was installed as a HACS custom repository. Manual installations still need manual replacement.
• HACS may still show a generic placeholder icon in its downloads list until HACS itself switches that view to Home Assistant's local brands proxy for custom integrations.

v0.3.1-beta.1

Beta test release for issue #6 follow-up.

Changes:

• Suggests the compatible entity ID suffix job_z_thickness for the existing internal job_z_thick layer-height sensor key.
• Adds the missing local Home Assistant brand logo.png next to brand/icon.png.
• Clarifies HACS update behavior, manual updates, and entity-ID migration guidance in the README.

Checks:

• python scripts/sync_version.py --check
• python scripts/check_private_data.py
• python scripts/check_release_version.py
• python -m compileall -q custom_components\anycubic_ha_integration scripts
• npm run build
• Release Gate: https://github.com/ljschmitt/hass-anycubic_cloud_v3/actions/runs/28495454957

v0.3.0

Stable release for the tested 0.3.0 beta line.\n\nHighlights:\n- Adds the native Home Assistant light entity for Anycubic camera light control.\n- Fixes Kobra X camera-light startup behavior by using the Slicer/MQTT-confirmed command type.\n- Adds the side view camera panel with manual stream start, zoom, fullscreen, and optional per-printer HA camera mappings.\n- Adds cautious first-open auto-loading for local, USB, and cloud file-list tabs.\n- Adds local/USB file print preparation from the panel.\n- Stabilizes English entity IDs and adds the entity migration service for older localized IDs.\n- Improves Kobra X ACE/material handling and reduces known MQTT warning noise.\n- Adds release safety checks and starts CHANGELOG.md.\n\nRelease Gate: https://github.com/ljschmitt/hass-anycubic_cloud_v3/actions/runs/28494823902

v0.3.0-beta.15

Beta pre-release for testing the Kobra X camera-light startup behavior.\n\n- Sets the initial Kobra X camera-light command type to the Anycubic value observed from Slicer/MQTT, so Home Assistant no longer needs a prior Slicer light toggle after restart.\n- Keeps the Anycubic Cloud panel version synchronized with the release.\n- Release Gate: https://github.com/ljschmitt/hass-anycubic_cloud_v3/actions/runs/28493977155

v0.3.0-beta.14

Beta diagnostic release for Anycubic camera-light troubleshooting.\n\nAdds debug logging for outgoing GET_LIGHT_STATUS and SET_LIGHT_STATUS orders plus MQTT light query/control responses and failures. The logs intentionally avoid printer IDs, tokens, topics, URLs, and other personal data.\n\nAlso rebuilds the frontend panel bundle so the displayed panel version matches v0.3.0-beta.14.

0.3.0-beta.9

Beta release for testing the cleaned entity naming behavior.

Changes:

• Removes frontend fallbacks for old localized/German entity IDs so the integration, panel, and card consistently use stable English technical entity IDs.
• Keeps German UI/documentation text in translations/docs, while Home Assistant entity names remain English to avoid localized entity-ID drift.
• Updates the README guidance for entity naming and migration behavior.
• Rebuilds the Home Assistant panel and card bundles for 0.3.0-beta.9.

Validation:

• Version files synchronized with scripts/sync_version.py --check.
• Frontend type check passed.
• Panel and card quick builds passed.
• Private-data scan passed.
• Translation entity blocks verified between English and German.

v0.3.0-beta.8

Beta test release for the native Anycubic camera light entity.\n\n- Uses the camera/chamber light type instead of the extruder light type for the native light entity.\n- Consumes failed Anycubic light reports without logging them as unknown MQTT updates.\n- Keeps Home Assistant light metadata as ONOFF and includes rebuilt frontend bundles.\n- No personal Home Assistant, printer, token, URL, or entity-specific data is included.

v0.3.0-beta.4

Beta release for testing the native Anycubic camera light entity.

Changes:

• Adds a native Home Assistant light entity for the Anycubic camera light on printers with camera/video or official light support.
• Uses Anycubic Cloud/MQTT light status and control commands.
• Keeps the native printer camera light separate from the optional dashboard-card lightEntityId.
• Adds release safety checks for version synchronization, private local data, branch strategy, and tag/release collisions.
• Documents beta/pre-release handling and the beta branch workflow.
• Removes direct URLs from Home Assistant translation strings so hassfest validation can pass.
• Fixes camera-session typing and aligns CI formatting so the beta branch can pass validation.

Testing notes:

• This is a beta/pre-release. Please install deliberately for testing.
• After installing, restart Home Assistant or reload the integration so the new light platform can be loaded.
• Do not post tokens, private IPs, printer IDs, serial numbers, or personal Home Assistant entity mappings in issue reports.

Note: earlier beta tags were withdrawn after CI exposed validation issues before this beta was finalized.

v0.3.0-beta.13

Beta fix: rebuilds the Anycubic Cloud frontend panel bundle so the version displayed in the panel matches the installed integration release.\n\nThis keeps the beta.12 behavior changes and only corrects the published panel asset/version mismatch.

v0.3.0-beta.12

Beta log cleanup for Anycubic MQTT reports.\n\n- Handles Kobra X print progress updates that do not include temperature fields.\n- Consumes known aux_fan_speed_pct and z_comp settings so they no longer create unhandled-data warnings.\n- Treats known video initSuccess and buried telemetry reports as expected MQTT noise instead of errors.\n\nThis is a pre-release for testing before a stable release.