# emonTX using ESP8266 Huzzah WIFI - Strange numbers **URL:** \ **Category:** emonTx\ **Created:** [23 June 2020 00:26 UTC](https://community.openenergymonitor.org/t/emontx-using-esp8266-huzzah-wifi-strange-numbers/14599 "2020-06-23T00:26:32Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![Robert.Wall](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/robert.wall/32/38246_2.png) [@Robert.Wall](https://community.openenergymonitor.org/u/Robert.Wall)\ **Post date:** [23 June 2020 20:51 UTC](https://community.openenergymonitor.org/t/emontx-using-esp8266-huzzah-wifi-strange-numbers/14599/14 "2020-06-23T20:51:29Z")
Look at the documentation for the library. That tells you what data type is returned by the “get” API call. You can download the documentation - it’s included in the .zip file - here: > [@EmonLibCM - Version 2.2.2](https://community.openenergymonitor.org/t/emonlibcm-version-2-03/9241): > > EmonLibCM is a Continuous Monitoring alternative to EmonLib. Whereas emonLib repeats, every 5 or 10 s, a sequence of voltage and current measurements in each of the input channels for a short period, normally 200 ms, and then reports the measurements back to the sketch for onwards transmission to (for example) emonCMS; emonLibCM continuously measures in the background the voltage and all the current input channels in turn, calculates a true average quantity for each and then informs the sketch t… You don’t need, but can have “signed”. See Kernighan & Ritchie, 2nd Ed, Appendix A8.2, page 211. --- _[View the full topic](https://community.openenergymonitor.org/t/emontx-using-esp8266-huzzah-wifi-strange-numbers/14599)._