Does your application issue another command prior to camera.getLivePreview? For example, do you set the mode to image? Try set a delay between the previous command and the camera.getLivePreview command. Ideally, use state or status to check that the camera is ready. If the behavior is inconsistent, it might be related to the camera load at the specific time the command is sent.
here’s what I would do to trace the problem:
- upgrade to the latest firmware
- place camera right next to the computer you are connecting to order to eliminate Wi-Fi signal strength problems
- verify that liveStreaming works consistently with the official mobile app and use Wireshark capture on that app to see what the HTTP headers look like for the command. Maybe there is a difference?
- test stream with Amelia Viewer
- change the Wi-Fi frequency from 5GHz to 2.4GHz as a test
- eliminate chance of strong wifi channel interference
- try it with a different Wi-Fi adapter or computer
Successful Theta V stream from drone to VR headset 0.25 miles away
- test the other apps posted on the forum