It was all working before the update.
SD card was brand new.
WIFI is pretty stable
Same power cord that came with the pi that I’ve been using.
I’ll try the clean install.
Thanks. I got it working by rewiring my setup. My previous BrewPi actuator numbers matched the digital output numbers on the Spark, but the BrewBlox assigned them differently so my unused digital output 3 was being assigned to the cool pin. Is there a way to change them to match the Spark digital outputs?
Did I mix something up? Can you explain in a bit more detail?
Released two bugfixes.
You’re seeing all values in that PID block, and apparently you’ve used both degF and degC at some point.
You can expand the PID block in the field selector to refine your selection.
It’s on the backlog to allow deleting or ignoring obsolete fields in history. Am I missing anything else?
Man you are right i did not see both degF and degC were selected, move on!.
I think the displayed measured and target values are reversed for the output row in the PID widgets. I think I’m using the latest version (Your release track is “edge” Your config version is “0.2.1”).
I checked, and you’re right: we mixed up the two properties.
Thanks for the report! We’ll have it fixed in the next release.
The graph widget keeps switching from “live: date to now” to “fixed: date to date” (or date to duration), switching back to live modes in the settings doesn’t work. It will update the duration displayed if you use a live duration, but this a) just seems to give a duration since the end date and b) has switched back to “fixed: date to date” next time you open the settings panel.
The only way to get the graph to show data after the end date is to change it to “fixed: duration since date” with a duration that stretches beyond the end date currently displayed. This will update the graph with recent data, but you still can’t switch to live modes.
Is this a known issue? If not, what further debugging information would be helpful? Separately, do you prefer bug reports here, in their own threads, or on github?
This is a new issue.
Helpful extra information would be:
- The link generated by
brewblox-ctl log - In the UI:
- open your dev tools (ctrl+shift+I on FF/chrome) .
- go to the network tab.
- toggle the settings a few times to reproduce the issue.
- right click on the network requests, and choose “save as HAR”.
- upload that file here.
While we’re happy to resolve all bugs brought to our attention, issues posted either in their own thread or on github will be easier to google for other users.
Okay. I reported an issue in the brewblox-ui repo. Hopefully that is the right one.
Updated release notes.
Regarding the instructions:
You probably know this, but many folks find that wpa_supplicant file and even the ssh file tricky. I created a small, open source, Windows-only program (since anyone with anyone else is likely not going to have an issue). You are free to link to it, distribute it, ignore me, whatever:
1 Like
That looks lovely. I’ll give it a try tomorrow, and then likely link to it.
We indeed had multiple people struggling to create an extension-less file.
Can someone please explain how to add part items to the process view.
I have created a ‘Process view’, then I go into edit mode and click on the grid to add a new part.
I select the a part (say Large Kettle). The choices then disappear but nothing shows on the grid.
If I try again to add a part it says in red “Can’t place this part here, location is blocked”.
What am I doing wrong or missing?
You should see the kettle after selecting it in the “new part” popup.
What browser are you using? And could you please export your process view (left side in edit view), and upload that file here?
It tries to place the kettle 15 units below where you click. This is probably a bug. @Bob_Steers, if you can’t easily replicate this, I’m happy to export the widget and my network activity for a bug report on github,
edit: went ahead and filed a bug here
1 Like
Must have missed and update yesterday, as it now works. I updated last night for the fix that @j616s did to his Tilit widget and now the process view works in both Safari and Chrome.
Rich
This does sound like a bug we fixed last week.
1 Like