Read ACCELEROMETER_QUERY response in macro

[mykepredko]

@bozzo

@bozzo

try replacing sudo pip install ... with ~/klippy-env/bin/pip install ...

That did the trick, klipper-repl is now installed in ~/klippy-env/bin:

Now, I don’t have a link to the Klipper API (or Klipper itself) in the run folder:

This is important because when I try to run klipper-repl with /run/klipper/api as suggested in the klipper-repl GitHub page, I get:

Reading through the klipper-repl Discourse announcement:

Announcing klipper-repl: the missing Klipper command line

I’m happy to announce the initial release of klipper-repl, a command line frontend for Klipper that uses the same socket API as Fluidd and Mainsail to provide an efficient G-Code REPL interface. [screenshot] Its features include: Automatic reconnection if Klipper restarts or is unavailable Support for running G-Code commands as part of shell scripts Multiple G-Code commands per line – use , as a separator Syntax highlighting for both G-Code and user-defined macros Tab autocompletion for use…

I tried using printer_data/comms/klippy.sock (which is used there but got the same error as the last post in the thread):

Now, I did try restarting the Klipper API (I know I shouldn’t have bothered, but I had to try) using the command:

~/klippy-env/bin/python ~/klipper/klippy/klippy.py ~/printer_data/config/printer.cfg -a /tmp/klippy_uds -l /tmp/klippy.log`

This is from the Klipper API page:

API server - Klipper documentation

I changed the printer.cfg location to match what was in the system.

I’m guessing I’m not providing the correct link to the Klipper API Socket, but I have no idea where it is.

Any ideas for next steps?

Thanx.