-
Now get this error in the WEBUI
If I check the directory on the pi I find this.
found the directory but looks like everything is locked. I can not use NANO to write anything just look.
pi@allsky1:~/allsky $ libcamera-hello
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
SOLVED |
Beta Was this translation helpful? Give feedback.
-
@BobW55 The next release lets you change the camera using the WebUI and does not allow manually editing the config.sh file for camera changes. It also updates the WebUI's "Camera Settings" page to reflect what capabilities the camera model has. The Glad you got it working. Please note the settings are somewhat different so you'll need to tweak them again. |
Beta Was this translation helpful? Give feedback.
-
Better yet…
The user can’t enter a name – they select from a drop-down. You select the camera TYPE (RPi or ZWO), and it automatically determines the MODEL (HD or compatible, or one of the many ZWO models).
Eric
From: BobW55 ***@***.***>
Sent: Thursday, December 1, 2022 12:40 PM
To: thomasjacquin/allsky ***@***.***>
Cc: EricClaeys ***@***.***>; Comment ***@***.***>
Subject: Re: [thomasjacquin/allsky] switched cameras from RPiHQ to ZWO now can't load the WEBUI (Discussion #1941)
Hope you make it so the camera name is not case sensitive. Was switching back and forth last night. Must have gotten tire and input "zwo"
Maybe select 1 for RPiHQ and 2 for ZWO 3 for Other
—
Reply to this email directly, view it on GitHub <#1941 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT2PYK6W34D2FUIXF5XLZMDWLD5IHANCNFSM6AAAAAASQ4RCD4> .
You are receiving this because you commented. <https://github.com/notifications/beacon/AT2PYKYIRMHRSPH24F2NBCLWLD5IHA5CNFSM6AAAAAASQ4RCD6WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAIFT7O.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
@BobW55 Our "to do" list for the release after the one that's almost out is to have a "Save / Store Configuration" button that saves or restores all the configuration files. That'll make moving to a new machine easier. Also on the "to do" list is a button to zip all the log files (including the temporary ones in allsky/tmp) then give people instructions on how to attach the zip file when reporting issues or asking configuration-related questions (like yours). That'll be easier on users and MUCH better for those of us supporting Allsky. |
Beta Was this translation helpful? Give feedback.
-
@BobW55 We've tried that and so have others, and the response has been pretty dismal. The next release will have the option to upload your settings to your Allsky Website; if it's accessible via the Internet then you can look at other people's settings. For privacy issues the default is "no". If those people put their camera on the Allsky Map, we may be able to poll all the map users' settings file automatically and summarize. The ZWO auto-exposure algorithm isn't very good so we wrote our own but it only works during the day so the ZWO algorithm is used at night. In the release after the upcoming one I hope to implement our RPi auto exposure/gain algorithm which works all the time and is pretty good. |
Beta Was this translation helpful? Give feedback.
SOLVED
Had to manually edit the Config.sh file.
had put zwo in lower case' things looking for UPPER case ZWO.