Can't connect to F2 machines

[rwgunther]

Migrated from BassXT/xtool. I was able to connect to my P2S, but not to either of my F2 machines—an F2 and an F2 Ultra UV. Both were auto-detected, but they both resulted in the message "Protocol handshake with the device failed — close XCS / xTool Studio and try again." Each device beeped when that message appeared. I do not have XCX open, and I checked in Activity Monitor to ensure there was nothing from xTool still in memory.

[DerSchdief]

@rwgunther I have the same error with my F2 Ultra UV. There is an open issue on BassXT/xtool where thecodingdad and i are working on it (mostly thecodingdad, im just giving him the error logs :D)

He updated it just now and i can add the Laser to HomeAssistant now. (Link to the Issue on BassXT/xtool: BassXT/xtool#20)

Maybe we should migrate the issue from BassXT/xtool to here.

[thecodingdad]

@DerSchdief yes, let's continue here!
@rwgunther please test the latest version

[thecodingdad]

@DerSchdief @rwgunther I've added tons of entities. Can you please check if all entities are working and report back any issues:

• Entities with state "unknown"
• Config/control entities not working
• Redundant entities
• Entities that represent features your device doesn't even have.
• Accessory entities (like AirAssist) that aren't connected to your device

https://github.com/thecodingdad/ha-xtool/releases/tag/v2.3.0

[BassXT]

Hi @thecodingdad I still get the same error trying to connect my f1.

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]

Strange, can you please provide debug logs? Have you tested v2.3.0? If so, it could be related to new entities added. Could you also check if v2.2.13 is working (confirmed working by @DerSchdief for an F2 Ultra UV)

[DerSchdief]

I can confirm that 2.2.13 and 2.3.0 are working for the F2 Ultra UV

Entities with state "unknown"
Config/control entities not working
Redundant entities
Entities that represent features your device doesn't even have.
Accessory entities (like AirAssist) that aren't connected to your device

I will check the points above these days and report back here.

[thecodingdad]

@DerSchdief thanks for the fast response. Then it must be a specific issue with the F2

[BassXT]

Nah sorry my bad - the device was tuned off 😂

[thecodingdad]

But thats also a good feedback: better error messages

[thecodingdad]

@BassXT Just to confirm for myself: is everything working properly now?

One thing else on my mind: It looks like some devices have a sleep mode, but I’m not exactly sure what that restricts. What I do know, though, is that there’s a command to wake the device up. But I don’t want to send unnecessary wake-up commands without knowing if it’s even necessary. So if certain functions become unavailable over time, please let me know.

[BassXT]

I can't say if every switch is working but autodiscovery did work an the device is revognized.

The most important sensor, the status sensor, is working.

I don't think ther is any need for you to implement a function to automatically wake the device up. The F-Series lasers are showing a dot so you can set the right height. after some time with no interaction the device will fall asleep an the dots will turn off.
The next interaction will automatically wake the device up.

[thecodingdad]

@rwgunther @DerSchdief Made some progress with the F2 Ultra UV, see issue #4. Feel free to test it.