But that's still bright enough that a lot of automatic headlights don't turn on.
I know mine do turn on, even at the lowest intermittent setting. I thought I'd read somewhere that that was typical, but... maybe not?
You wouldn't want the headlights to turn on all the time when wipers are on automatic mode. Now why they don't turn on for regular modes, I'm not sure, but probably consistency: if you don't turn them on for automatic mode, but you do for regular mode, then that's going to be too confusing for the driver. Maybe they should come on when the wipers are activated in any mode and stay on for a certain number of seconds (by "stay on", I mean actively clearing the windshield, not just waiting for water to appear). But this might be too unreliable in practice?
Right now the only way to realize you don't have your lights on when you have DRLs is to realize that your gauge cluster is missing the notification that the headlights are on.
I'd wager simply adding an icon in the gauge cluster like an orange icon with a cross through it would solve a large portion of the issue as it would only rely on people noticing the active notification rather than the absence of another.
We have a ’03 VW Golf that turns the lights on when the engine starts, but requires you to turn the knob from Off via Parking lights to On to use the high beams. But then it doesn’t warn you that the lights are on when you shut the engine off. So whenever you use the high beams you’ll probably end up running the battery down afterwards because you’re not used to having to turn the lights off manually.
Bad UX was a thing before computerized dashboards.
Why not beep at me or otherwise alert me if it's night and I'm driving with my lights off? You know there's already a light sensor in the car, and there's already a way to beep at people or show them messages (oil is low, parking brake engaged, etc.)
There's a thing that beeps at me when my gas tank gets low. And there's a thing that beeps at me when my seat belt isn't fastened. So obviously it's OK to beep at me while driving. There's even a thing that beeps at me if I accidentally leave my headlights on and might drain the battery. Which is a fine thing to warn about, but surely not as important as a safety issue like driving with headlights off.
One could say that beeping at people whose headlights are off at night is not necessary because many cars (maybe most?) already have an automatic headlight mode, so the driver can just use that and the problem is solved. But that ignores one simple fact: people aren't doing it. Watch cars drive down a road at night, and it won't take long until you see someone whose headlights are off. I'd wager a lot of the time their car has an automatic headlight mode but they don't have the switch in the right position.
As computer people know from fighting server downtime, if something is important, you monitor whether it's behaving as required, and if it isn't, you alert.
My Model 3 has everything set on auto. If the car can't see, it'll turn the lights on. If it doesn't see an incoming car, it'll turn on the high beams.
After a year of driving it as my only car, I needed a second car and got a cheap ICE clunker. Having to manage lights is a PITA and basically a failure of design.
I've had instances of them not detecting my smaller, older, car properly even when straight on. It's great to get blinded on a 2 lane 55mph road at night.
Many (all?) modern cars have an auto mode for night lights but it seems to endlessly baffle people as to how they work. At some point it seems you can throw all the UX you want, some are hell bent to skip on being attentive to basic driving safety anyway.
I also see a lot of cars with brights on but no lights. I annoy the people around me by asking them the difference between brights and lights and the answers are very depressing. It seems that many people fiddle with a few buttons until they see light in front of them and then consider everything good.
This seems pretty relevant.