Windows 10 IoT VS Zephyr RTOS

I would assume that Microsoft has some presence in these kinds of spaces as well (https://developer.microsoft.com/en-us/windows/iot/), but I find that there is a fairly low barrier to entry as far as learning how to manipulate linux well enough to build this type of functionality yourself. Or you can just as easily use the same knowledge to setup your desktop how you like it or whatever. They're the same thing... Source: almost 2 years ago

It does, but Microsoft doesn't consider that to be a "home user" use-case. Instead, in their minds, it's a use-case exclusively of interest to embedded-device system integrators: https://developer.microsoft.com/en-us/windows/iot/. - Source: Hacker News / over 2 years ago

I originally stumbled across what looks like a silver bullet device for caller ID, the Artech AD102. This is a HID device though, not serial like a USB modem and requires DLLs to use. The node-hid package looked a plausible candidate here, but it became rapidly clear that the AD102 must be switched into a kind of "open for questions" mode to get responses out of it, mandating use of the DLLs. Those DLLs are only... - Source: dev.to / about 3 years ago

I can recommend [Zephyr](https://github.com/zephyrproject-rtos/zephyr) for these things. Source: over 2 years ago

Zephyr, RIOT, NuttX are all open source RTOSes happy about contributions. Source: over 2 years ago

Microcontrollers are a good start. Boards are cheap and sensors are plentiful. You could get a yet unsupported board and port RIOT, Zephyr or NuttX. Source: over 2 years ago

Zephyr Project: Update to 2.5 or later.  Patches are available for prior supported versions. See the Zephyr security advisory for more information. Source: over 2 years ago