Archived Forum

Hi Nicolas, how are you obtaining the setpoint value? I think the problem is that you only get an input update whenever the value changes, which can result in an incomplete graph being displayed due to lack of datapoints within the selected timeframe. Is there anyway that you can get the setpoint value repeated/updated more regularly similar to the temperature feed?

As regards your second question, although I haven't tried it, you may be able to manipulate the inputs via the various processes to create the graph. This would need some experimenting and a lot of ingenuity though, depending upon your data sources.
Example, if you have an input from your heating appliance such as 'off = 0' and 'on = 1', then in your temperature input config add the function;

x input (your heating appliance input)

So if your heater was switched off, the result would always be zero, whilst if switched on, the resultant value would be the current temperature. This would then display as per your example.

My preferred option is that this could quite easily be created if you used emoncms to obtain the data, pass it to node-red via mqtt where you can manipulate and filter the data, before passing it back to emoncms again via mqtt to record as feeds and subsequent graphs.The same process could deal with your other issue too.
I had this sort of graph in mind for my system, and this is how I'm going to achieve it.

Paul

Paul, thanks for your answers.

Indeed i was pushing  the new value only when the setpoint was updated, I had in mind  to save a bit of bandwidth :). Now i'm updating all the values on the same batch. it seems better now.

As for heat values, I followed your advice and did the value transformations in my home automation application. Now it logged not only the living room temperature but also another value, product of heater state by the temperature. It should be ok, let's wait a few days to see the behaviour of the system

[2 further copies of this post deleted by moderator - (RW) ]