USB_ModeSwitch

Hello, if anyone could help me with this I would be very grateful

I recently bought a TP-Link TL-MR4320 which have ZTE MF110 on their compatible list of modems.
It detects the modem as MF110, but never connects (I've triple-checked settings with my ISP)

However, there seems to be a problem when it's using usb_modeswitch

truncated snipped from the routerlog:

1st day 00:11:15 3G NOTICE Modem switchs failed, reset the 3G modem, please wait.
.
.
.
1st day 00:11:35 3G INFO 3G Modem vendorID: 0x19d2; productID: 0x2000

1st day 00:11:48 3G INFO Switch modem mode with the 0 command in the file usb_modeswitch.conf

1st day 00:11:49 3G INFO 3G Modem vendorID: 0x19d2; productID: 0x2000

1st day 00:12:00 3G INFO Switch modem mode with the 1 command in the file usb_modeswitch.conf

1st day 00:12:08 3G INFO 3G Modem vendorID: 0x19d2; productID: 0x0017
.
.
.
1st day 00:13:59 3G NOTICE Modem switchs failed, reset the 3G modem, please wait.

In the device reference (http://www.draisberghof.de/usb_modeswit ... erence.txt isn't valid btw) there are two variants of MF110:

########################################################
# ZTE MF110 (Variant)
#
# Contributor: Moritz Grosse-Wentrup

DefaultVendor= 0x19d2
DefaultProduct= 0x0053

TargetVendor= 0x19d2
TargetProduct= 0x0031

MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
MessageContent2="55534243876543212000000080000c85010101180101010101000000000000"

NeedResponse=1

and

########################################################
# ZTE MF110 (Variant)
#
# Contributor: uusrlnx

DefaultVendor= 0x19d2
DefaultProduct= 0x0083

TargetVendor= 0x19d2
TargetProduct= 0x0124

MessageContent="5553424312345678000000000000061b000000020000000000000000000000"

NeedResponse=1

as well as multiple ZTE models that have 'DefaultProduct = 0x2000' but none that has 'TargetProduct= 0x0017'
Is this the problem?
Have ZTE changed something internally for my ISP (bredbandsbolaget/telenor in Sweden) while keeping the model as MF110?

TP-Links customer service has only replied with the standard "upgrade your firmware" boilerplate but maybe you guys here have some better insights?
Thanks!

See the latest data package linked in the "Download" paragraph. It contains a config file "19d2:2000". The target product ID "0017" is listed there.

The switching in the router seems to be working, but it is probably not recognized due to outdated configuration files.

Thank you for the quick reply, so the solution is to nag TP-link into upgrading their firmware then yes?
Should I just tell them to get the latest usb_modeswitch release or something more specific...?

I had a look at the source code of the router (v1) from the maker's web site.

The usb_modeswitch version is 1.0.5, which doesn't tell much. But the config files provided with it are quite dated too; the question is if there was an update at one point. And I have no idea how they wrap/run those config files.

The stupid binary modem files that they are providing for special cases are not helpful either. If you could import new modem parameters via a little text file - now, that would make sense ...