Short: Should removing filament cause dashboard displayed value to transition from detected to empty ?
Long:
Am intuitively expecting (assuming?) behavior of removing filament causing “empty” to be displayed for an active smart filament sensor.
Instead, am actually seeing “detected” continues to be displayed regardless of whether filament is subsequently removed/inserted. Enabling/Disabling the sensor makes no difference. Only restarting Klipper firmware causing sensor to show state at time of start up.
Same here.
On my Octopus v1.1, am seeing, for Diag 4, 5 or 6 that an enabled filament motion sensor will be display as “empty” (no filament detected). As expected.
Shoving filament in causes “detected” to be set and displayed. As expected.
“detected” continues to be displayed after removing filament. Unexpected.
Shared [filament_motion_sensor SFS_T0] section within my printer.cfg.
Klippy.log contains…
Filament Sensor SFS_T0: insert event detected, Time 5257.57
But no mention of subsequent removals and inserts.
From [filament_switch_sensor.py#L84(https://github.com/Klipper3d/klipper/blob/d32a83345518f4bb632bef9ca2de669b35f0e555/klippy/extras/filament_switch_sensor.py#L84) …
Um, runout event only fired if is_printing is true?