@DTS Engineer The certificate implementation on the accessory side is not yet completed.
For the time being, I am using a website with a self-signed certificate to test this scenario. The issue occurred because I used the website's domain name. When I replaced the domain name with the IP address, the issue was resolved.
The changes need to be tested again with the accessory device once it is ready.
You really should complain to your firmware folks, because using the same self-signed digital identity for all instances of your accessory makes it even more insecure
This makes sense. I will discuss it with my device development team. Thank you very much for your valuable feedback.
Topic:
App & System Services
SubTopic:
Networking
Tags: