Node-red error with update

Hi Paul,

I have experienced situations when a 200 response has been issued but the data has not actually gone into the input. I don’t remember the exact situation, I think it was some malformed data or a timestamp issue. The http response is also not consistent across different input types which I do appreciate is difficult to fix as emonhub (I believe) looks for the ‘ok’. It has made me less than confident that a 200 really does mean all is well.

However, I’ve not handled that well so I am looking at it again. I think I will output the 200 response and leave the user to decide if it is an issue or not.

Oh and the 200 response is hardcoded in EmonCMS.

But 200 is the agreed protocol for a successful delivery, so surely if there is a problem with that, it’s more to do with the server, than the node.

IMO, users wouldn’t want to see a 200 message popping up every time a payload is sent. I certainly wouldn’t.

Maybe this is something that would benefit from further discussion in one of the node red forums, - Google groups or Slack?


Yes I don’t disagree. It is the way I’m handling it at the moment. Looking for a more elegant solution (which I suspect is simply updating the status text to say ‘http 200 response’ when that is what is received but learning about node.js http module ATM.

But that would mean that the message would be made everytime it sends data. I can’t recall any other node that does that, as they usually report by exception when there’s a problem…


I have worked on the module today and have added a number of modifications.

  • Improved the decoding of the http response to look explicitly for the JSON type response ‘success’ and the non-json response ‘ok’ (these responses can be seen by using the API help URLs)
  • Improved handling if for example, the requested server or address is incorrect or unreachable.
  • Modified the text to indicate the response and the HTTP response code.
  • Removed some warnings.
  • Added in a timeout but have not been able to test this functionality.

I’ve not tested it with

You can get the JavaScript file from here - testing and comments would be appreciated!!!

It is just the status text I am updating now, so yes it updates each time, but you never notice it if everything stays OK. (Examples of responses) Obviously, if it is not a green then you get a debug message.


That’s a much better solution Brian. I wish more nodes would make better use of ‘status text’, as it’s discrete, and doesn’t fill up the debug panel with messages.
I’m in the middle of something at the moment, but hopefully I’ll get chance to try it in the coming days.

Nice work!


1 Like

Apologies for my duh! moment on the 200 response. Not being an expert in http and it being mentioned as an issue I had assumed that it was something we would want to warn about.

The solution you’ve made looks great though, thanks Brian.

One caveat to that, if all other types of node simply show a green indicator without any message in normal situations then shouldn’t we drop the message and just show the green indicator. Having the message when there is an issue is great as it helps to debug things.




Example - MQTT nodes show text as well.

@Bramco @jvda @alexandrecuer @chrisghz @myozone

If you get a chance to try the node and see if there are any further comments. You just need to overwrite the .js file in the nodes folder and restart node-red.

Brian, we are away for the next couple of weeks, so sadly I won’t be able to test it.


Hi @borpin,

I have copied your 88-emoncms.js in folder:


using the following command


and I have restarted node-red.

… and it is working fine for me (I am using

Excellent job - thanks a lot.

There was one little thing I noticed which happened the first time you upgrade to node-red-node-emoncsm version 0.1.0: although data type is prefilled with “Legacy Processing” you must explicitly set it again to “legacy processing” and redeploy the flow to get it properly working.


Great ! just updated 88-emoncms.js and how I don’t have any errors - Thanks


Works fine here on local installed emoncms Brian.

Only observation is that if I send a malformed payload, I get the corrrect error msg, but it still shows as RC=200. Should that be expected?



Yes that is expected for the node. It goes back to my earlier comment that a 200 response code does not necessarily mean a successful data input. The 200 code is hard coded in EmonCMS, but the text that comes back is not OK or success. You should see the actual error message in the debug window.

1 Like

Are you making a PR for the node to be updated Brian?
It seems to work fine now, nice work.


1 Like

Yes I’ll do it over the weekend.

Thanks. Interesting playing with something new :smile:

1 Like

I just installed a new instance of the Emon node. and I am also getting the HTTP error in the debug pane although the data is still going to emoncms.

The data is sent in the following format :

payload = AR:100,AB:123,TT:200,SCC:355,SOC:400 …
It is a string with 31 values and is sent with the legacy processing . But I get the following :

payload: “ok”
_msgid: “c1c0c802.d04508”
topic: “http response”
rc: 200
warning: “ERROR: Http response”

as well as the following

“WARN: Time object undefined, no time set”

The node has not been updated yet, so you are still loading the same npm version.
When @borpin updates git, it should be fixed shortly thereafter.

Sorry didn’t get a chance at the weekend. I’ll get it done on Friday.