@Verodin It didn't work properly for me! Wifi worked, it started with a blue nixie display, but I couldn't set the wifi to the home network and I couldn't set the time. However, there is a WLED version, it is good! It worked perfectly, the wifi was a bit hectic, but at least it worked. Smoothly, I reprogrammed from Total Commander Command line with ESPTOOL and back again! I copied this from a forum post:
So I wanted to run WLED firmware on my Elekstupe IPS clock.
I'd played with the Elekstube Official App and changed the Custom font in the clock.
This was a good place to start. It proved I could talk to the clock and provided me with the tools I required to change firmware.
I also noticed in the Official App the COM port number (13 for me) I needed to use for communications with the clock.
Once I'd installed the Elekstube Official App, I had a epstool directory.
\IPS Upload Tool\esptool
I'm going to refer to this as my "Working Directory"
First off - I backed up my original firmware
I made some mistakes along the way, but this backup go me up and running again every time.
I went to a Command Prompt and my "Working Directory" then ran the following command
NOTE: for me the Com Port was 13. Check the COM /CH340/ port in the Elekstube program.
esptool --baud 115200 --port COM13 read_flash 0x0 0x400000 ORIGINAL-fw-backup-4M.bin (Check the COM /CH340/ port in the Elekstube program.)
I used the following command to upload the ORIGINAL firmware, after my screwups.
esptool --baud 115200 --port COM13 write_flash 0x0 ORIGINAL-fw-backup-4M.bin
I got my WLED firmware from the zip file in this post.
I unzipped it into the "Working Directory".
I uploaded the Bootloader and the Firmware using the two following commands. (In Total Commander Command Line or windows CMD.exe)
esptool --baud 115200 --port COM13 write_flash 0x0 esp32_bootloader_new.bin (Check the COM /CH340/ port in the Elekstube program.)
esptool --baud 115200 --port COM13 write_flash 0x10000 elekstube_ips.bin (Check the COM /CH340/ port in the Elekstube program.)
After the reboot, Nothing appears on the Clock Display, this is expected.
But the Clock does now have a Wi-Fi access point you can connect with.
Once connected to SSID: WLED-AP P/W:wled1234 I completed the configuration of my new firmware.
Configuration details are elsewhere and will likely change with firmware revisions, so I won't cover those here.
Except to say, I used a browser to visit 192.168.1.2/edit (not really my clocks IP address)
Using that menu I "Choose File" and "Upload" my 0-9 .bpm files (all ten files), I rebooted the clock and the clock display was up and running.
I'm in no way an expert in this field, I post what I did in the hope that it points others in the correct direction with their firmware replacement journey.