I like this idea)
Another opinion to enter in config by hold during twisting tailcap.
Sorry, I canāt do that in firmware. The brightness is determined by hardware, not firmware. So there are only three brightness settings:
- High: Power on, internal resistor off.
- Low: Power on, internal resistor on.
- Off: Power off.
It can control whether the power is on or offā¦ and whether the control chipās internal resistor is added into the circuit to reduce brightness. But it canāt control how much.
Instead of a few short menus attached to the mode they configure, at 1 to 3 items eachā¦ you would prefer one long menu with about 10 to 20 items?
At last count, there were 21 config valuesā¦ of which about half are set from a menu and half are set using some other action. The number changes over time though, as things are added and removed.
How would people configure lights which are physically incapable of this?
It uses āhold while connecting powerā for factory reset, on most lightsā¦ so it would need another way to do that. And it would need to be really easy to do, since itās a safety net for new users.
So it is not user friendly UI I see. Easy config for lite mode is big issue for ordinary user.
The idea for the simple UI is that most people wonāt have to configure itā¦ just take it out of the box and turn it on. It has no config options unless the user goes to the advanced UI.
After going to the advanced UI, theyāll be able to configure some settings for the simple UI. However, after going back to the simple UI, it will again not allow changes.
One way to do a power-on/hold the button config and reset, is to do it in 2 timeouts:
- 3 second hold to enter config mode
- 5 second hold to reset to factory
At 3 seconds, you could blink, say twice, then the user releases to get into config. If they continue to hold for 5 secs, it does the reset.
Now once you get into config, defining how it works to control 21+ settings (add all those being requested), and it gets insane not sure how this could be accomplished with an intuitive UI, accept maybe use the standard UI with the current config settings. A normal power-up sequence would have no config settings.
This might actually work out well, usability wise, and be relatively easy to implement since it uses the current UI for config settings. This is kind-of/sort-of what TK is saying above with the "simple" and "advanced" UI.
TK - I'm not so clear on this. The new voltage reading code, I assume will still be in Vers 2, do you believe it to be good enough to not need individual calibration?
I still have my older Anduril variant with added voltage calib (internal ref only for 1S battery, not voltage divider use for 2S+) and wondering if it's still useful, or are you considering adding it.
It still needs individual calibration. Itās very stable and consistent now, but if the sensor isnāt calibrated right, itāll be very consistently the wrong value.
So I have a voltage calibration function on the todo list. Itāll probably be a numeric entry menu attached to the battcheck mode.
My apologies if this has been suggested - I havenāt read through the entire thread. Iād like to see an option for the lighted switch to have a battery check option. So rather than a simple, steady blink, the switch will periodically broadcast the battery voltage.
To clarify, this would be under the current aux/switch options.
Iād like a timer mode like candle mode but with just regular brightness, maybe swap it for one of the annoying strobe modes nobody uses or likes, oh and a working muggle mode.
Iād like an Anduril feature that materializes $100 bills in the battery compartment, please. 
That isnāt too surprising. The way the button-press handling works now is definitely more efficient in terms of code space.
Thought it was worth suggesting, but it is not worth splitting the UI between lights with older and newer chips.
Thanks!
Iām adding a sunset / auto shutoff timer which works in both the ramp mode and in candle mode.
Trying to decide what the button press should be to activate it. In the old version, it was 3C to add 30 minutesā¦ but 3C is already used in ramp mode, to change the ramp style. However, there is nothing on 4C yet, because I moved the config modes.
So this gives me a few optionsā¦
- Use 4C to activate sunset timer. Also adds 30 minutes. (or maybe just 10 minutes?)
- Use 4H to activate sunset timer. Adds 10 minutes per second until the user lets go of the button. Blinks each time to make it easier to keep track of.
- Move āchange ramp styleā from 3C to 4C, and use 3C to activate sunset timer.
Canāt use 2H because thatās used for ramping down. Canāt use 3H because that does tint ramping. So 4H is the shortest hold action available.
For testing, I have it set to 4Hā¦ but Iām not sure if itās the right choice.
There should be an easy way to adjust beacon brightness. I imagine this is a useful function e.g. when having a car breakdown or worser, an accident. But then is should be easily adjustable by press & hold and double press & hold. Right now I not even have an idea how to adjust it. Iām using manual memory. And the pulses should be shorter. While at it, it should go to the other blinkies-set with memory.
4C / 4H sounds good to me. How will the config modes be activated now?
Ramp to the brightness you want, then go to beacon mode.
People have asked for the config modes to be harder to accessā¦ so Iām thinking maybe 7C.
- Ramp -> 7C -> ramp config
- Tempcheck -> 7C -> thermal config
- Battcheck -> 7C -> voltage calibration
- Off -> 7C/7H -> aux LED config
- Lockout -> 7C/7H -> aux LED config
Or perhaps 6C/6H, since thatās not used any more.
But with maybe one exception. Whatever sequence is used to go from the advanced UI to the simple UI, Iāll probably make the āholdā version of it go to the config mode for simple UIās ramp.
The details arenāt set in stone.
Yes, I know. Still limited by the upper boundary. And just double clicking to max - off - beacon wonāt give the intended result. I think this should be changed 
TK,
I vote for a shorter Sunset default. 5 minutes max, Two minutes would be even better.
Or make the initial default timeout programmable.
Just enough time to snuggle down in bed or sleeping bag.
Then extra clicks for more time if desired.
If the shortest timeout is too long, Iām not going to use it.
It needs some sort of indication that the user has activated Sunset correctly.
Also, going into Sunset, there should be no brighter blinks to blast sleepy eyes.
And Iād like Sunset to step down from whatever brightness the light is currently running at, as opposed to always dropping to a low brightness as default.
Itās easy to start the light where you want it at a useful brightness.
Starting at XX brightness - Everybody ready for bed?
Do the Sunset clicks and the ramp down starts from there.
Also Iād like a stepped down vs ramp for the fade out (an option perhaps?). Like the old Eternalight.
The steps remind me that it is going to go out and I need to be ready for that.
All the Best,
Jeff