IoT with AME: Difference between revisions

From IoT with AME
Jump to navigation Jump to search
Line 3: Line 3:
==Planned content==
==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 (like, conversational state)
* [[Stacks]]
** HW stack: Arduino, ESP8266, additional hardware
** SW stack: PubSubClient, Client -adapter, ESP8266 or, alternatively, AC_MQTT & AC_ESP8266
** SW problems (SoftwareSerial, memory use, bugs)
** HW problems (current spikes, general unreliability of the ESP)
* [[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]
** [[MoquetteMon]] - Add-on to the Java OpenSource MQTT Broker [https://github.com/andsel/moquette Moquette] (shows IP, QoS, subscribed-to and published topics etc.)
* [[Naming and Behavioral Conventions]]
** MQTT-ID
** devices
** capabilities (reporting)
** topics


* [[MQTT]] - A protocol that connects IoT devices
* [[Stacks]] - Software and Hardware
* [[Tools]] - Tool for programming, monitoring
* [[Naming and Behavioral Conventions]] - A scheme for devices, topics, and payloads
* [[Pitfalls]]
* [[Pitfalls]]
** [[Pitfalls-power_lan|Fun with power LAN adapters]] (don't plug in your fridge)
** [[Pitfalls-power_lan|Fun with power LAN adapters]] (don't plug in your fridge)
** Returning pointers to method-scope variables
** Returning pointers to method-scope variables
* Challenges
* Challenges
** Updating device configuration (ie, MQTT/ WLAN)
** Updating device configuration (ie, MQTT/ WLAN)
** Updating device code
** Updating device code

Revision as of 11:44, 3 July 2017

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

Planned content

Retrieved from "http://iot.ctreber.com/index.php?title=IoT_with_AME&oldid=39"