How are you attempting to get more than 4h in the graph? Are you changing the duration in the settings menu for the graph? Using the controls on the graph itself doesn’t currently re-fetch the extra data.
Afterwards, the result from the first query should look like https://termbin.com/k5sz.
This won’t fix existing data, so you’ll have to wait a few hours to confirm the results.
If you’re working from the default BrewPi arrangement provided by the wizard, unset the “Driven process value” in the setpoint driver’s settings. This lets you manually set the fridge setpoint without the driver trying to over-ride it.
Somewhat less knowledgeable about the firmware, but valves are not yet implemented. They’re pretty high on the backlog, but I can’t make any promises about timelines.
If you use the “Classic BrewPi” Arrangement the wizard creates, or set up a dashboard as per the instructions posted on these forums some time ago, you’ll have a Setpoint Driver widget/block that sets the fridge temperature based on the beer temp & PID. There should only be one Setpoint Driver widget. This widget has a setting called “Driven Process Value” which is the setpoint the driver is setting. If you un-set this value, the setpoint driver won’t drive anything.
It’s also worth noting that you can create your own arrangement that excludes all the beer setpoint widgets/blocks. But I’m assuming you’ve followed the instructions made available so far.
or…
delete the ‘group’ setting in the ‘setpoint driver’. The block becomes ‘inactive’. Then you can use the Fridge setpoint, without the driven setpoint (formerly the beer temp). You don’t have to remember what to fill in the ‘driven process value’. To activate: fil in the group setting and the block will be active again for the driven fridge setting.