Hmmm. There is a little catch-22 here with emoncms. I’m guessing that you defined the new node in your IoTaWatt and saved it, which started the emoncms process and started uploading the historical data.
IoTaWatt gets an acknowledgement when the data is posted to the input and moves on to the next frame. Emoncms has created new inputs but doesn’t yet have input processes defined to save the data that is streaming in. So it just gets dropped.
While this is going on, you are in Emoncms defining the input processes, It looks like you did main1 first and so from that point on, the data coming in for input1 is posted to the feed. In the time it takes you to define the input process for input2,
a day’s worth of history has arrived. The main1 data is going to the feed, but your main2 is dropped until you save the new input process list for main2. From then on, it all works as expected.
So what to do? It’s a catch-22, but you can get around it.
First, stop the Emoncms process in IoTaWatt with the STOP button in the Emoncms tab in the status display.
Now go into Emoncms and delete the inputs and feeds that were created.
Go back to IoTaWatt and START the Emoncms process. As soon as it starts, STOP it again.
The inputs should recreated in Emoncms.
Redefine the feeds. I’d suggest you also add a"Power to kWh" feed after the “log to Power”. If you add that later, Emoncms will only start posting to it from the time you add it.
START the Emoncms process in IoTaWatt. It should continue where it left off uploading history, and the data should be posted to the feeds that you defined.