IoT with AME: Difference between revisions

From IoT with AME
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:


* [[MQTT]] - A protocol for connecting IoT devices
* [[MQTT]] - A protocol for connecting IoT devices
* [[Software Stack|Software for building IoT devices]]: PubSubClient, Client-adapter, ESP8266 (out in the open) or, alternatively, AC_IOT, AC_MQTT, ACP_TCPESP8266, and AC_ESP8266 (my own stack)
* [[Software Stack|Software for building IoT devices]]: Libraries for device and capability classes, MQTT-, TCP-, WLAN-, and chip level access
* [[Software Problems]]: SoftwareSerial, memory use, debugging
* [[Software Problems]]: SoftwareSerial, memory use, debugging
* [[Hardware Stack|Hardware for building IoT devices]]: Arduino, ESP8266, additional hardware
* [[Hardware Stack|Hardware for building IoT devices]]: Arduino, ESP8266, and additional hardware
* [[Hardware Problems]]: Current spikes, flaky ESP8266 behavior
* [[Hardware Problems]]: Current spikes, flaky ESP8266 behavior
* [[Pitfalls]] - Things that can go wrong, and how to address them
* [[Pitfalls]] - Things that can go wrong, and how to address them

Revision as of 22:53, 14 June 2018

IoT with AME - The Internet of Things, with Arduino, MQTT, and ESP8266

Voltage controller (left), status LED (RGB; top), Arduino (top right), ESP8266 (bottom right, on adapter) - My standard hardware stack

This is work in progress started in June 2017 - I am in the process of typing out my experiences with IoT, Arduino, and ESP8266, as a documentation for myself and as something that might be helpful to others.


Note to self (help on MediaWiki):