I read you have an emonBase but there is no mention of the software you are using.
What Robert says about a single byte stream is correct for the journey to the emonBase. A similar situation applies to any data being passed via http from emonhub to emoncms. But on the emonSD image the data is passed from emonhub to emoncms via individual MQTT topics, however in real terms the “batch” of data values are all processed in the same way, at the same time and there is generally no noticeable difference between them.
I previously outlined the expected behavior of having 60s data saved to a 10s feed, this has come up many times and the symptoms are usually the same, data missing in one (or more) feeds but rarely all from the same packet.
The influences in whether a graph will plot with or without missing data will depend on when the feed was created and when the graphing query is run.
The feed start times are not linked or sync’d and when the data is saved it is at multiples of the fixed interval (10s) from the start time, regardless of the actual time received. Those 10s timeslots can be filled with data or set to
Every time your 60s data lands it is creating a hole of 5
null datapoints in the 10s feed and only occupying every 6th datapoint.
Whether there is anything peculiar occurring to the humidity feed alone or not, we wouldn’t be able to tell without looking at the raw csv because we cannot rely on the data shown in the graphs, it is expected to be inconsistent in this instance.
Something else that just occurred to me that you could test for. I believe the graph start, stop and sample times might be linked to the first selected feed, so try selecting the feeds in a different order or individually in separate windows, I’m not sure of this so it’s unlikely to firmly prove anything, but if you manage to stumble across a combination that shows the humidity in a good light and/or one of the others with more missing data, it may help.
In short, as Robert says you need to recreate the emonTH feeds with a 60s fixed interval, the sooner you do, the sooner you will start accumulating historic data again and we can revisit this to check for any further abnormalities to the humidity feed. The longer you leave it the more data historic you are discarding.
The new feeds will consume 1/6th of the disk space of the old ones with no loss of resolution.