# Data from IoTaWatt - getting HPE\_INVALID\_CONSTANT error

**URL:** <https://discourse.nodered.org/t/data-from-iotawatt-getting-hpe-invalid-constant-error/36177>\
**Category:** Hardware\
**Created:** [19 November 2020 06:05 UTC](https://discourse.nodered.org/t/data-from-iotawatt-getting-hpe-invalid-constant-error/36177 "2020-11-19T06:05:19Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![overeasy](https://avatars.discourse-cdn.com/v4/letter/o/3d9bf3/32.png) [@overeasy](https://discourse.nodered.org/u/overeasy)\
**Post date:** [21 November 2020 15:21 UTC](https://discourse.nodered.org/t/data-from-iotawatt-getting-hpe-invalid-constant-error/36177/17 "2020-11-21T15:21:35Z")

</div>

I just tried adding keep-alive. That didn't help. But I have tried something else and have got it to work.

The older post from March had a clue with the curl response that said there was

> [@Basic Fetch Error](https://discourse.nodered.org/t/basic-fetch-error/22416/6):
>
> Leftovers after chunking: 5 bytes

This is a problem with newer ESP8266WebServer's chunking interacting with IoTaWatt's older implementation. Never bothered browsers but I'll get it fixed in a day or so. After reading through the various releases of ESP8266WebServer, it looks like they have changed it yet again but that version is not yet published to PlatformIO, so I will need to understand the implications of that.

Thanks for your efforts. I'll post back when I have resolved on my end.

It's been interesting to explore Node-Red and I think you'll be seeing more of me in the future. Nice project.

---

_[View the full topic](https://discourse.nodered.org/t/data-from-iotawatt-getting-hpe-invalid-constant-error/36177)._