Skywatcher Alt Az Simple new issue ?

[saviourbot]

After an upgrade my Alt Az will no longer connect (Debug below) I dont want to raise it as an issue if it is just something I am doing wrong has there recently been a change in InitMount() ?

The mount connests as a USB device to the PI:
astroberry@astroberry:~ $ ls -l /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_BKCXb106315-if00-port0 lrwxrwxrwx 1 root root 13 Feb 3 10:26 /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_BKCXb106315-if00-port0 -> ../../ttyUSB0

Debug output shows no connect - Handshake failed:
INFO 0.030534 sec : Session log file /home/astroberry/.indi/logs/2022-02-03/indi_skywatcherAltAzMount/indi_skywatcherAltAzMount_10:51:52.log
DEBUG 0.121657 sec : Connecting to /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_BKCXb106315-if00-port0 @ 9600
DEBUG 0.126972 sec : Port FD 3
DEBUG 0.127087 sec : Connection successful, attempting handshake...
SCOPE 0.127124 sec : SkywatcherAPIMount::Handshake
SCOPE 0.127159 sec : CheckIfDCMotor
SCOPE 1.129368 sec : CMD
SCOPE 1.133705 sec : RES
SCOPE 1.133787 sec : Mount type not supported. 0
SCOPE 1.133817 sec : SkywatcherAPIMount::Handshake - Result: 0
DEBUG 1.133846 sec : Handshake failed.

`bool SkywatcherAltAzSimple::Handshake()
{
DEBUG(DBG_SCOPE, "SkywatcherAltAzSimple::Handshake");
SetSerialPort(PortFD);

Connection::Interface *activeConnection = getActiveConnection();
if (!activeConnection->name().compare("CONNECTION_TCP"))
{
    tty_set_generic_udp_format(1);
}

bool Result = InitMount();

if (getActiveConnection() == serialConnection)
{
    SerialPortName = serialConnection->port();
}
else
{
    SerialPortName = "";
}

RecoverAfterReconnection = false;
DEBUGF(DBG_SCOPE, "SkywatcherAltAzSimple::Handshake - Result: %d", Result);
return Result;

}`

It has been working fantastic but since an apt upgrade not so much.

Thanks in advance
Gus

Update: I did a fresh build of the astroberry 2.0.4 build and it worked. Then I did an apt update && apt upgrade and I got the error again.

So, it appears to be a recent change causing the problem.