You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a graph of 03 values, which are showing as "o3" : 0343853 in the mqtt messages are all being rounded to 0.
The DB shows the definition of 03 as REAL.
Describe the bug
A clear and concise description of what the bug is.
I'm expecting the graph to automatically generate the correct Y axis and scale appropriately.
The definition initially was set as:
[[o3Chart]]
title = O3 Concentration ppm
[[[o3]]]
yAxis_label = "Parts Per Million"
yAxis_label_unit = "ppm"
I've just now (before I wrote this bug report) tried adding the following to see if it changes the display.
Please don't delete these questions! They are asked almost with every issue - answering them as below saves us time from asking them!
First step
Try to debug the skin yourself. If you can't figure it out, please include the debug information (text, screenshots, etc.). See this guide on debugging the skin. https://github.com/poblabs/weewx-belchertown#how-to-use-debug
For a graph of 03 values, which are showing as "o3" : 0343853 in the mqtt messages are all being rounded to 0.
The DB shows the definition of 03 as REAL.
Describe the bug
A clear and concise description of what the bug is.
I'm expecting the graph to automatically generate the correct Y axis and scale appropriately.
The definition initially was set as:
[[o3Chart]]
title = O3 Concentration ppm
[[[o3]]]
yAxis_label = "Parts Per Million"
yAxis_label_unit = "ppm"
I've just now (before I wrote this bug report) tried adding the following to see if it changes the display.
It changed the scale but still seeing just 0s
The DB does seem to show values other than 0
Link to your website (IMPORTANT)
https://www.baugh.org/weewx/belchertown/graphs/?graph=airQuality
Version of the skin you're using
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Device Information (please complete the following information):
Additional context
Add any other context about the problem here. Maybe a potential fix?
HELP WANTED
If you have a fix for this, please submit a pull request against the development branch!
The text was updated successfully, but these errors were encountered: