-
-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Per camera snapshot settings for indoor/outdoor camera mix? #970
Comments
Will look into this. |
Or, I just realized, as another idea....could the outdoor cameras periodically poll the API for an updated snapshot at the same interval as whatever is set for RTSP? When motion events trigger, if I'm not mistaken, the snapshot on the Wyze end updates. If that's the case, it'd be awesome to poll the API often-ish to so those snapshot images are somewhat current yet not battery draining. Thanks for looking into this! |
You might want to try out the dev branch which currently has motion events that can be enabled with Will try to see if we can update the snapshot url when an event is detected. |
* audio latency #388 * Motion Events * Log number of cams from API #974 * Store and reuse s3 thumbnail from events #970 * better error handling * Increase MTX_WRITEQUEUESIZE #984 * MOTION_START for HA * limit login attempts * pass exceptions upstream * motion images for webhooks/ntfy in header * REST API motion endpoint * Additional audio codecs * keep stream alive if livestream enabled #985 * Catch RuntimeError #994 * assert bitrate value * refactor av_send_io_ctrl * Refactor API client and use battery from device_info * motion_ts endpoint * use .pipe instead of .wav for audio pipe * update frame size if not preferred_frame_size * Exclude battery cams from RTSP snapshots #970 * revert changes * buffer mtx event data #990 * Match all 11.x or newer firmware #975 * MOTION_WEBHOOKS * clean * revert changes * Media MTX changes * ffmpeg v6 * Use ffmpeg-for-homebridge in QSV build #736 * remove unneeded packages * don't return none * Adjust queue size and compression #388 * Adjust sleep, queue, and fifo for lag * Catch other HTTPErrors for events * Revert "Adjust sleep, queue, and fifo for lag" * Update ffmpeg.py * Update tutk.py * adjust thread_queue_size #388 * Add build date time * Update ffmpeg.py * Additional queue tweaks and fifo options #388 * Catch RequestException in motion events * Update MediaMTX version from v1.1.0 to v1.1.1 (#1007) (#1008) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mrlt8 <mrlt8@users.noreply.github.com> * Fix ETag header for MediaMTX 1.1.1 * Don't use wallclock #388 * remove asetpts * audio #388 * Update ffmpeg.py * allow wallclock flag in FFMPEG_FLAGS #388 * changelog * Update .env
I have just run into this; the battery was killed on all my outdoor cameras. Would love to see a solution! |
motion events was added back in v2.4.0: https://github.com/mrlt8/docker-wyze-bridge/wiki/Camera-Motion |
Got that, doesn't seem to matter. No motion has happened but the battery is dead. |
Settings are snapshot mode: API, and MOTION_API on, and the battery drained. I also tried ON_DEMAND on, but this stops snapshots from appearing in Home Assistant entirely. Also, with snapshot mode to API, I don't get my non-battery cameras updated on a regular interval. |
ON_DEMAND shouldn't affect battery cams, so I believe you can leave it off. You can trigger a snapshot on demand by using:
or use the
the |
* Sign motion event request #1125 * use device id instead of mac #1125 * remove wrong flags from mkfifo #1174 * less aggressive flush #1159 #1167 * Use K10052 for setting FPS #1161 * Refactor bits for going above 255 for quality * Revert ffmpeg changes #1159 #1167 * version is obsolete * default quality to hd180 * Update Wyze iOS App version from v2.44.5.3 to v2.50.6.1 (#1176) * use struct pack * Token based auth over the webUI * Fix redirect for Home Assistant Ingress * Use request headers to fix redirect for HA * Change GET to POST for webhooks data * Deprecate ifttt_webhook in favor of webhooks * use yml for HA config and make credentials optional * keep trying to identify audio #1172 * Snapshot on motion and push to mqtt #709 #970 * Add event time to motion message * refactor auth * EVENT_API option #1125 * Add additional headers #1125 * Audio sync with higher bitrate * Debug api request #1125 * Update api.py * only debug on error * Tweak audio sync * don't raise error on lost frame * clear buffer if out of sync * Unique macs only #1125 Co-Authored-By: Cameron <32912464+kiwi-cam@users.noreply.github.com> * Require auth by default and block non-ingress access #1181 * Allow non-ingress access with auth #1181 * Remove retain flag from commands #1182 * update webrtc to work with auth streams * Add WB_API and rename WEB to WB #1181 WEB_USERNAME > WB_USERNAME WEB_PASSWORD > WB_PASSWORD * HA move /config/wyze-bridge/ to /config/ * Don't notify substream event and remove v2 #1125 * WebUI Auth related config for HA * Don't retain discovery message? #1182 * Case sensitive credentials for WebUI * changelog and readme --------- Co-authored-by: Cameron <32912464+kiwi-cam@users.noreply.github.com>
I tried various combinations of the above; I can either get no snapshots or thumbs or get battery drain on the battery cams. |
Do you have the motion detection active on the camera? The thumbs should get updated when the camera detects motion and pushes that to the cloud. |
I have a mixture of outdoor cameras and non-battery cameras in my setup. For the indoor cameras, it's great having them use an RTSP interval setting; however, even the longest available option in the HomeAssistant config (RTSP300) will quickly kill the outdoor cameras within about a day.
Is it possible to have those outdoor cameras pulling the snapshot from the API while having the indoor/wired cameras grabbing their snapshots via RTSP?
Or alternatively, could we get new options to define even longer custom RTSP intervals within the HomeAssistant settings?
The text was updated successfully, but these errors were encountered: