For example, we've got the Eden buoy offline at the moment. It hasn't updated in 2 days, yet the graphs appear normal. This is related to #44 and #49. I need to make sure that when a buoy is offline it's shown to the user, and that old readings aren't pulled into the graph willy nilly.
Maybe the graph/table history should be handled in a more thorough manner. Rather than just pulling out the keys. #51 address this. When fetching data for the current 24hr one we could request just reading within the past 24hr, using the sorted set's scores for a range query. Then maybe that could be dealt with on the client side in how it's handled.
For example, we've got the Eden buoy offline at the moment. It hasn't updated in 2 days, yet the graphs appear normal. This is related to #44 and #49. I need to make sure that when a buoy is offline it's shown to the user, and that old readings aren't pulled into the graph willy nilly.
Maybe the graph/table history should be handled in a more thorough manner. Rather than just pulling out the keys. #51 address this. When fetching data for the current 24hr one we could request just reading within the past 24hr, using the sorted set's scores for a range query. Then maybe that could be dealt with on the client side in how it's handled.