Skip to content
This repository was archived by the owner on May 4, 2026. It is now read-only.

v2.1.0

Choose a tag to compare

View all tags
@BassXT BassXT released this 12 Nov 16:44
· 57 commits to main since this release
2.1.0
ed5d66c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Overview

This release introduces major quality-of-life improvements for easier setup and cleaner device management in Home Assistant.

Configuration via configuration.yaml is no longer required — all xTool devices (P2, F1, M1, Apparel) can now be added directly through the Home Assistant UI (Config Flow).
Each device is now handled as a separate device entity.

All communication logic, polling, and status mapping remain unchanged.

What's New

  • Full UI-based setup (Config Flow) — no YAML configuration required.
  • Multiple device support — each laser appears as its own device.
  • Automatic entity naming based on your chosen name and device_type.
    Example: binary_sensor.laser1_f1_power, sensor.laser1_f1_status.
  • Refactored code structure using the Home Assistant Device Registry.

New: Power Binary Sensor

A new binary sensor (binary_sensor.<name>_<device_type>_power) indicates whether your xTool device is powered on or reachable.

Condition sensor.<name>_<device_type>_status binary_sensor.<name>_<device_type>_power
Device reachable / responding Running, Idle, Done, etc. on
Device offline / unreachable Unavailable off

Breaking Changes

  • The integration no longer uses configuration.yaml.
    Any previous YAML setup will be ignored.
  • Entity IDs will change due to automatic naming.
  • Existing automations and dashboards may need to be updated to reference the new entity IDs.

No Functional Changes

Device communication, polling, and API behavior remain identical.
This update only improves setup, naming, and user experience.

Assets 2
Loading