Ask here for assistance on configuring anything

[Winston-Lu]

SegmentWiringOrder is a bit of a mess, but its here to provide flexibility for many different (possibly existing) setups without hardcoding anything specific to any values. If you need any assistance with configuring anything, feel free to ask here

[xkeeevx]

First of all - awesome work! But I've trouble configuring the LEDs with the default wiring of the original project:
https://lirp.cdn-website.com/65e30418/dms3rep/multi/opt/wiring+diagram+1-1920w.jpeg

Also the downlighters have their own data channel.

Can you assist my configuring the LEDs right?

Best Regards!

[Winston-Lu]

For your config, you would need to change the following in Config.h under the #ifdef _12_HR_CLOCK:

const int PROGMEM segmentWiringOrder[] = {-13, -6, 12,19, 26, -32, -25, -11, -4, 10, 17, 24, -30, -23, -9, -2, 8, 15, 22, -28 ,-21, 7, 20, 1,3,5,14,16,18,27,29,31};

Where the last 9 numbers are just so the code won't go out of bounds and instead pushes to LED's that dont exist. This is just a way to work around the fact that the design of the code was intended for 32 segments instead of the original 23.

Also change the following line assuming you went with the original wiring order as well:

const int PROGMEM spotlightWiringOrder[] = {5,4,3,2,1,0,6,7,8,9,10,11};

The code will need a refactor to handle having a separate data line for spotlights. I'll add in a feature to implement this as a config option.

[Winston-Lu]

Just pushed a commit but is untested since I dont have the setup for it. I confirmed it does compile, so uncomment define SPOTLIGHTPIN 5 to enable the dedicated spotlight pin. If there are any bugs in this setup feel free to submit a report under the 'Issues' tab

[OniLink57]

Hello,

First, thank you for your work. I'm gonna use the DIY design too to have fewer LEDS. What interest me the most in your project is the ability to change the hour OTA, because I'm in France and we change the hour twice a year... So it's gonna be 24H format.

At first, I tried to use the 12H format (I didn't connect the LEDS yet, I just wanted to try it the code worked and if I was able to reach the page). It works well. I can reach the server.

So I tried to configure for the 24H format. I modified the config.js file and the Config.h like this :
`//Clock format

//#define _12_HR_CLOCK

#define _24_HR_CLOCK`

The problem is when I try to compile the code, I get the error :
"In file included from D:\Mes documents\Arduino\Projets\LED_Clock\LED_Clock.ino:2:
Config.h:117:20: error: #elif with no expression
117 | #elif _24_HR_CLOCK
| ^
In file included from D:\Mes documents\Arduino\Projets\LED_Clock\Lighting.h:5,
from D:\Mes documents\Arduino\Projets\LED_Clock\LED_Clock.ino:4:
Config.h:117:20: error: #elif with no expression
117 | #elif _24_HR_CLOCK
| ^
In file included from D:\Mes documents\Arduino\Projets\LED_Clock\LED_Clock.ino:4:
Lighting.h:153:19: error: #elif with no expression
153 | #elif _24_HR_CLOCK
"

So there is a problem with the #elif expression, but I don't know why. Am I making a mistake somewhere ? It seems simple but I can't get it to work.

[Winston-Lu]

I pushed a new commit to see if it could be something wrong with loading an unexpected EEPROM value. In the config.h line 29, uncomment the following line: //#define RESET_EEPROM. If the problem still persists, see if you can paste the entire serial output here after pressing the reset button, as well as uploading your config.h file here since I am currently unable to reproduce the issue on my device.

[OniLink57]

It seems to work now :)
At first I tried to upload the program, still the same error. Then I uncommented //#define RESET_EEPROM as you said, and I worked fine ! Can you tell me why it was needed ? It worked fine without it in 12H format !

Well now I have to build the shelves ! I still need to print 22 of them. I already have the supports so I'll screw them and then I'll solder the LEDS. Then I'll try !

At first I'll try without the 2 "sacrified" LED and if it blinks I'll solder them.

Thanks again for your help. I'll come back to tell you if everything works !

[Winston-Lu]

Not quite sure myself really, seeing as 416 as a UTC offset was a bit odd, probably something with the NTP time library. I figured that if something with the time call was off, I'd try to see any small changes would fix it.

As with the sacrificial LED's, only 1 is recommended, not 2. It flashes on mine, which might ruin a bit of the style, but doesn't really flash until it decides to synchronize with the NTP time server. In the meantime, you can go to the webserver and set your UTC offset at the bottom in the Commands section and put in the command utcoffset 1 for France's time offset. I look forward to seeing the end result since I don't have a setup for 24hr and haven't fully tested it yet

[OniLink57]

I was talking about 2 sacrificial LEDS because I'm going like DIY machines : 1 pin for the hour and 1 pin for the spotlights.

[Winston-Lu]

Oh right — forgot that my own code does that for the dedicated spotlight pin too

[OniLink57]

Hello there,

I almost finished soldering all the digits (running out of wires for the spots... I ordered some on Amazon...)

I was looking at the program to change the wiring order and I have a question : why are some numbers positive and other negative (with a minus before them) ? I think that I need to know that to make it work haha

[Winston-Lu]

Positive numbers represent that you've wired the LED's such that the next LED is to the right or below. Negative numbers means the next LED is either moving up or to the left. Mixing up positive and negative wont affect single-colour segments, but effects such as rain, rainbow, and a couple other animations will be affected as the animation will be moving in the wrong direction.

