Well, the people that use the hundreds of other devices that don't have that issue, generally. There are too many devices out there for any one system to support every one of them to the hilt. That would be more work than even a very large company could stomach. It can only happen if the manufacturers of the devices themselves do the drivers. Though of course that also suffers from the same problems as operating systems drivers demonstrate.
Just within a single category, like A/V receivers, it's almost impossible. Companies put out variations at a stupid pace, and don't really do anything to help us create adaptable drivers that can support a wide swath of their products as is. Yamaha has recently started to get this right, allowing us to just query it for what it supports and have a single driver that can adapt to a lot of different models.
Actually the bulk of the drivers, at least for the important stuff, are written and maintained by us. Or, in some cases, they are a simple derivation of one that we wrote, to deal with some other variation of the same device. Most of the third party ones are for more peripheral type devices. We do the Elk, Omni, RA2/HW, Hue, Nest, Z-Wave, Insteon, Brultech, TTS, audio players and media repositories, Sonos, Nuvo, Amazon Echo, Harmony, Aprilaire, Plex, DSC, Weather, Tekmar, Global Cache and other IR related ones, iTunes, Russound, and other drivers of that sort that are core to lots of people's systems.
Ultimately, if customers want more peripheral drivers to be done and maintained by us, they will have to contribute bucks to it. Unlike Homeseer we don't charge for drivers, so we cannot afford to spend enormous amounts of time on drivers that will only be used by a small fraction of customers, which is ultimately most of them. Even if we did charge for them, if only a small number of customers ever use a given one, we'd still lose money.
