Last night I updated my RasPi set-up to V8.0.4. Everything worked apart from two nodes updating through the input API.
Posting an example from a browser of the same data that has been working fine for the last 6 months gave error "NodeID must be a positive integer between 0 and 32, nodeid given was out of range". The two non working nodes have ID's of 32 and 33 and if I change them to something within the given range they work fine.
Searching through the forums I now realize that I have contravened the suggested standards for NodeID's. I don't remember why I used these NodeID's but they have worked for the last 6 months and 32 still appears to be within range. As well as a heads-up for others who may have made the same mistake a few questions:
Have I stumbled across an anomaly or are the changes intentional?
Is there any way to merge data from my old and new feeds?
Re: EmonCMS V8 NodeID's
The Node ID is a limitation of JeeLib - the library used for the RFM12B communications. If you look here: http://jeelabs.org/2011/01/14/nodes-addresses-and-interference/ you'll see that the Node ID occupies 5 bits, giving it a range of 0 - 31. All I can presume is the DST bit (indicates whether the node number relates to the Destination or the Source of the message) was being incorrectly decoded, allowing you to use nodes 32 - 63 !
Nodes 0 and 31 have special meanings, Node 0 is OOK (on/off keying) and Node 31 is for broadcast.
I'm no expert on emonCMS so I can't say whether it is possible to easily convert your old data.
Re: EmonCMS V8 NodeID's
Thanks to Robert for answering my first question. I altered the offending Node ID's and solved my second question in the process.
For anyone with the same issue I simply set up the new Node ID with a 'Log to feed' to the existing 'feed name' so that it updates to the existing Timestore file. I lost a few hours data in the process but that is a lot better than a few months worth.
Keep up the good work...