How to build a stable 0.6.2 docker image that supports mqtt? #329
Replies: 1 comment
-
As a test, I got some GPT help and created the following to try and use this build with mqtt. This enables me to build a custom image locally and then when combined with a I ran this with my Battery Doorbell Camera for about 4 hours, mqtt configured to transmit every 15,000 milliseconds. For the first hour mqtt worked fine (I can see battery level dropping about 10% over an hour) and then I stopped getting new mqtt values published to the broker. Logs for the docker container showed that neolink started running into a disconnect-reconnect cycle where it was failing to maintain a connect or obtain new values from the camera. Based on the mqtt published date values it looks like it continued to publish the old values - so battery level sat at 89% for about 3 hours while in reality the camera was in use. I just stopped and restarted the container and started getting data properly again.
|
Beta Was this translation helpful? Give feedback.
-
I've been testing the docker images of the latest builds and v0.6.2. At least on my machine I have found 0.6.2 is more stable and maintains a good connection with my camera, but it looks like that release had an error with the dockerfile that forced it to always run in rtsp mode independent of the environmental variables provided. That issue is fixed on the latest image (mqtt works) but I encounter other stability issues.
I figured since v0.6.2 is stable for me, I just need the dockerfile fixed. I checked out the source at commit e47a0d5734b0a06b53bd8d78be9ca2f6b8396480, made the fix to the dockerfile, and ran a build locally. I get this error:
Any thoughts on if I need to checkout at a different more-recent commit or what fix to implement so I can build this locally?
This is the dockerfile as I have it today.
Beta Was this translation helpful? Give feedback.
All reactions