IoT with AME: Difference between revisions

From IoT with AME
Jump to navigation Jump to search
m (Ctreber moved page Main Page to IoT with AME)
No edit summary
Line 1: Line 1:
IoT with AME - The Internet of things, with Arduino, MQTT, and ESP8266.
=IoT with AME - The Internet of things, with Arduino, MQTT, and ESP8266=
 
==Planned content==
 
What would I like to write about?
 
* MQTT
** finite state machine of the protocol
** most simple application (QoS 0)
** encoding and decoding
** more sophistication (QoS 1, 2), limits of the Arduino environment (session keeping)
*The Stack
** HW stack: Arduino, ESP8266, additional hardware
** SW stack: PubSubClient, Client -adapter, ESP8266 or, alternatively, A_mqtt & AC_ESP8266
** SW problems (SoftwareSerial, memory use, bugs)
** HW problems (current spikes, general unreliability of the ESP)
* Logical organization
** MQTT-ID
** devices
** capabilities (reporting)
** topics
* Tools
** AC.programmer (SPI programming, freed-up serial interface, 2k more flash mem, logging via I2C)
** Monitoring MQTT publications with [https://github.com/kamilfb/mqtt-spy MQTT-Spy]
** Augmented MQTT broker for testing (IP, QoS, subscribed-to and published topics etc.), based on [https://github.com/andsel/moquette Moquette]
* Pitfalls
** Fun with power LAN adapters (don't plug in your fridge)
** Returning pointers to method-scope variables
* Challenges
** Updating device code
** Updating device configuration (ie, MQTT/ WLAN)

Revision as of 13:38, 21 June 2017

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

Planned content

What would I like to write about?

  • MQTT
    • finite state machine of the protocol
    • most simple application (QoS 0)
    • encoding and decoding
    • more sophistication (QoS 1, 2), limits of the Arduino environment (session keeping)
  • The Stack
    • HW stack: Arduino, ESP8266, additional hardware
    • SW stack: PubSubClient, Client -adapter, ESP8266 or, alternatively, A_mqtt & AC_ESP8266
    • SW problems (SoftwareSerial, memory use, bugs)
    • HW problems (current spikes, general unreliability of the ESP)
  • Logical organization
    • MQTT-ID
    • devices
    • capabilities (reporting)
    • topics
  • Tools
    • AC.programmer (SPI programming, freed-up serial interface, 2k more flash mem, logging via I2C)
    • Monitoring MQTT publications with MQTT-Spy
    • Augmented MQTT broker for testing (IP, QoS, subscribed-to and published topics etc.), based on Moquette
  • Pitfalls
    • Fun with power LAN adapters (don't plug in your fridge)
    • Returning pointers to method-scope variables
  • Challenges
    • Updating device code
    • Updating device configuration (ie, MQTT/ WLAN)