moonraker warnings
Hi ,
After updating I have been getting warnings about the beacon which I gather has just been added to supported probes and it seems to be with update manager moonraker doesn't seem to be happy about it.
RATOS is up to date but hasn't been sorted it doesn't changing anything with my setup but just thought I'd let you know.
Thank you
15 Replies
Did you have beacon installed already?
Not installed at all it just come up a few nights ago after updating ratos
Yes, because it'll skip installing beacon if it's already installed, that's why i asked.. Curious. Let me verify the script.
No worries I have a euclid installed
@dsmakes did you ever run a soft or hard recovery on RatOS ? Like did it turn up "dirty" or "invalid"?
No not at all buddy
Odd.
Can i have you try this:
And paste the output
Sorry I shall have to do this tomorrow as I'm not at the printer .
I shall get back to you thank you for your help
Aight no problem 🙂
here you go Mikl
Updating RatOS device symlinks..
###### Updating whitelisted commands
###### Updating service permissions
###### Installing beacon module...
/home/pi /home/pi
Cloning into 'beacon'...
remote: Enumerating objects: 29, done.
remote: Counting objects: 100% (29/29), done.
remote: Compressing objects: 100% (25/25), done.
remote: Total 29 (delta 13), reused 17 (delta 4), pack-reused 0
Receiving objects: 100% (29/29), 34.59 KiB | 1.73 MiB/s, done.
Resolving deltas: 100% (13/13), done.
/home/pi
beacon: installing python requirements to env.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: numpy>=1.16.6 in ./klippy-env/lib/python3.9/site-packages (from -r /home/pi/beacon/requirements.txt (line 2)) (1.23.4)
beacon: registering beacon with the configurator.
###### Registering klippy extension 'beacon' with the RatOS Configurator...
{"id":null,"result":{"type":"data","data":{"json":true}}}Registered beacon successfully.
###### Installing git hooks
###### Registering klippy extension 'ratos_homing_extension' with the RatOS Configurator...
{"id":null,"result":{"type":"data","data":{"json":true}}}Registered ratos_homing_extension successfully.
###### Symlinking klippy extensions
Symlinked 4/4 extension(s):
Symlink for "gcode_shell_command.py" already exists
Symlink for "linear_movement_vibrations.py" already exists
Symlink for "ratos_homing.py" already exists
Symlink for "beacon.py" created
###### Symlinking moonraker extensions
Symlinked 1/1 extension(s):
Symlink for "timelapse.py" already exists
yes that looks to have sorted it,thank you
Yeah i think the problem was caused by a soft/hard reset, this script should run automatically each time you update RatOS, that problem should now be fixed as well 🙂
Superb thanks again
cd ..
I have the same issue. I ran the same command and it skipped installing beacon
pi@ratos:~ $ sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
Updating RatOS device symlinks..
###### Updating whitelisted commands
###### Updating service permissions
###### Installing beacon module...
beacon: beacon already installed, skipping...
###### Installing git hooks
###### Registering klippy extension 'ratos_homing_extension' with the RatOS Configurator...
{"id":null,"result":{"type":"data","data":{"json":true}}}Registered ratos_homing_extension successfully.
###### Symlinking klippy extensions
Symlinked 3/3 extension(s):
Symlink for "gcode_shell_command.py" already exists
Symlink for "ratos_homing.py" already exists
Symlink for "linear_movement_vibrations.py" already exists
###### Symlinking moonraker extensions
Symlinked 1/1 extension(s):
Symlink for "timelapse.py" already exists
I do have a becon-klipper directory
I tried installing beacon following the instruction on the beacon github
Yeah it won't install it if you already manually installed it
You should uninstall it (remember to delete ~/klipper/klippy/extras/beacon.py as well), then run ratos-update.sh again and it'll reinstall it where RatOS expects it to be and also manage the extension for you (so that you can recover it easily through the configurator if you hard reset klipper).
@renatojd2010 forgot to tag 
Ok. Thanks.