IoT with AME: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
* [[MQTT]] - A protocol that connects IoT devices | * [[MQTT]] - A protocol that connects IoT devices | ||
* [[Stacks]] - Software and Hardware | * [[Stacks]] - Software and Hardware for building AME IoT devices | ||
* [[Tools]] - Tool for programming, monitoring | * [[Tools]] - Tool for programming Arduinos, monitoring MQTT communications | ||
* [[Naming and Behavioral Conventions]] - A scheme for devices, topics, and payloads | * [[Naming and Behavioral Conventions]] - A scheme for IoT devices, topics, and payloads | ||
* [[Pitfalls]] | * [[Pitfalls]] - Things that can go wrong, and how to address them | ||
** [[Pitfalls-power_lan|Fun with power LAN adapters]] | ** [[Pitfalls-power_lan|Fun with power LAN adapters]] | ||
** | ** [[C++ is not Java]] (ie, returning pointers to method-scope variables) | ||
* Challenges | * Challenges - How to overcome hardware and software limitations | ||
** Updating device configuration (ie, MQTT/ WLAN) | ** Updating device configuration (ie, MQTT/ WLAN) | ||
** Updating device code | ** Updating device code | ||
Revision as of 12:06, 3 July 2017
IoT with AME - The Internet of things, with Arduino, MQTT, and ESP8266
- MQTT - A protocol that connects IoT devices
- Stacks - Software and Hardware for building AME IoT devices
- Tools - Tool for programming Arduinos, monitoring MQTT communications
- Naming and Behavioral Conventions - A scheme for IoT devices, topics, and payloads
- Pitfalls - Things that can go wrong, and how to address them
- Fun with power LAN adapters
- C++ is not Java (ie, returning pointers to method-scope variables)
- Challenges - How to overcome hardware and software limitations
- Updating device configuration (ie, MQTT/ WLAN)
- Updating device code