Closed Shand359 closed 2 years ago
@Shand359, can you attach (don't copy/paste) your config/config.sh and config/ftp-settings.sh files? You may need to append ".txt" to their names. Make sure to blank out any sensitive data in ftp-settings.sh.
You can also try pressing F12 in the web browser, then click on the "Network" link and refresh the browser window. It should show what the name of the file is that it's trying to display.
Thank you for your quick reply..... this is so annoying as i had it working with a previous version.... both files you asked about have been attached...
ok, from what i can see and figure out, it is trying and failing to load the liveview-image.jpg file....
Nov 24 16:29:41 raspberrypi allsky.sh[688]: Starting AllSky Nov 24 16:29:42 raspberrypi allsky.sh[688]: RPiHQ Camera not found. Exiting. Nov 24 16:34:05 raspberrypi allsky.sh[746]: Starting AllSky Nov 24 16:34:05 raspberrypi allsky.sh[746]: RPiHQ Camera not found. Exiting. Nov 24 16:37:50 allsky allsky.sh[781]: Starting AllSky Nov 24 16:37:51 allsky allsky.sh[781]: RPiHQ Camera not found. Exiting. Nov 24 16:39:55 allsky allsky.sh[1533]: Starting AllSky Nov 24 16:39:55 allsky allsky.sh[1533]: RPiHQ Camera not found. Exiting. Nov 24 16:56:17 allsky allsky.sh[725]: Starting AllSky Nov 24 16:56:17 allsky allsky.sh[725]: RPiHQ Camera not found. Exiting.
I suppose that explains why there is no image being produced...
@Shand359 That'll do it.
What do you get when you run vcgencmd get_camera
and grep -i "VERSION_CODENAME=bullseye" /etc/os-release
?
@Shand359, Did you keep restarting the service, or did it do that automatically? After printing the "not found" message, it's supposed to stop the service.
it was probably me resetting and restarting the rpi
@Shand359
What do you get when you run vcgencmd get_camera
and grep -i "VERSION_CODENAME=bullseye" /etc/os-release
?
pi@allsky:~ $ vcgencmd get_camera supported=1 detected=0 pi@allsky:~ $ grep -i "VERSION_CODENAME=bullseye" /etc/os-release
Look vor 2020-02-13-raspbian-buster-full
on this it will run.
Look vor 2020-02-13-raspbian-buster-full on this it will run.
I found a copy of buster and got it running like before on it. Thank you for that....
I had to go back to an older RPi3 as the 4 kept crashing or freezing.... One day things will just work as intended.... lol
@Shand359 A possible hardware or power issue? Were you running Allsky when the Pi 4 crashed and froze?
If your original problem has been resolved would you please close the iseue?
I have the same Problem with my "Raspberry Pi 4", HQ-Camera, newest OS since days. After complete installation and configuration of OS with Windows "Raspberry Pi Imager" and the "allsky"-SW with your instructions here, the Liveview-Screen is also totally blank; only a small Icon in the top-left corner. I totally formatted the SD-Card 3-times without success, always same issue.
_vcgencmd get_camera --> supported=0 detected=0 grep -i "VERSION_CODENAME=bullseye" /etc/os-release_- -> VERSIONCODENAME=bullseye ./allsky.sh_ Starting AllSky RPiHQ Camera not found. Exiting.
At first, i thought that my camera is defective, but after reading above discussion, i think, this is not a camera problem. isn'it? greetings, Peter from CH P.S. sudo systemctl status allsky ● allsky.service - All Sky Camera Loaded: loaded (/etc/systemd/system/allsky.service; enabled; vendor preset: enabled) Active: inactive (dead) since Sat 2021-11-27 16:55:34 CET; 19s ago Process: 3535 ExecStart=/home/pi/allsky/allsky.sh (code=killed, signal=TERM) Main PID: 3535 (code=killed, signal=TERM) CPU: 189ms
Nov 27 16:55:34 PedroSky systemd[1]: Started All Sky Camera. Nov 27 16:55:34 PedroSky allsky.sh[3535]: Starting AllSky Nov 27 16:55:34 PedroSky allsky.sh[3535]: RPiHQ Camera not found. Exiting. Nov 27 16:55:34 PedroSky sudo[3551]: pi : PWD=/home/pi/allsky ; USER=root ; COMMAND=/usr/bin/systemctl stop allsky Nov 27 16:55:34 PedroSky sudo[3551]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Nov 27 16:55:34 PedroSky systemd[1]: Stopping All Sky Camera... Nov 27 16:55:34 PedroSky sudo[3551]: pam_unix(sudo:session): session closed for user root Nov 27 16:55:34 PedroSky systemd[1]: allsky.service: Succeeded. Nov 27 16:55:34 PedroSky systemd[1]: Stopped All Sky Camera.
almost identical to my issue after a fresh clean install... I dont know enough about Rasbian/Linux or RPi software to play around with settings.... I can only follow the instructions that other people have typed....
@Shand359, @Pedritoprint, the command we use to determine if a RPiHQ camera is attached works differently in Bullseye so unfortunately the Allsky software thinks there is no camera when there actually is one. So the software stops and you don't get any pictures.
We will fix, but in the meantime I posted a workaround in another discussion. In allsky/allsky.sk there is a line that uses "vcgencmd get_camera" to determine if a camera exists. If it does it sets a variable (called something like RPiHQisPresent??) to 1, else it sets it to 0. Simply change the 0 to 1 and restart the service.
Look in /var/log/allsky.log for any error messages. And let me know how it goes.
Nov 27 23:35:52 allsky allsky.sh[28556]: [0:28:22.924995929] [28558] ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x009e0901 but control is not exposed by device /dev/video0 Nov 27 23:35:52 allsky allsky.sh[28556]: [0:28:22.926533469] [28558] ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x00980911 but control is not exposed by device /dev/video0 Nov 27 23:35:52 allsky allsky.sh[28556]: [0:28:22.926886169] [28558] ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x009e0903 but control is not exposed by device /dev/video0 Nov 27 23:35:52 allsky allsky.sh[28556]: Stream configuration adjusted Nov 27 23:35:52 allsky allsky.sh[28556]: [0:28:22.930974461] [28558] FATAL Serializer control_serializer.cpp:598 A list of V4L2 controls requires an ControlInfoMap Nov 27 23:35:52 allsky allsky.sh[28556]: Backtrace: Nov 27 23:35:52 allsky allsky.sh[28555]: Aborted Nov 27 23:35:52 allsky allsky.sh[19202]: >>> Unable to take picture, return code=134 Nov 27 23:35:52 allsky allsky.sh[19202]: > Sleeping from failed exposure: 0.0 seconds Nov 27 23:35:52 allsky allsky.sh[19202]: STARTING EXPOSURE at: 2021-11-27 23:35:52 @ 1.0 sec
@Shand359, @Pedritoprint, the command we use to determine if a RPiHQ camera is attached works differently in Bullseye so unfortunately the Allsky software thinks there is no camera when there actually is one. So the software stops and you don't get any pictures.
We will fix, but in the meantime I posted a workaround in another discussion. In allsky/allsky.sk there is a line that uses "vcgencmd get_camera" to determine if a camera exists. If it does it sets a variable (called something like RPiHQisPresent??) to 1, else it sets it to 0. Simply change the 0 to 1 and restart the service.
Look in /var/log/allsky.log for any error messages. And let me know how it goes.
Thanks a lot, here my logfile after changing value to ": Nov 28 10:42:21 PedroSky allsky.sh[941]: Starting AllSky Nov 28 10:42:22 PedroSky allsky.sh[941]: CAMERA: RPiHQ Nov 28 10:42:22 PedroSky allsky.sh[941]: CAMERA_SETTINGS: /etc/raspap/settings_RPiHQ.json Nov 28 10:42:22 PedroSky allsky.sh[941]: Starting allsky camera... Nov 28 10:46:46 PedroSky allsky.sh[941]: Nov 28 10:46:46 PedroSky allsky.sh[941]: Sorry, AllSky with RPiHQ cameras on the Bullseye operating system does not yet work. Nov 28 10:46:46 PedroSky allsky.sh[941]: See https://github.com/thomasjacquin/allsky/discussions/802 for more information. Nov 28 10:46:46 PedroSky allsky.sh[941]: BTW, now in "Liveview" i could see a Picture (Error.jpg) with the hint to see in "var/log/allsky.log" about the "Error" and now waiting, like other users of "allsky", for new version. Also reading the official statement of "Raspberry" here. and here
I re-opened this simply to state that the allsky camera with the RPiHQ camera is now fully operational, running Bullseye OS on an RPi4.,....
Thank you to everyone who gave ideas and pointers...
I am once again struggling with the setup....
I updated the software to the newest version but when i reboot the RPi the liveview screen is totally blank...