Andrew King
Andrew King
We use this for push notification https://github.com/RandomEngy/fcm-push-listener and it says: > will stop working on June 20, 2024, since Google is shutting down an API it calls. You'll need to...
To disable push notifications put `push_notifications = false` in each of your `[[cameras]]` config. But without it we can't reliably wake up the camera when there is motion
As long as `push_notifications=false` is in every camera setup then it should not event try and connect to the push server
You can't get notified without push notifications thats why we use them. You could send a manual wake up command over mqtt when you need the picture and battery to...
Also if you have a `neolink_token.toml` from before the shutdown it should still work since only the part about getting the token was pulled
Perhaps you can try this? - Set `idle_disconnect = true` - Send the mqtt command `control/wakeup 5` at an interval you want via scripts By sending `control/wakeup 5` the camera...
Not a bug, there's a background thread that polls the battery and image as long as the camera is connected. You can disable those background threads in the mqtt config...
Motion mqtt is very specific type of motion, not my definition but the Reolink one. It is the motion that triggers the MD alarm on msg id 33. Some cameras...
I'm exploring the new fcm push notification. Seeing if there's anyone to acquire the vapid key.
I actually don't have an android (was thinking to setup an emulator), are you tech savvy enough to setup something like a mitmproxy on the android and then reinstall reolink?...