# Is there a way to reset a filament motion sensor after it triggers?

**URL:** <https://klipper.discourse.group/t/is-there-a-way-to-reset-a-filament-motion-sensor-after-it-triggers/3763>\
**Category:** General Discussion\
**Created:** [August 8, 2022, 1:55am UTC](https://klipper.discourse.group/t/is-there-a-way-to-reset-a-filament-motion-sensor-after-it-triggers/3763 "2022-08-08T01:55:53Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![azab2c](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/azab2c/32/5430_2.png) [@azab2c](https://klipper.discourse.group/u/azab2c)\
**Post date:** [June 22, 2023, 1:08am UTC](https://klipper.discourse.group/t/is-there-a-way-to-reset-a-filament-motion-sensor-after-it-triggers/3763/17 "2023-06-22T01:08:07Z")

</div>

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.

> [@horatio1989](#):
>
> I have configured the sensor as per this page: [Setup a BTT Smart Filament Sensor | Voron Documentation](https://docs.vorondesign.com/community/howto/samwiseg0/btt_smart_filament_sensor.html)

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.

![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/2/2487569bb0c4ecc816dbb3603121c7cc8c387360.png)

Shared [[filament\_motion\_sensor SFS\_T0]](https://github.com/aaronse/v1engineering-mods/blob/main/mp3dp-v4/klipper/printer.cfg#LL142C1-L142C1) section within my printer.cfg.

Klippy.log contains…

```auto
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](https://github.com/Klipper3d/klipper/blob/d32a83345518f4bb632bef9ca2de669b35f0e555/klippy/extras/filament_switch_sensor.py#L84)) …

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/b/b66110522ecdf0b533c47ee9f2176a168581bfc5.png)

Um, runout event only fired if is\_printing is true?

---

_[View the full topic](https://klipper.discourse.group/t/is-there-a-way-to-reset-a-filament-motion-sensor-after-it-triggers/3763)._