I am looking for advice regarding the integration between Mews and TESA locks.
We chose TESA mainly because it is officially supported by Mews, but after following the Mews setup instructions, we still cannot connect Mews with TESA. The TESA system itself works perfectly: the locks work correctly and card encoding works from the TESA application. The issue is only the connection between Mews and TESA.
I opened case 00668982 with Mews Support on 15 June. Since then, I have checked Mews Connector, tested different IP/port combinations, performed key creation tests, and sent all requested logs. On 18 June, I was told the case had been escalated to developers, but I have now been waiting 9 days without any real update or solution. This is affecting our daily operation, as we are having to create all keys manually from TESA.
Could someone from Mews please review the case and clarify whether this is a known issue, a missing configuration step, or something specific to our setup?
we do have the same issue. Many different trys with our partner / TESA Resller and hopefully we are on the final way… i will talk to our IT guy today and if you want i can let you know.
Thank you for your quick reply. Yes, please, I would really appreciate it if you could let me know what solution you find with your IT team and TESA reseller. It is at least reassuring to know that we are not the only property facing this issue, although honestly it is very disappointing that Mews is providing such poor support on an integration they promote as supported.
Mews is announcing new mobile check-in/opening features, but in my opinion they should focus more on the quality and reliability of their existing services before adding more layers. For properties like ours, this is not a minor issue; it directly affects daily operations.
@JTJ46 i spoke to our IT guys! so it is by now not a MEWS issue it is between our reseller and TESA as the service shutsdown every 5-10 minutes and they need to investigate what the cause is.
As soon i do get the feedback i will share that and i am maybe than be able to share our contact at TESA to speed up the process for you as will. I believe there will be a solution.
Hi @JTJ46 @Johannes_Rott
Thank you for being patient. This was indeed escalated and it took some time for it to reach a resolution with the engineering team. I believe it’s now understood as a TESA integration issue and the fix is now available, as of yesterday. I’ve followed up with the support team and asked to give you an update.
I have tested it again, but unfortunately it is still not working. Support told me that I should not need to change anything and that the current configuration should work as it is.
However, I believe the Mews–TESA guide is outdated. The screenshots show a TESA software version that, according to the TESA technicians, is no longer in use and has been replaced by a newer version.
Could you please update the guide or provide clear, step-by-step instructions on how to remove and reconnect the integration using the current TESA software?
The current Mews guide for TESA is too limited and leaves out essential configuration details. Mews should be more careful with this type of error and update the documentation with a more detailed, accurate and realistic step-by-step guide.
Hopefully, this helps anyone facing the same issue.
The current Mews guide for TESA is too limited and leaves out essential configuration details. Mews should be more careful with this type of error and update the documentation with a more detailed, accurate and realistic step-by-step guide.
Hopefully, this helps anyone facing the same issue.
KR, Javi
Hi Javi,
thanks on the update, we will give it a try as we are still struggling.