For example, the rainbow effect moves from top left to bottom right. A horizontal segment would change from red on the left to purple on the right. However, if you wired it from right to left, it should be the purple colour first, then the red on the last:
Red(1) -> Orange(2) -> Yellow(3) -> Green(4) -> Blue(5) -> Purple(6)
If you wired it the other direction (which I did to save wire), you may have some segments that go right to left
Red(6) <- Orange(5) <- Yellow(4) <- Green(3) <- Blue(2) <- Purple(1)

So because of that, the negative number compensates for the wiring direction that segment and flips it so that any effects will still run properly. Additionally, the wiring index will start at 1 instead of 0 since there is no positive/negative zero.

[OniLink57]

Hello :)

I wired my LEDS ! it seems to work just fine. Buuut.... I changed the wiring settings on the program. I works just fine. The animation when the program "loads" is well rendered (a circle basically) and then... nothing. So I tried to look at the console and same bug as before...

Setting up Wi-Fi
.....
mDNS set up. You can connect to ledshelf.local to connect instead of the IP
Showing lights
Initializing real-time clock...
UTC Offset: 0

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Exception (9):
epc1=0x4021cd00 epc2=0x00000000 epc3=0x00000000 excvaddr=0xffffffff depc=0x00000000

stack>>>

ctx: cont
sp: 3ffffda0 end: 3fffffc0 offset: 0190
3fffff30: 00000000 000d000f 00000000 00000000
3fffff40: 3fff04b0 3fffff8c 3fff04b0 40212330
3fffff50: 3fff03e8 3fffff8c 3fff04b0 4020a1ad
3fffff60: 3fff03e8 3fffff8c 3fff04b0 4020553e
3fffff70: 3fff1780 3fff1774 3fff03c8 4020f878
3fffff80: 00000000 feefef00 00000000 00000000
3fffff90: 74682e78 00000000 feefeffe feefeffe
3fffffa0: 3fffdad0 00000000 3fff0630 40219a34
3fffffb0: feefeffe feefeffe 3ffe85f4 40100ef5
<<<stack<<<

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3460, room 16
tail 4
chksum 0xcc
load 0x3fff20b8, len 40, room 4
tail 4
chksum 0xc9
csum 0xc9
v0005fba0
~ld

RESETTING EEPROM TO 0'S. ALL EEPROM SETTINGS WILL BE WIPED
EEPROM data:
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Initializing data structures for lighting effects
Setting options to default settings
Storing to EEPROM:
Done storing to EEPROM up to 0x4e
Done initializing lighting data
LittleFS contents:
FS File: config.js, size: 332
FS File: css, size: 0
FS File: img, size: 0
FS File: index.html, size: 5920
FS File: js, size: 0

As you can see, the EEPROM gets cleaned but it still doesn't work... Maybe last time was just lucky ? I don't know...

[OniLink57]

I just had an idea to automate the clock brightness without the sensor. We could sens HTTP requests to the clock to update its settings right ? It's basically what the webserver does ? I use Home Assistant and I have a light sensor outside my home. I could make an automation to send HTTP to the clock with the settings I want but I don't know at all how to do that. I don't know what is sent to the ESP when we change a setting.
I see in the code :

   webServer.on("/brightness", HTTP_GET, []() {
    setSegmentBrightness((byte)webServer.arg("value").toInt());
    lightingChanges.segmentBrightness = true;
    lastUpdate = 0;
    updateSettings = true;
    webServer.send(200, "text/plain", "1");
  });

But I don't know what is sent to the ESP when I change the brightness.

Edit : I tried http://ip/brightness and it sets the brightness to 0. I tried brightness=50 for exemple but it doesn't work.

[Winston-Lu]

Clock brightness should work without the sensor. You just need to move the slider and it should change how bright it appears. What happens is everytime the slider changes, it makes that GET request to the ESP like: GET /brightness?value=255. While you can type that into the address bar like http://ip/brightness?value=255 for full brightness and http://ip/brightness?value=0 to turn the clock off completely. To change the values, you can look here:

For some stuff like setting colours, the request will be like http://ip/spotcolor?value=12&red=255&green=255&blue=255 where value is the index position (background primary colour has value = 0, background secondary colour has value 1, the first spotlight has value=0, the 5th is value=4, red, green, and blue should be self-explanatory). If you don't know which one is what, you can press F12, go into the console on desktop, and click on what you want to change and it will give you an example GET request

[OniLink57]

The slider works well no problem about it. I wanted to get the HTTP requests because I can tell Home Assistant to send GET requests to the clock to automate the brightness without the brightness sensor. For exemple, if the outside brightness reach less than 100 lux, I could set the clock brightness to 50. Or if I shut down my living room lights, it could set the brightness to 5. I'll try to do that ! Thank you for the request form !

[OniLink57]

Hello,

Today, I configured home assistant for the clock. Now I'm able to change every digit color, the brightness of the clock, the effect of the clock or turn it on or off from home assistant !
Maybe I'll do the spotlights later but it already took me a lot of time only for the clock. Now I can automate it. The brightness depends of the moment of the day. If I'm away from home or at night, it just shuts down.

[Winston-Lu]

That sounds amazing, it seems like you dont need the photoresistor at all at this point