[Bug] M1 not Connectable

[Chellux]

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

hi, my M1 cant connect witzh that addon . firmware is 40.18.026.00.ht3. HA is the newest version.

it dont auto detects, and when i try thru IP, it dont works

Das Gerät wurde erkannt, aber der Protokoll-Handshake ist fehlgeschlagen. Möglicherweise ist das Gerät belegt (XCS / xTool Studio offen) oder die Firmware-Version wird nicht unterstützt.

Device model

xTool M1

Firmware version

40.18.026.00.ht3

Integration version

2.5.4

Home Assistant version

2026.5.1

Steps to reproduce

cant add

Expected behaviour

can add

Actual behaviour

cant add

Debug logs

no logs

Screenshots / additional context

No response

[thecodingdad]

Hi @Chellux,

thanks for the report! Tthe integration only had the V1-firmware M1 model registered. Your firmware 40.18.026.00.ht3 is probbably on the V2 communication framework.

I've added the XTOOL_M1_WSV2 model entry in v2.5.5. If it still does not work, please add debug logs:

1. Enable Debug Logging
   If you have (another) device added, just got to:
   Settings → Devices & Services → xTool Laser → click the three-dot menu → Enable debug logging

   If not, you have to enable it with an action call:

   action: logger.set_level
     data:
       custom_components.xtool: debug    # use 'warning' to disable debug logs afterwards

2. Try to add your device (auto-discovery or manual by IP)

3. Disable Debug Logging

4. Go to Settings → System → Logs → 3-dot menu → show raw logs and copy relevent logs (you can filter for "xtool")

[Chellux]

2026-05-16 21:39:33.872 DEBUG (MainThread) [custom_components.xtool.protocols.rest.protocol] REST GET JSON http://192.168.178.143:8080/device/machineInfo failed: Expecting value: line 1 column 1 (char 0)
2026-05-16 21:39:33.872 DEBUG (MainThread) [custom_components.xtool.protocols.rest.protocol] REST /device/machineInfo raw response: None
2026-05-16 21:39:33.963 DEBUG (MainThread) [custom_components.xtool.protocols] Manual validation against 192.168.178.143 as DT001/V1 rejected: device info is empty (likely wrong protocol_version)

[Chellux]

2026-05-16 21:38:57.155 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module with args ('custom_components.xtool.config_flow',) inside the event loop by integration 'config' at homeassistant/components/config/config_entries.py, line 195: return await super()._post_impl(request, data) (offender: /usr/src/homeassistant/homeassistant/loader.py, line 1313: return importlib.import_module(f"{self.pkg_path}.{platform_name}")), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+config%22
2026-05-16 21:38:57.281 DEBUG (MainThread) [custom_components.xtool.discovery] V2 probe target=255.255.255.255 broadcast=True rx_sockets=4 request_id=2221463562
2026-05-16 21:38:57.292 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.295 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.298 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.302 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.305 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('172.30.32.1', 5353) undecodable (192 bytes)
2026-05-16 21:38:57.570 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.572 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.575 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.575 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.575 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('172.30.32.1', 5353) undecodable (192 bytes)
2026-05-16 21:38:57.879 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.879 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.879 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.879 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 53642) undecodable (192 bytes)
2026-05-16 21:38:57.884 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('172.30.32.1', 5353) undecodable (192 bytes)
2026-05-16 21:39:10.010 DEBUG (MainThread) [custom_components.xtool.discovery] V2 probe target=192.168.178.143 broadcast=False rx_sockets=4 request_id=951597111
2026-05-16 21:39:13.013 DEBUG (MainThread) [custom_components.xtool.protocols] No UDP reply from 192.168.178.143 — cannot identify device
2026-05-16 21:39:21.365 DEBUG (MainThread) [custom_components.xtool.protocols.ws_v2.protocol] V2 connecting to wss://192.168.178.143:28900/websocket?id=13fa451a-0cb7-47c1-8a1a-8f2051465200&function=instruction
2026-05-16 21:39:21.416 DEBUG (MainThread) [custom_components.xtool.protocols.ws_v2.protocol] V2 connect failed for 192.168.178.143: Cannot connect to host 192.168.178.143:28900 ssl:<ssl.SSLContext object at 0x7f3d50208690> [Connect call failed ('192.168.178.143', 28900)]
2026-05-16 21:39:21.418 DEBUG (MainThread) [custom_components.xtool.protocols] Manual validation against 192.168.178.143 as M1/V2 failed: V2 WebSocket connect failed: Cannot connect to host 192.168.178.143:28900 ssl:<ssl.SSLContext object at 0x7f3d50208690> [Connect call failed ('192.168.178.143', 28900)]
2026-05-16 21:39:33.872 DEBUG (MainThread) [custom_components.xtool.protocols.rest.protocol] REST GET JSON http://192.168.178.143:8080/device/machineInfo failed: Expecting value: line 1 column 1 (char 0)
2026-05-16 21:39:33.872 DEBUG (MainThread) [custom_components.xtool.protocols.rest.protocol] REST /device/machineInfo raw response: None
2026-05-16 21:39:33.963 DEBUG (MainThread) [custom_components.xtool.protocols] Manual validation against 192.168.178.143 as DT001/V1 rejected: device info is empty (likely wrong protocol_version)

[thecodingdad]

