Simple IoT is collection of building blocks to help you build custom IoT systems quickly, but yet provide full flexibility to customize the system. Many features such as device communication, device update, rules, user/group management, user portal, etc. are needed for every IoT system. This project provides a solid foundation of common features so that you can focus on the specific problem you are solving.
- Simple concepts are flexible and scale well.
- There are more problems to solve than people to solve them, thus it makes sense to collaborate on the common technology pieces.
- There are a lot of IoT applications that are not Google scale (10-1000 device range).
- There is significant opportunity in the long tail of IoT, which is our focus. This is not an "enterprise" platform.
- There is value in custom solutions (programming vs drag-n-drop).
- There is value in running/owning our own platform.
- A single engineer should be able to build and deploy a custom IoT system.
- We don't need to spend gobs of time on operations. For smaller deployments, we deploy one binary to a cloud server and we are done with operations. We don't need 20 microservices when one monolith will work just fine.
- For many applications, a couple hours of down time is not the end of the world. Thus a single server that can be quickly rebuilt as needed is adequate.
- Runs in cloud and edge instances.
- Configuration changes can be made at either cloud, UI, or edge and are synchronized efficiently in any direction.
- Efficient use of network bandwidth for edge systems as most are connected via low cost cellular plans.
- Rules can run in cloud or edge devices depending on action required (sending notifications or controlling outputs).
- System supports user authentication and grouping users and devices at multiple levels.
- User interface updates to changes in real time.
IoT Systems are inherently distributed, so even though we prefer a monolith for a cloud service, we can't get around the fact that we also need to synchronize data with edge devices and user interfaces.
Simple IoT is built on simple data structures arranged in a graph that allows for very flexible configurations.
Because the core of Simple IoT is designed with flexible data structures, adding functionality and supporting new devices is usually as simple as creating your custom edge device code and modifying the UI to display and configure your device features.
Though we are focusing on smaller deployments initially, there is no reason Simple IoT can't scale to large systems by swapping out the internal database for MongoDB/Dgraph/InfluxDB/etc.
This project was developed while building real-world applications and has primarily been driven by these project requirements. This project provides
- a portal application (typically deployed in the cloud)
- packages for implementing an edge application to run on embedded Linux systems.
This example (build only tested on Linux and MacOS) shows how to run the server and send data to it:
Build Simple Iot or download the latest release:
- install Go v1.14 (newer versions will likely work) and node/npm (tested with v12 and v14)
- git clone https://github.com/simpleiot/simpleiot.git
. envsetup.sh(note space is required between
envsetup.sh. Another way to type this is
source envsetup.sh. This command populates your terminal session with all the functions defined in
Now, run the example:
- in one terminal, start server:
- open http://localhost:8080
- login with user
- login with user
- in another terminal, send some data
- using HTTP:
./siot -sendPoint "1823:t1:23.5:temp"
- using NATS:
./siot -sendPointNats "1234:v2:12.5:volt"
- (the format of the
- using HTTP:
- in a few seconds, devices should be populated in the web application
SIOT web interface screenshot
Below is a screenshot of the siot web interface with the above data.
Example 2 (send commands/files to device)
- in another terminal, start edge device example:
go run cmd/edge/main.go
- in a 3rd terminal:
- send command to device:
- send file to device:
- send command to device:
Example 3 (send data with acknowledgments from server)
./siot -sendPointNats "1234:v2:12.5:volt" -natsAck
Example 4 (send version information to server)
Hardware version information is a
Point that encodes the version information
Text field of a
./siot -sendPointText "1234::1:hwVersion
./siot -sendPointText "1234::2:osVersion
./siot -sendPointText "1234::3:appVersion
Flexible node view
Information is arranged in a flexible node/tree which allows for easy grouping of users, devices, and device attributes.
Each nodes can be expanded to edit/view attributes
Extensive support for modbus devices
Simple IoT can be configured to connect with a number of external programs/services such as Particle.io, Twilio, and Influxdb.
Additionally, command line option help can be viewed by running
Dashboard and Graphing
Although Simple IoT provides a rudimentary dashboard and device listing, it does not provide graphs yet. If you need graphs, using InfluxDb + Grafana may be a good interim solution. Contact us if you need help setting this up -- it is relatively simple.
Note, Simple IoT is under heavy development right now and APIs and database format may change. If you can't find something, it likely got moved to a different package, or renamed -- feel free to ask if you run into problems.
- edit/save device config
- device management
- dashboard showing each device and collected parameters
- REST api for devices
- particle.io support
- boltdb support
- influxdb 1.x support (removed)
- user authentication
- user accounts
- group support (assign users and devices to a group so users can only see devices they own).
- Modbus RTU pkg (both client and server)
- Command line Modbus utlity
- rules engine (conditions/consequences)
- sms notifications
- modem/network management
- NATS.io integration (WIP)
- file transfer over NATs (used for sw updates)
- efficient protocols for cellular data connections (NATs/protobuf)
- Modbus RTU support in SIOT
- Modbus TCP support in SIOT
- Twilio SMS notifications
- influxdb 2.x support
- email notifications
- COAP API for devices
- store timeseries data in bolt
- esp32 client example
- graph timeseries data
- WiFi management
Support, Contributing, etc.
Pull requests are welcome -- see development for more thoughts on architecture, tooling, etc. Issues are labelled with "help wanted" and "good first issue" if you would like to contribute to this project.
For support or to discuss this project, use one of the following options:
- Simple IoT community forum
- #simpleiot Slack channel is available on gophers.slack.com
- open a github issue
Apache Version 2.0
Package respreader provides a convenient way to frame response data from devices that use prompt/response protocols such as Modbus, other RS485 protocols, and modem AT commands.
|Package respreader provides a convenient way to frame response data from devices that use prompt/response protocols such as Modbus, other RS485 protocols, and modem AT commands.|