I happen to like the side-effect on work-life balance. Nobody will ever expect me to do a bit more work at home. When I go home, I'm totally off work. I also get paid overtime, so I'm not getting cheated at the office either.
It's also somewhat about physical hardware. Remote use of screw drivers and soldering irons is difficult.
There's no problem with work-life balance while working remote. You can even have better work-life balance as you don't need to take half a day off from work to attend to a 10-minute chore that can't be rescheduled. It needs maturity and trust on the part of the employers and the employees. You're almost boasting about calling a bug a feature.
Depending on what you mean by "a day", each commute direction is 2 to 3 hours. (or I suppose 6) You have a very long distance, or severe traffic, or something else unusual. It sounds like you would be driving over the mountains to reach a place like LA or SF.
I've been a software developer at 5 different work locations in 2 different states, but I have never commuted more than 20 minutes. Currently it is almost that if I walk, or 3 minutes if I drive.
This is because I choose small cities with affordable housing and low traffic. Big urban tech hubs are popular, but they mean you probably won't get a large property right near work.
But traffic is insanely bad in places like Bangalore and people just can’t choose to live in smaller places because 99% of the jobs in India are in places like Bangalore. The half-a-day case is much more the norm than the living-closer-to-work case in my experience.
In general, it's also embedded systems that are (a) most difficult to remotely flash and test and (b) most easy to irreversibly damage if you're not in front of them during the testing process.