[Bug] F2 Ultra UV Entities

[GizmoGoody]

Pre-submission checklist

• I have searched the existing issues and did not find a duplicate.
• I am running the latest release of the integration.
• I have enabled debug logging and captured the relevant lines (instructions below in the Debug logs section).
• My device works correctly in xTool Studio / XCS (rules out a hardware-side problem).

Bug description

It seems the F2 Ultra UV has a bunch of entities which offer no information, consistently Unknown states, or are simply not applicable to a galvo (e.g. Home buttons). Also, the README suggests the camera entity should be available but it is not.

Here is a video during the processing of a job.

Device model

xTool F2 Ultra UV

Firmware version

40.130.021.00.ht2

Integration version

2.3.4

Home Assistant version

2026.5

Steps to reproduce

N/A

Expected behaviour

Multiple

Actual behaviour

Multiple

Debug logs

N/A

Screenshots / additional context

https://youtube.com/shorts/oEOodvp1Nlg?feature=shared

[thecodingdad]

Hi, thanks for the feedback. The integration is currently only fully tested for the S1 (the only model I own), all other models have been added solely through reverse engineering of xTool Studio. So it’s quite possible that some things aren’t displaying correctly yet. I’d really appreciate your help with this. First and foremost, I need debug logs so I can figure out where the problem lies.

[GizmoGoody]

No problem. I assumed they were N/A since I could not reproduce a bug per se, but I enabled them for a couple minutes while the same job as the earlier screenshot is still running. Let me know if you need anything else and thank you!

home-assistant_xtool_2026-05-08T22-26-45.593Z.log

[thecodingdad]

Just shipped v2.4.1. It covers some bugs identified in your log:

• Missing camera entity should now appear.
• Pause / resume / cancel buttons should work now.
• Cover sensor stuck Unknown should be fixed.
• Home XY / Move to origin buttons removed on galvo models (no XY motion path).
• There were further minor issue - all should be fixed.

What's likely still broken

Three things that were visible in the log but couldn't be fully verified without a retest:

1. Entities that still show Unknown. - please report them. Unfortunately, xTool Studio and the firmware do not allow us to determine exactly which endpoints are actually available for each model.
2. Pause / resume / cancel — fix is implemented from the Studio bundle definition but I have no live device to confirm.
3. Peripheral switches (fill light / IR LED / etc.) — same: implemented from the bundle, unverified live.

To help me close out the remaining items

If you can spare another few minutes during a job:

