Klipper error "code":"key69", "msg": "The value 'filament_sensor'

General Discussion
1

Basic Information:

Printer Model:Creality K1 Max
MCU / Printerboard: Creality stock board
Host / SBC

Klippy log,BTT config.zip (2.3 MB)

klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Hello, so I have a rooted Creality K1Max. I just installed a BTT smart filament sensor V2 and I have a seperate .cfg file in Mainsail for the sensor config that I have “included” in the printer.cfg file. As to the old sensor configuration in printer.cfg I have “commented out each line with # at the beginning. The sensor configuration file I’m using is one suggested for Klipper on github. When I try to initiate the auto leveling and input shaping cycle from my machine the cycle fails causing a 2069 “unknown exception” error, and I get this error on Klipper.

{“code”:“key69”, “msg”: “The value ‘filament_sensor’ is not valid for SENSOR”, “values”: [“filament_sensor”, “SENSOR”]}

I have seen a couple of references to this error code and the solutions have involved changing the configuration header name. I have played with this idea and have had no luck in solving this issue. any help would be appreciated.

2

Hi @TimA ,

I would go through your config and rename filament_motion_sensor encoder_sensor to filament_motion_sensor filament_sensor

Also, keep in mind, even though you rooted your printer, it’s still running Creality’s modded Klipper.

3

@3dcoded Thank you for your reply, your expert advice, and the recourses! Your solution worked! interesting though, after I changed the header name the error popped up again but this time With an _2 behind it. I realized that I had accidentally “commented out” a second sensor that the program was still trying to use. After re instating it I’ve tested the sensor and everything is working great.

4

Great! Could you please mark my post as the solution so other people know this has been resolved?