Having trouble finding the balance or config to get data but maintain battery #338
EricLauber
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've found that neolink 0.6.2 seems to be the most stable version for me, but it eats battery life on my Battery Doorbell. Like 10% an hour, even if I set it for just mqtt with a large interval. The battery doorbell connects to doorbell power and can recharge, but only tends to do so when you don't use the device, so it's almost like connecting to get the data results in stopping charging.
I had an idea - what if I just shut neolink off entirely, and restarted it every 5 minutes? I've seen improvements, but it's still not what I wish it was. Not only is data infrequent, but I'm still losing about 20% per day. The goal obviously would be to get data like a doorbell preview image as frequently as possible, while minimizing power loss.
Anyone have ideas? Here's what I've got so far.
A custom
entrypoint.sh
that starts neolink every 5 minutes, but stops it after 20 seconds to break the connection.A custom
dockerfile
to use that custom entrypoint.I build this image locally:
docker build -t neolink-mqtt .
And then use it with this
docker-compose.yml
Beta Was this translation helpful? Give feedback.
All reactions