-
-
Notifications
You must be signed in to change notification settings - Fork 488
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
Camera widget cannot get most recent timelapse image if custom path is defined #1072
Comments
Thanks for the bug report. I'll prepare fixes that will be available in the next release. |
Actually, this was suposedly fixed with cca16f6#diff-6d1d7d9a1ecfaec5100bf049d2ac42413e199e7d979151a31f649510c1afce94 Neither the current release nor master branch has "INSTALL_DIRECTORY/cameras/{camera_uid}" in utils_general.get_camera_image_info(). This appears to be an issue with camera_img_latest_timelapse() in routes_general.py: Mycodo/mycodo/mycodo_flask/routes_general.py Lines 179 to 181 in 803f3eb
|
It's a bit more involved that that, I'm finding, but I'll have it solved soon enough. |
… widget resizing, fix email logging showing actual subject
Just committed a fix. Thanks again for the bug report. |
Thank you for the quick fix! And yes, my mistake for specifying that it was hardcoded to that path when I was making reference to |
Describe the problem/bug
I have a camera defined with a custom timelapse path. When I configure a camera widget on my dashboard and select "most recent timelapse image", it will never find a valid one because it doesn't flex on the custom path.
The logic in
routes_general.camera_img_latest_timelapse()
is hardcoded to search for the filename successfully found byutils_general.get_camera_image_info()
within"INSTALL_DIRECTORY/cameras/{camera_uid}"
.Versions:
Reproducibility
Please list specific setup details that are involved and the steps to reproduce the behavior:
Expected behavior
The most recent timelapse image would show in the widget
The text was updated successfully, but these errors were encountered: