-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bookoo scale and pressure sensor #855
Comments
Hello @bytelinker, Can you please elaborate more on the issue you have?
The refresh rate is already 1/10, when its 1s on your side, please check how your bluetooth-settings are: Please deactivate ignore negative anomaly/negative weight - this will be disabled in the next update. Have a good cup of coffee |
You need to use their official app.
When you tap your finger on the scale, the tile where it shows "0g" will show the change of the weight. The screenshot you're showing me, are normally telling me that everything is rightly connected and ready to use. |
Thanks. Firmware is updated for scale and pressure. The 0g is shown, but you have to know, that this is the situation for "ok". Most measuring devices like Pt100 with readout, DMM are working different. |
The scale weight is shown live in the tile, even without starting the brew. Maybe this will be tackled when we go and redesign the app but this isn't the highest priority to be honest. |
Bookoo scale and pressure sensor are present and have been working. Now connection is indifferent. When brewing, there is no time to handle connection problems. There is a pop up showing a problem, but this is closing some how. There is no clear display weather both sensor are showing live data or not. A full red big "x" symbol showing the problem and a direct re-connection button with live data as number would be good. Live data should be with so many digits that the actualization with new data can be seen from the changing last digit. Alternatively a heat beat dot is good. Hart rate shall be 1/10 s - 3/10 s. 1 s is much to slow.
The text was updated successfully, but these errors were encountered: