-
Notifications
You must be signed in to change notification settings - Fork 180
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
Fixes 'jq' try to read settings_auto.json warning in logs #548
Conversation
Don't merge yet... I'm seeing another oddity that I want to run down. May be more commits coming. |
Ok, found and fixed my other issue -- was a local test gone wrong ... this PR is safe to commit. |
Ok, there was a bug in the earlier commit -- using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Michael,
Have you tried this on your Pi? I'm not sure the config.sh change will work. If $CAMERA=auto it won't set CAMERA_SETTINGS and all jq commands will fail.
Or am I missing something?
If it DOES work, you can delete the "fi" on line 123 and change the "if" on 125 to "else". You already checked for CAMERA=auto on 120 so no need for another check on 125.
HI @EricClaeys -- actually, the double check of It's how the script detects that the contents of New logic:
Since To the first question - yes, it's running on my Pi right now. :) |
Thanks for the explanation Michael. Let's hope Thomas agrees we can dump the CAMERA=auto, in which case we don't need this and we can use ALLSKY_DEBUG_LEVEL as soon as config.sh is sourced in to allsky.sh, rather than after the camera detection is done. |
Fixed in two steps:
CAMERA
is still set toauto
after readingautocam.sh
fromconfig.sh
, don't try to read the camera settings, instead set default debug level 0.allsky.sh
, if auto camera detection was selected, and we detect a camera, re-read debug level from the proper camera settings file.