@codetricity we noticed very strange behaviour from Theta V (on 2 devices)
It is randomly hanging. If we are asking every 10 seconds or every few minutes for list of files in some time it stops responding. It is answering to mDNS requests but not TCP or ICMP requests. Sometimes we can call few hundred times sometimes few times until this hang. It is not responding to any device asking. Only shutting down and turning it on again fixes issue until next hang.
Theta is responding to DNS calls while being hung. Which means, we can discover it over network but we can’t call any API because it will timeout. As far as i remember Android NSD uses DNS-SD. Python code used mDNS
I’ve updated camera to latest update (so update was made today). Issue persist. After some random time(and number of requests), camera stops responding to any api calls but it is still visible in network
i’m also checking it via: “avahi-discover” command on my linux.
From my further tests, when camera hangs, i was able to discover via avahi, but while clicking for more details avahi also returns timeout: “Error: org.freedesktop.Avahi.TimeoutError: Timeout reached”. It looks like internal server is shutting down
I’ve been thinking about this more. As the THETA V is using Network Service Discovery, I think that DNS-SD is the main supported method.
NSD implements the DNS-based Service Discovery (DNS-SD) mechanism, which allows your app to request services by specifying a type of service and the name of a device instance that provides the desired type of service. DNS-SD is supported both on Android and on other mobile platforms.
While mDNS does work, it is probably not tested as thoroughly. I’m still thinking that we should try and use DNS-SD when possible.
I know a developer that is using this for testing:
Thank you for your reply, haha, I am developing the Android mobile terminal. The client mode of THETA V has been bothering me for a long time, until I saw your post yesterday. That Android Developers page is very helpful to me, thank you very much.