In examining the source code for the qs-iot example application for the EK-TM4C1294XL Connected LaunchPad and porting that code to the older EK-LM3S8962 Stellaris® LM3S8962 Ethernet+CAN Evaluation Kit board, I uncovered a couple of bugs in the qs-iot code.
1) TivaWare\examples\boards\ek-tm4c1294xl\drivers\exosite_hal_lwip.c
Line 680: the wrong size is returned
Suggest: Line 669: return the value returned by "usprintf()"
2) TivaWare\examples\boards\ek-tm4c1294xl\qs_iot\requests.c
Line 324: if "ExtractValueByAlias()" returns false (i.e. no value found for the alias), the following "StatSetVal()" blindly writes to the status item whatever was left in the "pcServerValue" string from a previous use
Suggest: Line 324: test the return from "ExtractValueByAlias()" to conditionally call "StatSetVal()"