That should be 1 (ie no cooling). Again that will change when the splitter node goes in again.
The bit of the chart that we want to see (once it is up and running) is how it cools down from ambient or at least a good number of degrees above setpoint.
How very odd, you haven't got zero for PB or Integral Time or Max Sample Interval have you? If not then I don't understand how that can happen.
My only zeros are derivative and smoothing.
An unexpected byproduct of 95% scaling is the PID, effectively, never turns off. Disabling the PID only limits the output power to 5% so while I'm trying to make it back to 65F it is adding 5% on time every ten minutes.
I'm ready for a weekend. 
Charles
With the Output Power When Disabled set to 1 (is it?) then that will go straight through the range node and the cooler should be off when the pid is disabled.
Output power when disabled is set to 1 after it goes through the range node it is 0.95
I thought that is what it is supposed to do. Maybe the scale should be 1.0 to 0 and 0.0 to 0.95?
Should be like this, so 1 maps to 1 and 0 maps to 0.95, or as configured in the node, the range 1 to 0 maps to the range 1 to 0.95
That makes a lot more sense and with PID disabled the output is to the GPIO pin is 0.
Thanks
I got influxdb installed along with grafana and I am able to reach the grafana server from my desktop. The problem is I assumed influxdb was a standard relational database like I am used to working with. Boy was I wrong.
I may have something to report after I give my brain a rest and can absorb a new database.
I did install your influxdb node and am exploring it. I think I got it connected to influxdb but not sure since grafana is not showing any data.
Hope you have a restful Sunday.
Charles
Success!
I am storing data in influxdb and graphing it in grafana across my network to my pc.
I have my retention set to one day for now and it's just a test db but it works.
I should have taken your advise first Colin. This combination is perfect for what I am doing.
The temps are pretty well equalized but I'm going to wait until tomorrow to start a trial run.
I have to pay attention to my wife for a day or two.
Can you define what the power scale is showing please.
Before I send the data to influxdb I do this math:
msg.payload = Number(1-payload);
Then in grafana I scale it to reflect our 5% limit.
Math(*100)
So the power level is on a scale of 0 to 5%.
I should probably do Math(*200) which would give me a scale of 0 to 100%
Actually the PID value is 0.9875 which is actually 0.0125 in a range of 0-0,5 so the actual percentage of power being used is 2.5%. Do you agree?
What you need to plot is the cool power as a percentage of the maximum we are allowing. To do that I would personally prefer to put the output of the PID algorithm, flipping 0 and 1, into influx, so that 0 is off and 1 is max cool (which is actually 5%, but that doesn't matter, it is still max cool). However if you prefer to put the actual cool power in that is ok, but scale the chart so that it shows 0 to .05 so that the graph shows the full range of power that we are allowing. At the bottom when there is no cool and at the top when the pid algorithm asks for max.
Lid is open and PID is disabled. Waiting for temp to rise.
Here is the graph we were talking about.
I think it's more readable and requires less monkey math.
Charles
Looks good, now we can see what the power is doing.
Ya, in if I got my retention correct the wild power lines will go away in a few hours.
Did you say you had it set to 24 hours? The problem with that is that you will not be able to look back in a few days or a week to see how it performed with certain tuning params. I generally have mine set to a year.
A typical fermenting cycle is 5 to 7 days but I sometimes go beyond that. Maybe 2 weeks? All those wild lines hurt my eyes though, I'd like to see them go. 
I'll see if I can redo retention. It was a struggle to get it to 1d.
I've only used 17% of my SD card so I guess I can afford some more storage and I may even want to look back at a previous batch to see how temp controll affected flavor.
