falkecarlsen/jvm-loss

management and statistic project for coffee vending machine Wittenburg 9100

jvm-loss's Issues

Fix database design

Apply our knowledge of DBS to this project

Pretty graphs needed

Track ingredient levels in database

Function to check if low threshold has been fixed

When a IngredientLevel type message is received, it typically specifies that a container is below the threshold. Other notifications message that a specific container has been filled.

The system should be able to check if a threshold alarm has been matched by a filling and possibly notify if some number of consumption has been used from the given container, symbolising that the alarm has not been resolved.

Database function to retrieve last entry of certain type

Implement db querys for other fields

As of right now, it is only possible to do querys based on timestamp, and not on drink type or event. Would be nice to be able to get all "coffee" or "Hot water" events

Ability to get status on ingredients by sending mail to JVM mail

Bug with failure timestamps

More functions in database for different searches

Forward low-volume mail if not acted upon

Add argument to disregard 'working-hours' on mail processing

Allows for better testing when out-of-office

Track how much water has been used

Will be used to determine when a new waterfilter is needed

Implement notification on low amount of coffee-beans

The Wittelburg 9100 supports sending email-notifications on states of contents, e.g., amount of sugar or coffee.

This could be mapped to a, e.g., Slack notification on %20 remaining coffee, to help maintenance.

Implement proper parser

Would help with running test-procedures instead of bothering with sys.argv