will also work by putting the values in a payload that puts the “updated every send” values first with the lesser updated values at the end will allow you to just send a partial frame in between full frames.
you can see in that last link it is easy to set up a test on an unused node id and just delete the inputs afterwards.
EDIT - I just looked into why this might not work on emoncms.org and found the changes never got that far so this will only work on self hosted as the code is different
Thanks for the update. That explains why null is not working for me.
As emoncms.org does not have this feature yet I have coded in my BASH script to detect the pulse, slice of the data and post using BULK format to a separate node id. So this node id gets infrequent posts which process well into a PHPTIMESERIES feed.
I actually needed a bit of code for my pulse count values to graph well. A pulse is posted as a BULK upload with a 0 at timestamp-10s, the pulse count at timestamp and a 0 at timestamp+10s. My gas pulse rate is so slow this is OK as there is never a pulse 10s after a pulse - the smallest gap I see is 50s.
Any idea if emoncms.org is going to get the change to support nulls?