You have to set “Transition” below the Segments to 0,1 s. Otherwise it somehow takes this value for the delay. And yes the mod is only working with “solid” effect if you have this much LEDs, I have 782.
Thanks for your reply, I temporarily solved my problem by increasing JSON_BUFFER_SIZE from 20480 to 30720 and lowered the desired frame rate to 33 FPS. Even the effects are working well so far
@Rolfje and @pa1okz any chance to fix the user mod after the last beta 0.14.0 broke it? It seems the refactoring of the WS2812FX class from @blazoncek causes the problems. Only segments 0 and 1 lighten up, doesn’t matter if the swipe goes up or down. Thx in advance.
FYI: Animated Staircase usermod has been updated to work with upcoming 0.14.
1 Like
It does compile. And it also works.
Use @srg74 binaries if you are unable to compile yourself.
Thanks. Where do I find those binaries for ESP32 please?
Try Serg Bins for a start.
Hunting about his Github site will unearth all sorts of good possibilities.
Hi guys,
I got it all working with my ESP32 Wroom Dev board. However, I just purchased the QuinLED Dig Quad board to run 2 channels and have the fuses as well for security.
I installed 0.13.3 “Toki” just like on my other working board. The QuinLED has much less GPIOs pins. So I only can use
|GPIO15|Q1|External GPIO (can be pulled low)|
|GPIO12|Q2|External GPIO (can be pulled low)|
|GPIO_2|Q3|External GPIO (can be pulled high)|
|GPIO32|Q4|External GPIO (can be pulled high)|
I tried one HC-SR04 with Q1 and Q2 using GPIO15 as trigger and GPIO 12 as Echo. You can hear the sensor measuring with the clicking sound but no lights turn on despite having 2 segments saved as presets.
I tried to revers the Q1 and Q2 pins and no more clicking sound and when I change the settings to GPIO 12 as trigger and GPIO 15 and echo, you can hear the clicking sound again but no lights.
Then I thought maybe the trigger high and trigger low is the issue, so I connected trigger to Q1 aka GPIO15 and echo to Q4 GPIO 32 and again clicking sound but no lights.
I then thought the power supply to the HC-SR04 is the issue, so I removed the working one from my stairs which powers the other 2 working HC-SR04 but still the same issue.
I cannot figure out how to make the Dig-Quad work with the Staircase Usermod.
Any advice?
Thanks.
Nevermind. After trying 3 HC-SR04s from the batch of 12 I bought from Amazon, I was wondering why the clicking sound is not as loud as the original ones I had. So I dug out older HC-SR04 from a different project and voila, it works.
I got a batch of HC-SR04s which are not working at all. 12 of them. Who would have thought that.
@Pseudomizer I recommend you use PIR sensor SR-HC501 or SR-HC602
I did try the SR-HC501 and it was not as accurate as the HC-SR04.
My new challenge is now that I got it working with top and bottom but once I power off the extension cord powering the power supply 5V for the sensors and powering the UHP 350W 12V power supply for the Quad Dig, the ESP32 just hangs 2 out of 3 times. No lights turn on, the UI doesn’t load.
Once I unplug and plug back in the power supply for the sensors, it works. Only once I take away all power the system hangs sometimes but not always.
I checked the wiring multiple times and given that it is working as designed and only on power up it hangs occasionally, tells me that the timing of powering up the sensors is causing the ESP to hang.
Does anybody else have this issue?
It means your set-up is wrong. 
Watch out for a GPIO being held Hi or Lo on power up and stopping the ESP32 boot process.
Thanks for making this awesome usermod. I did have the ledstrips laying around a year and finally could make some time now to make the staircase lights.
But I’m running in to a problem. I think it’s something in the software. But I can’t find what.
Problem:
Only top sensor (hr sr04 ) is working. Bottom is also a (hr sr04 ) and that’s not reacting. If I change the ultrasoon sensor in wled from bottom to top and the top to bottom(gpio pins). I does the same thing. So only detecting on top sensor and no detection on bottom sensor.
Did try this with wled 14.0 and 13.1, no difference. And because of changing the gpio pins in wled, it’s not the problem high/low or a broken ultrasoon sensor. Using gpio, 14,27 top and 26,13 for bottom.
Who is putting me in the right direction?
Edit 30-12:
Problem solved, somewhere wled didn’t saved settings from the bottom sensor. But it was visual in the UI. So recompiled the staircase.h file with my pin settings. Restored the settings in wled to factory settings. Put the staircase.h to default settings. Compiled again and then I did go back to wled. The trigger pins were filled in with the gpio pins I use. But the echo pins were -1. So filled in the right gpio pin, but didn’t remember it when I did pushed save. So filled again the right gpio in and enabled the sensor and pushed save. And then wled saved it. So I did that also with the other sensor and it worked.
So it looks like it only did saved it when i did enable the sensor.
So now hooking up the sensors on the right place.
Maybe did help someone with the same problem.
Thanks, I got this working. Just wondering is there any way that i can get the PIR/Ultrasonic sensors triggers in Home assistant and use them as motion sensors for security purpose as well? I am new to WLED, not sure if mqtt can be used to get the sensors triggers in HA which are being used with WLED.
There is a Multi-Relay user mod that will publish to MQTT a “Relay state” based on a switch input.
Nothing says you actually have to attach a relay to a GPIO even if you tell the code you did.
You’d have to see how well that coexists with the Staircase usermod and/or steal/update the code yourself.
Certainly worth a look.
Just noticed the current Animated Staircase usermod already has MQTT publish for top of stair and bottom of stair sensors so you should be good to go.
Looks like that was added back in May '21 by the ubiquitous (and super) - @blazoncek 
I take all the blame. Thank you.
1 Like