Thanks, found the root cause, the M1 uses different REST endpoints compared to all other models using the same communication proctocol. I have one more question: does auto-discovery work in xTool Studio (or XCS) or do you have to add your device manually? I'm asking because I can't find anything about this in xTool Studio (unlike with all the other models)

[Chellux]

No. No auto discovery. But ip works directly. Testet on a "never used laptop"

[thecodingdad]

Just pushed v2.5.6. I hope it works now. If not, I’ll need debug logs again. If it's working, please check that all the entities are working properly.

[Chellux]

2026-05-17 10:08:04.529 DEBUG (MainThread) [custom_components.xtool.discovery] V1 probe target=255.255.255.255 broadcast=True multicast=False payload={"ip": "0.0.0.0", "port": 42481, "requestId": 1779005284526}
2026-05-17 10:08:04.530 DEBUG (MainThread) [custom_components.xtool.discovery] V1 probe target=224.0.1.77 broadcast=False multicast=True payload={"ip": "192.168.178.37", "port": 55987, "requestId": 1779005284526}
2026-05-17 10:08:04.533 DEBUG (MainThread) [custom_components.xtool.discovery] V2 probe target=255.255.255.255 broadcast=True rx_sockets=4 request_id=2211675723
2026-05-17 10:08:04.537 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.538 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.538 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.539 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.540 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('172.30.32.1', 5353) undecodable (192 bytes)
2026-05-17 10:08:04.725 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.726 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.726 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.727 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.728 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('172.30.32.1', 5353) undecodable (192 bytes)
2026-05-17 10:08:04.880 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.881 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.883 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.885 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.37', 55869) undecodable (192 bytes)
2026-05-17 10:08:04.889 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('172.30.32.1', 5353) undecodable (192 bytes)
2026-05-17 10:08:18.579 DEBUG (MainThread) [custom_components.xtool.discovery] V1 probe target=192.168.178.143 broadcast=False multicast=False payload={"ip": "192.168.178.37", "port": 49085, "requestId": 1779005298576}
2026-05-17 10:08:18.582 DEBUG (MainThread) [custom_components.xtool.discovery] V2 probe target=192.168.178.143 broadcast=False rx_sockets=4 request_id=3398929016
2026-05-17 10:08:21.069 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('192.168.178.109', 5353) undecodable (81 bytes)
2026-05-17 10:08:21.070 DEBUG (MainThread) [custom_components.xtool.discovery] V2 RX from ('172.30.32.1', 5353) undecodable (81 bytes)
2026-05-17 10:08:21.584 DEBUG (MainThread) [custom_components.xtool.protocols] No UDP reply from 192.168.178.143 — cannot identify device
2026-05-17 10:08:30.687 DEBUG (MainThread) [custom_components.xtool.protocols.ws_v2.protocol] V2 connecting to wss://192.168.178.143:28900/websocket?id=134be094-2de8-4a94-a889-3fa5ad491cb7&function=instruction
2026-05-17 10:08:30.792 DEBUG (MainThread) [custom_components.xtool.protocols.ws_v2.protocol] V2 connect failed for 192.168.178.143: Cannot connect to host 192.168.178.143:28900 ssl:<ssl.SSLContext object at 0x7f10d0a00690> [Connect call failed ('192.168.178.143', 28900)]
2026-05-17 10:08:30.793 DEBUG (MainThread) [custom_components.xtool.protocols] Manual validation against 192.168.178.143 as M1/V2 failed: V2 WebSocket connect failed: Cannot connect to host 192.168.178.143:28900 ssl:<ssl.SSLContext object at 0x7f10d0a00690> [Connect call failed ('192.168.178.143', 28900)]
2026-05-17 10:08:39.023 DEBUG (MainThread) [custom_components.xtool.protocols.ws_v2.protocol] V2 connecting to wss://192.168.178.143:28900/websocket?id=0a1d86a3-a665-4fe0-877a-643161d77d05&function=instruction
2026-05-17 10:08:39.095 DEBUG (MainThread) [custom_components.xtool.protocols.ws_v2.protocol] V2 connect failed for 192.168.178.143: Cannot connect to host 192.168.178.143:28900 ssl:<ssl.SSLContext object at 0x7f10d0a00690> [Connect call failed ('192.168.178.143', 28900)]
2026-05-17 10:08:39.096 DEBUG (MainThread) [custom_components.xtool.protocols] Manual validation against 192.168.178.143 as M1/V2 failed: V2 WebSocket connect failed: Cannot connect to host 192.168.178.143:28900 ssl:<ssl.SSLContext object at 0x7f10d0a00690> [Connect call failed ('192.168.178.143', 28900)]

[Chellux]

When i try to connect (m1v2)

Das Gerät wurde erkannt, aber der Protokoll-Handshake ist fehlgeschlagen. Möglicherweise ist das Gerät belegt (XCS / xTool Studio offen) oder die Firmware-Version wird nicht unterstützt.

[thecodingdad]

It was just an assumption that the firmware uses V2 protocol, but it turned out the M1 uses the V1 REST protocol with different endpoints. Can you please try to add it as M1 (v1).

[Chellux]

Same error

[thecodingdad]

It turned out not just the endpoints but also the response shape is different. I've removed the "M1 (V2)" from the model list. Your logs show that it is definitely the REST protocol and not the WS-V2 protocol.
Hopefully it's working now. If not, I'll need new debug logs.