I have to add that I noticed that on two official pages the following compliance either for Tether as for IDCloud for the V4, so I suppose shall work.

Am I right?

https://www.tp-link.com/nordic/cloud-service/product-list/

https://www.tp-link.com/nordic/tether/product-list/

By the way I follow also this guide (https://www.tp-link.com/it/support/faq/2808/?app=kasa) but no chance to get online when outside my network, and the Cloud ID options (mentioned in the guide, point 2) does not appear on my V4.

Any hints about:

shall work on V4?

how to solve it?

Thanks,

Andrea

  @Andrew4891 

Hi David TP,

Firstly thanks for the information.

This is a very bad news from my point of view.
The compatibility either for Tether App and Cloud ID, is mentioned everywhere on TPLink Website (see images on my previous post) from V4, and App (see image attached) starting from V3.
On some local TP link Website it even mention V3 for both compatibility with ether App and Cloud ID.

In my case these information from TPLINK have been misleading, since I recently specifically purchased a V4 (after having specifically required to the seller to check on the unit if this was V4 and not previous one) because I needed among other features also the SMS reading from the APP.
Obviously I looked for that specific seller because the price was interesting.

If I had known V5 was required I would have looked for a different solution.

Since one month elapsed from the purchase while in vain I tried to configure what I needed with a lot of tests and spent of time, to allow the system work, I cannot even return the unit to the seller (which by the way is not all responsible for this).

I believe the wrong information from TPLINK website and App took me to purchase a unit which does not do what is declared and claimed on the official communication channel of TPLINK.

Moreover this wrong information is probably over the Internet since at least 5 years (which I found amazing!)

What am I supposed to do now with such unit? How can TP Link help in solve this situation not caused by my error?

Thanks for the comprehension.

Andrew

  @David-TP 

Hi David,

considering my previous request claiming for wrong information claimed by TP link on communication official channel, can you tell me how to handle this case and claim?

Who shall I address my claim to get support and clarification by TP Link? How can TP Link help in solve this situation not caused by my error?

Thanks in advance,

Andrea

  @David-TP Hi David,

Thanks for the reply.

The unit cannot be returned since basically it works and respect what I specifically required to the seller (V4).

The product return policy was valid for 30 days but as mentioned in my previous post I tried for the whole last 45 days (after receving the product) to make it work without chance.

This because I was sure TP Link information provided (V4 compatible) was right, while it was not.

Now the return product policy period is elapsed and hence I have a unit which does not do what the producer tell it is supposed to do and I can't return it.

You mention by the way: "TL-MR6400 V4 doesn't support Tether APP remote management, but its firmware upgrade supports OTA firmware pushed from TP-Link Cloud via MAC address. "

It would be fine for me having to perform the FW upgrade to enable the feature, but I tried to perform a Firmware upgrade from the dedicated page on the browser but it mention the last firmware available is already installed and no different upgrade is possible.

How I am supposed in this case to perform the Firmware upgrade?

Thanks,

Andrew

  @David-TP Hi David,

I am sorry to insist but this does not change the fact.

I paied a product which TP LINK states to be compatible with a specific feature while it is not.

Now, who shall be considered responsible for the amout  paid:

1) me as customer?

2) the provider?

3) the producer?

IMHO, definetely not the first two, so how TP LINK will manage this? If is not you the one that can reply to this question, can you tell me who shall I address my concern?

Thanks for your help.

Andrew