Error connecting device after deploying the cloud via docker
已完成
After deploying the cloud via docker and logging in with the controller i get the error "device not found" although my device is turned on and connected to the controller. Everything is up2date but not working. I don't know where to start looking at, it seems like the tomcat is searching the database for a device with the given ID but he cant't find it - thats what i see inside the logs of the cloud_api_sample container.
-
Sorry for keeping you waiting. Due to the current Spring Festival holiday, the relevant engineers are on vacation, and your question may not receive a timely response. We have recorded your question and will contact you as soon as the engineer's vacation ends. We deeply apologize for any inconvenience caused~ -
The deployment worked so far after investing hours and tons of time in fixing erros with taobao and nlark librarys and some other errors.
What i got stuck on now is, that there is no way to identify an incoming rtmp stream from the cloud because the url from the controller sets a new timestamp at the end of the rtmp url everytime the controller is restarted. Also there is no way to get all subscribed mqtt message topics in the console as already stated here:
https://github.com/dji-sdk/Cloud-API-Demo-Web/issues/31
Also i'm getting a java exception when going live from my rc plus:Caused by: java.lang.UnsupportedOperationException: rcLiveStatusUpdate not implemented
at com.dji.sdk.cloudapi.device.api.AbstractDeviceService.rcLiveStatusUpdate(AbstractDeviceService.java:151)
at com.dji.sdk.cloudapi.device.api.AbstractDeviceService$$FastClassBySpringCGLIB$$c8bb170e.invoke(<generated>)
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
and for me right now like i said it is not possible to identifie an incomming rtmp stream to a specific drone/remote
-
Just to add for clarification: Starting the Livestream is not possible although i'm connected to the cloud api. I need to go to main menu -> Test Group One Cloud Api Platform, select "Livestream manually" than start the live stream manually and when i go back to the pilot 2 app and view my camera from the drone and start the stream it is working. But it only works after i started it manually one time and after that the url is broken because it doesn't has the correct URL it only has the timestamp and no UUID
I'm not able to start the livestream via the controller, i'm only able to start the livestream from the /project url. After i did this once, i also can start it from the controller
-
As the code is no longer being maintained, the methods that have not been implemented need to be developed by the developers themselves. What are the specific symptoms of the failure to start the live broadcast? Is there any error information? Could you please share the returned information for us to review? -
What means, the code is no longer being maintained? Will there be any update of the DJI Cloud SDK in the future? There are already things missing in the cloud like the new m4 drone.
So... the problem is still that you need to start the stream once via the webinterface and only after you started it once you are able to start it from the drone.
If you shut down the controller and restart it, you have to start it once again from the webinterface and after that you can use the start button on the drone
请先登录再写评论。
评论
7 条评论