1. Update integraton to v2.4.1 → restart Home Assistant.
2. Enable debug logging.
3. Reload the xTool integration (Settings → Devices & Services → xTool Laser → ⋮ → Reload).
4. List every entity on the F2 Ultra UV device that's still showing Unknown or Unavailable. A screenshot of the device page is fine.
5. Press each of: pause job, resume job, cancel job, fill light on/off, IR LED on/off (if visible), and any switch that previously errored. After each press wait ~3 s.
6. Disable debug logging (it's verbose) and attach the resulting file like before.

The combination of (4) + (6) tells me which capability flags I still need to drop and whether the new endpoint paths actually work on your firmware. Thanks again for the detailed report!

[GizmoGoody]

I did 1-3 (3 is at the device level, not integration ⋮ level).

While the F2 Ultra UV sat in standby, all of these were Unknown

Controls

• Home laser head (grayed out but still present)
• Home XY (grayed out but still present)

Sensors

• Cooling fan
• Exhaust fan
• Task time
• UV fire sensor

Events

• Button
• Error
• Fire warning

Diagnostic

• Air-Assist connected
• Laser module runtime
• Last job time
• Print tool type
• Standby time
• Task ID
• Working mode
• Working time

5

• Pause job - With no job running still, no errors
• Resume job - With no job running still, no errors
• Cancel job - With no job running still, no errors
• Fill light - Failed to perform the action light/turn_on. V2 PUT /v1/peripheral/param returned code 1: action failed, not set_bri|get_bri
• IR LED - No entity matching that name
• Cooling fan - With no job running still, no errors
• Exhaust fan - Worked for On and Off
• Purifier speed - I do not have a purifier, so Failed to perform the action select/select_option. V2 PUT /v1/peripheral/param returned code -2: invalid request
• I DO have an IF2 2.0 but realized it was no longer binded via BT, so I rebinded it and reloaded the integration while debug logging was still enabled, but I still did not see any entities for controlling it.
• Cameras - Close-up and Overview entities now present, but neither provide an image.

6 - Log attached

home-assistant_xtool_2026-05-09T13-42-21.275Z.log

I then started a job using Resume job (maybe clarify this is a start and resume or offer two different entities?), paused it, and then cancelled it. All worked. Log attached

home-assistant_xtool_2026-05-09T13-46-26.608Z.log

Lastly, I started the same job and successfully paused and resumed it. No logs for that one.

[thecodingdad]

Hi @GizmoGoody, thanks for the detailed bug report! I've just shipped v2.5.0.

Resolved (some already in v2.4.x, the rest in v2.5.0):

• IR LED switches added (close-up + global)
• I've added support for almost all accessories (including IF2 2.0), should appear as child device
• Entities with state "Unknown" should be removed (grayed-out). You might have to delete the entities manually.

Still need your help to close out:

1. Lifetime / status sensors stuck Unknown — Laser module runtime, Working time, Standby time, Working mode, Print tool type. Could you check if these populate after a job runs? They're driven by push frames I haven't been able to confirm against F2 Ultra UV — a debug log around a full job would identify the missing push mapping.
2. Events (Button / Error / Fire warning) still Unknown — physical button press should fire event.xtool_..._button. If it doesn't, a debug log over the press tells me the missing push URL. Other events remain unknown until first event appers.
3. IF2 2.0 — did the device/entities appear after the v2.5.0 update? F2 Ultra UV's BT path isn't tested live yet; if entities still don't surface, a debug log around the rebind would help.

The "Resume job" entity is now labeled Start / Resume Job to disambiguate (it's the same wire endpoint regardless — start + resume share the path).

Thanks again for the detailed reports!

[GizmoGoody]

Thanks! Here's the latest after updating to v2.5.0.

• Functional Tests

  • Successful

    • (2) IR LED
    • Fill Light

  • Unsuccessful

    • (2) Camera entities
      • There are now two camera entities for each camera. One entity for each camera indicates idle and the other indicates streaming, but none of the 4 actually stream anything. I checked before and during a job.
    • IF2 2.0
      • I'm not seeing any child devices, but maybe I'm not looking in the right spot? I also reloaded the integration.
      • Log attached from a disconnect and rebind. home-assistant_xtool_2026-05-13T16-56-13.430Z(IF2BTrebind).log

• Entities (all after running a job)

  • Unavailable/Grayed Out (during and after job completion with a device reload). Log attached
    home-assistant_xtool_2026-05-13T19-01-14.732Z(completelongjob).log

    • Controls

      • Cooling fan
      • Home laser head
      • Home XY
      • Purifier speed

    • Sensors

      • Cooling fan
      • UV fire sensor

    • Events

      • Button (log attached) home-assistant_xtool_2026-05-13T19-03-32.357Z(buttonpress).log

    • Configuration

      • Air-Assist gear (cut)
      • Air-assist post-run
      • Purifier auto-continue
      • Purifier check
      • xTool F2 Ultra UV (entity name is number.xtool_f2ultrauv_mxfk007002251107h0184a4_air_assist_gear_engrave)

    • Diagnostic

      • Air-Assist connected
      • Laser module runtime
      • Last button event
      • Last job time
      • Print tool type
      • Standby time
      • Working time
  • Unknown (during and after job completion with a device reload)
    • Sensors
      • Exhaust fan
      • Task time - was Unknown during the job but after completion updated to 7 s...I don't know what that represents. A device reload reset it to Unknown.
    • Events
      • Error
      • Fire warning
    • Configuration
      • IR-light auto-off
      • Sleep timeout
      • Sleep timeout (cover open)

• Questions

  • The F2 Ultra platform does have dual cameras. Does the firmware label them as Overview and Close-up cameras? Unlike my P2, the camera is presented in xTool Studio as a single image. Maybe we'll be able to troubleshoot that more effectively once we get it streaming successsfully.
  • Why are there two IR LED entities? Both seem to activate the same LED along the right side of the chamber.
  • When you say to delete Unknown entities manually, is that just an artifact of this Beta testing, or will future users of the integration also have to do that for Unknown and Inapplicable entities?
  • Are any of the following also available?
    • Currently loaded filename as in the one that would process when the Start job is pressed or the one currently in process?
    • Times (ETC, Remaining, etc.)...Which one would Task time represent once you get it working?