Stallguard functionality

[Jrimmer95]

Hi there,

I was just reading though the user guide after putting together a DIY box and I noticed the following message:

The sensor that normally detects the closed end (called “StallGuard”) is not working in this version of the firmware. During homing the motor will NOT stop by itself. You must watch the curtain and press Stop the moment it reaches the fully-closed position. If you do not stop it, the motor will keep running and strain against the stop. Always stay with the device while homing.

Is this feature being implemented and will be available in the future?

[DeepuCodesss]

From the wording in the user guide, it sounds like StallGuard support is currently disabled/not available in this firmware version rather than being fully implemented yet.

I couldn't find a clear indication that it is already on the roadmap. It would be useful to know whether the StallGuard sensor is supported by the current hardware but just disabled in firmware, or whether there are hardware/firmware changes still needed.

If the hardware already supports it, I imagine implementing it would mainly involve reading the StallGuard signal during homing and using it as the stop condition, with a fallback/manual stop option for safety.

Is there already an issue or planned work for this, or would a feature request be appropriate?

[daniel-frenkel]

StallGuard functionality is there, just not enabled out of the box. Unfortunately I don't think it will ever be a standard feature and will always be an advanced feature that someone can play with.

The easiest way to hone your device right now is to press the close button 7 times very fast and when it reaches the close position, press it again to stop and make it home.

The problem with StallGuard is that it needs to be tuned to everyone's parameters, which includes the amount of force a curtain needs to move. So let's say one persons curtain needs 5lbs of force to move and another persons needs 10lbs. Those require 2 completely different StallGuard values. And without a closed loop motor and end stops, there's no way for the ESP to know if the device has stalled. So there's no way to automatically have the device figure out which values to set. That means a person must set them, and that takes some knowledge and trial and error to get right.

[Jrimmer95]

Thanks for the response I was just looking into the yaml directly and noticed comments you had left in there. I'll go have a play with configuring this myself and see how it goes. Awesome project by the way!

[daniel-frenkel]

The wiki should have some good info on it. And if that doesn’t work, have Claude look at the repo and wiki and it’ll get you squared away. I spent a lot of time trying to get it to work and finally realized that as long as the motor is open loop, it’s impossible to make a universal calibration routine. If the wiki doesn’t have much info please let me know and I’ll update it.Also be sure you’re on the latest firmware by pressing the update firmware button on the config page.On Aug 9, 2026, at 7:56 PM, Jrimmer95 ***@***.***> wrote: Thanks for the response I was just looking into the yaml directly and noticed comments you had left in there. I'll go have a play with configuring this myself and see how it goes. Awesome project by the way! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>