Brewblox assistence


#61

Have done another brewblox-ctl, this time was clean with no errors.
However using Safari I can’t get past this on the service tab.

Screen Shot 2019-03-08 at 9.57.23 AM
All is okay via the dash board tab, works perfectly on Chrome.
Still only 4hrs of graph.

Thanks again for your efforts

Dave.


#62

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.


#63

As j1616s said: you control the data period in the form, not by scrolling in the graph.

If you open the network console in safari, and refresh the page, do you see any errors or failed requests?


#64

Okay graph setting is this

Screen Shot 2019-03-08 at 3.46.46 PM

My assumption was it would display all data from said date to now, similar to the old brewpi graph. But I only get this … i.e. 4hrs worth.

Screen Shot 2019-03-08 at 3.49.06 PM

Console result on page refresh …

Screen Shot 2019-03-08 at 3.46.08 PM

Thanks again for your patience


#65

And another but all displayed on Safari?

Screen Shot 2019-03-08 at 7.14.24 PM


#66

Your services look good. Another problem may be that history failed to configure during setup.

On your raspberry, try running

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{ "query": "show continuous queries" }' 'https://localhost/history/_debug/query'

If the output looks like https://termbin.com/4yd6, the original configure call failed, and you can run the following to fix it:

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' 'https://localhost/history/query/configure'

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.


#67

Whats the best way to replicate the fridge constant feature using brewblox?


#68

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.


#69

Thanks Bob,

Sorted.

Screen Shot 2019-03-10 at 9.21.07 AM


#70

How do i add the onewire valve expansion boards to Brewblox? What block?


#71

Does the DS2413 block work?


#72

No, i get nothing in the block list (i might be doing something wrong). The board sais DS2408 on the back if that helps.


#73

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.


#74

Ok thanks for replying, is there anywhere we can follow the progress of the backlog?


#75

We use Github issues. You can view the combined dashboard at https://waffle.io/BrewBlox/waffle.

  • Inbox contains everything that we haven’t committed to, but haven’t explicitly nixed either.
  • Backlog is all the stuff we’re pretty sure we want to implement.
  • Next is (surprise) everything next up.
  • Done means the issue is merged into develop. We aim to push develop onto edge about once a week, but those processes are still evolving.

Feel free to submit issues for any feature requests or bugs you encounter.


#76

Very nice indeed, bookmarked :slight_smile:


#77

Need a little more info. Driven Process Value?


#78

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.


#79

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.


#80

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.