Open Source C++ IoT Software for Windows

ESPHome is a system for defining and deploying custom firmware to ESP8266 and ESP32 microcontrollers for smart home automation. Using a simple YAML configuration, users can specify how sensors, switches, and devices should behave, and ESPHome compiles and flashes the firmware accordingly. Integrated seamlessly with Home Assistant, ESPHome is ideal for DIY home automation enthusiasts who want full control over their IoT devices.

A versatile test tool running on Windows/Linux/macOS/Android. Works as data transceiver/realtime plotter/shortcut/file transceiver. Supports serial port, Bluetooth SPP client/server, Bluetooth LE client, TCP client/server, UDP. Homepage: https://github.com/wh201906/SerialTest

EMQX is the world's most scalable and reliable MQTT Broker designed by EMQ. It supports 100M concurrent IoT device connections per cluster while maintaining extremely high throughput and sub-millisecond latency. EMQX boasts more than 20,000 global users from over 50 countries, connecting more than 100M IoT devices worldwide, and is trusted by over 300 customers in mission-critical IoT scenarios, including well-known brands like HPE, VMware, Verifone, SAIC Volkswagen and Ericsson. Flex to meet the demands of various industries towards digital transformation, including Connected Vehicles, Industrial IoT, Oil & Gas, Carrier, Finance, Smart Energy, and Smart Cities.

Now with IEC61850 support! This project combines existing open source projects and tools to create a very capable, mobile and cloud-friendly HMI system that can rival proprietary software. This approach makes it possible to join forces of each project (Chromium, SVG/HTML5, PHP, Lua, SQLite, Inkscape, Lib61850, OpenDNP3, Nginx, Vega, PostgreSQL, Grafana,…) to achieve a great set of open, evergreen, modular and customizable tools for building great HMIs for automation projects. This is not a toy project! It's been actually used in dozens of substations up to 230kV level and also in control centers with configurations up to 70.000 tags. Feel free to ask questions in the "Discussion" section. Help sponsoring OSHMI here https://github.com/sponsors/riclolsen. >>> Have a look also at my new SCADA project here: https://github.com/riclolsen/json-scada

The Device SDK simplifies access to the Pub/Sub functionality of the AWS IoT broker via MQTT and provides APIs to interact with Thing Shadows. The SDK has been tested to work with the AWS IoT platform to ensure the best interoperability of a device with the AWS IoT platform. The Device SDK provides functionality to create and maintain a MQTT Connection. It expects to be provided with a Network Connection class that connects and authenticates to AWS IoT using either direct TLS or WebSocket over TLS. This connection is used for any further publish operations. It also allows for subscribing to MQTT topics which will call a configurable callback function when these messages are received on these topics. This SDK implements the specific protocol for Thing Shadows to retrieve, update and delete Thing Shadows adhering to the protocol that is implemented to ensure correct versioning and support for client tokens.

Next-generation AWS IoT Client SDK for C++ using the AWS common runtime. This document provides information about the AWS IoT device SDK for C++ V2. If you have any issues or feature requests, please file an issue or pull request. This SDK is built on the AWS Common Runtime, a collection of libraries (AWS-c-common, aws-c-io, aws-c-mqtt, aws-c-http, aws-c-cal, aws-c-auth, s2n...) written in C to be cross-platform, high-performance, secure, and reliable. The libraries are bound to C++ by the AWS-crt-CPP package.

Easily collect, transform, and transfer vehicle data to the cloud in near-real-time. AWS IoT FleetWise makes it easy and cost-effective for automakers to collect, transform, and transfer vehicle data to the cloud in near-real-time and use it to build applications with analytics and machine learning that improve vehicle quality, safety, and autonomy. Train autonomous vehicles (AVs) and advanced driver assistance systems (ADAS) with camera data collected from a fleet of production vehicles. Improve electric vehicle (EV) battery range estimates with crowdsourced environmental data, such as weather and driving conditions, from nearby vehicles. Collect select data from nearby vehicles and use it to notify drivers of changing road conditions, such as lane closures or construction. Use near real-time data to proactively detect and mitigate fleet-wide quality issues.

Async.MQTT5 is a professional, industrial-grade C++17 client built on Boost.Asio. This Client is designed for publishing or receiving messages from an MQTT 5.0 compatible Broker. Async.MQTT5 represents a comprehensive implementation of the MQTT 5.0 protocol standard, offering full support for publishing or receiving messages with QoS 0, 1, and 2. The MQTT protocol is widely utilised for communication in various real-world scenarios, primarily serving as a reliable communication protocol for data transfer to and from IoT devices. While the MQTT protocol itself is relatively straightforward, integrating it into an application can be complex, especially due to the challenging implementation of message retransmission after a disconnect/reconnect sequence. The aim of Async.MQTT5 is to provide a very simple asynchronous C++ interface for application developers. The internal Client's implementation manages network and MQTT protocol details.

OWLOS Open source network operating system for managing IoT devices: - does't require internet access or additional servers - ready to connect sensors, actuators, LCD, DHT, Stepper and other devices - does't require programming skills - built-in user interface - use web browser to access and manage your OWLOS nodes - built-in RESTful server - built-in MQTT client - at the same time WiFi access point and station, in any combination: - can be used autonomously - can work on a local network can work via the Internet can integrate with other nodes running under OWLOS - organizing an internal network. without using a servers available in source code