significant improvements. I connected the slim cam via rtsp to the dahua DVR and view it through the gdmss plas program. So, cam slim loads much faster, together with dahua cameras. I used to think that the problem was the long loading time in the ewelin server, but it turns out the problem is in the ewelink app itself. I once again decided to use, in the hope that the problem was solved, NFC tags to allow children to gain access to the house by opening an electromechanical lock. but due to the infinitely long loading time of the ewelink app, this idea turned out to be a failure!!! We all constantly hear promises to solve all these problems, but things don’t go beyond promises!!! I suggest one more improvement. Today I connected to smart things and an update appeared there. They use maps for houses. Why don’t you take this idea on board??? Honestly, I’m surprised that you haven’t come to this kind of improvement before, because this is the best smart home control that can be!!! You don’t have to reinvent the wheel. All you have to do is take advantage of what has already been invented and improve it!!!
Thx for your feedback!
I’m glad you find a way to have our cam work better. But if the issue is serious from the eWeLink app side, would you please submit a support ticket in the app, so our team can look for a way to improve the performance?
The Mapview/Floorview feature is already in discussion, we will share more information on this once we have determined a solid roadmap for this feature.
Hello! Is there any positive news about the map???
Hello. Is there any news? Over such a long period, there must be some results.
Hey
The feature is still in the early evaluation phase for the WEB. We will provide more detailed information once we have a more specific solution and user experience design.
It’s very, very bad that it’s at an early stage of evaluation!!! It’s not even at the development stage… at this rate, in 2-3 years we might hear about some progress
Sorry for failing your expectations. As you can tell, it’s a complicated feature, and even those who have been offering this feature for a while still experience serious crashes and are less stable to use on a daily basis.
And I may have conveyed misleading information in my last reply. The team has previously researched some solutions to build the feature, but they cannot meet our standards so far, which is a key reason why it took longer than we expected. But we will keep trying as long as there is a strong need from the community.
Thx for your concerns on this feature.
Thank you very much. I will wait with great impatience!!!