Replies: 5 comments 3 replies
|
Thanks, I am still testing this release so feedback is very useful. Did you use a username other than 'pi'? I suspect I broke the docs so will do a full reinstall on Trixie and see what happens Thanks Alex |
|
Just did a fresh install of v2025.xx.xx in 64 bit Trixie lite using 'alex' as the user
Following 1st reboot after installation it does indeed say you need to reboot - I'll add that to the list The documentation link is also wrong, I have added that to the list That would imply that it didn't initialise the database during installation. Could you please upload the support info as that may provide some clues. For reference I am tracking the issues here |
|
Yes, the install script may add the user to the groups, but the very first thing the documentation tells you do is rpicam-still --list-cameras. If the user isn't in the video group or run as root, the command will fail. You should mention that in the docs. |
|
Here's the support file. |
|
Just flashed a Trixie 64 bit lite using the Pi Imager, user name Alex The video group has already been added to the alex user so rpicam-still works fine for me, Have you seen a circumstance where it is not? I have sorted the documentation link for the installation and the reboot message Thanks for the support info, I think I need to add some more logging around the database code as it doesnt really indicate if there was an issue. If you look in the main settings at the 'Allsky database settings' Is the 'database' field populated? NOTE: Dont try and install v2025.xx.xx yet as I have broken the module installation and cannot fix it until tomorrow Alex |
Uh oh!
There was an error while loading. Please reload this page.
I just installed the v2025.xx.xx version of allsky onto a new Raspberry Pi 5 running trixie. I've hit a number of issues.
The allsky user needs to be a member of the video group in order for rpicam-still in order to access the camera. Should probably mention that adding i2c and gpio groups should be done if you’re adding sensors and the like to the allsky camera.
At the end of installation, it prompts to reboot. If you select yes, it’ll reboot, but the allsky software comes up with the system message Status: Stopped - reboot needed even though it already did the reboot. I’m guessing the status should be that configuration needs review before the software can be started.
After bringing up the allsky software, I tried viewing the updated documentation that’s installed. In the Allsky documentation Home tab, it links to an installation guide linked to hostname/allsky_guide/allsky.html, which doesn’t exist and results in a 404. The link should be to hostname/docs/allsky_guide/allsky.html
After starting the allsky software, the System Messages tab displays the following errors:
***** Stopping all module processing.
ERROR: Module 'allsky_loadimage.py' failed on line 220 called from flow-runner.py line 258 - 'databasedatabase’.
Note that I haven’t configure any modules yet.
I’m just starting to play with the new release, so if I find other issues, I’ll update here.
Alex
All reactions