Well that sounds like a “yes but no” response from Wanderer.

The Wanderer Astro drivers already included in INDI.

Good to know. Thanks Jasem

Indi has support only Wanderer Lite rotator, but not Mini v2
I wrote to Frank Wang about adding support of Mini v2 rotator to indi.
His answer looks like:
"This INDI driver is not valid for rotator MINI V2.
Our new INDI driver for rotators will be available soon." (c)

I received my Mini V2 rotator yesterday and I confirm the existing driver is not particularly usable.
A few details:
- It does not connect to the device automatically. Times out, then when I manually click Connect in the INDI control panel, it actually connects.
- Although "set current position as home" works (and resets the current value to 0), the sync button says syncing is not supported.
- When rotating, the current position number changes faster than the device actually rotates. At first it made me confused as I had an impression it was rotating past the requested position.
- More often than not, after reaching the requested position, the current value jumps to seemingly random numbers.

An example of the last point: I reset home position (current is 0), moved to 45. Then started "homing" (I think this is just supposed to be "go to home position"). It moved back to the initial place, but the current position became something wild like 294 instead of 0.
When I told it to go again to 45, it started moving backwards.

I know it was already stated above, but yes, the current "Lite" driver is not usable for the Mini V2 device.

Absolutely the same behaviour for me. I suggest you also to write email to Frank Wang and ask him about writing driver for Mini V2 for libindi or opening specification to do this by community.

Here's what he kindly responded:

any experience with the flat panel?

by the way, any plan to support the V4 flat panel?

github.com/indilib/indi/pull/2000

It has happened, driver for WandererRotator Mini V1&V2 was added

Hoping to give it a test tonight, although not under the sky as the winds are a bit crazy today.

Here's what I did and observed.

1. Connected. Current angle is loaded as 110.
Backlash is disabled, reverse is also disabled.
Limits are set to 0.

2. I click “Mechanical Zero”
Log: Virtual Mechanical Angle is set to zero.
Current angle is also reset to 0.00.

3. I try to make it go to 90.
It rotates CCW by 90 degrees, and as it is moving the current angle field is updated accordingly.
However, when it stops, the current value is set to 9.00 instead of 90.

4. I try to make it go to 0.
It rotates CW, but only by a tiny bit (I suspect by 9 degrees).
And the current angle field is set to 8.10 instead of 81 (I am starting to see a pattern here)

Looks like there is a bug that sets the current angle to only 0.1 of the actual value.

The logs only say what its rotation targets are, together with the commands, but one can see that the second move command parameter (-10278) is only -0.1 of the first one (102780).