gberl001 / coffee_monitor_site Goto Github PK

Not sure if this means the logs should move to the database (probably not a bad idea) or if I just serve up the raw text logs on a page but I'd like to read the logs from the website so I don't need to SSH in to do so.

Will have to wait for the events feature to be added but I would like to see the current brew's age on the website. #6 #5

Use existing database logs to simulate an actual scenario, at the very least just have a CSV of fake generated data to use as the readings and test certain scenarios so you don't need the entire scale system when debugging/testing.

This is a very minor issue but for whatever reason, within the first x seconds of when the network connection is made, the hostname command used to print the IP address prints a hex string with it even though it's supposed to delimit on spaces and only grab the first field.

ex. output:
172.20.10.4 2600:1017:b113:a47f:a765:97ce:d9d5:67bb

Not specific to the Coffee Monitor Site but add a cron job that periodically checks for connectivity, when there is none, try to connect.

It would seem the Raspberry pi only initially looks for wifi on startup and will continue to do so until connected. Once that initial connection ends it never looks for connection again so a reboot is necessary.

There are commands (need to find which ones) that can force wlan0 to look for a connection. (wicd didn't work, couldn't connect to wifi over wicd)

In most cases, when an error is encountered the server simply shuts down. Need to handle errors better, more specifically the mysql commands seem to be a more common issue.

The branch is in but for whatever reason it isn't working, need to test and figure out why.

Since 90%+ users will be using mobile, the chart needs to be focused on mobile usage.

If we use the previously added offset recordings to get an average of what the offset should be, we should be able to avoid needing to start the scale with nothing on it.

Needs to be thoroughly tested as I'm not sure what the chances are that the offset would change for any reason such as if the tile is reseated, will that throw the values off?

I guess you could add some code to use the average offset, take a reading to guess whether something is on the scale, if it's not then tare the scale and record the value so we can continue to log offset values.

I want to be able to reset the service from the website so I don't have to SSH in to do it.

Currently using Flask to host charts but it's a lot of overhead for just wanting a simple dashboard to display.

Update the charts to use something with less overhead, just a simple one page dashboard will do for serving to end users.

Store information in the database regarding details about the weight constants so we can display the number of cups remaining.

Would also like to record the time since last brew but that will have to wait for the events feature to be added.

Currently there is an IT ticket in to try and help get the Pi connected to Internet782.

It might be worth trying a WiFi dongle. Reason being, I am able to connect over an ESP32 module but not the Raspberry Pi. My guess is that IT is blacklisting the Rasberry Pi Mac prefix so a wifi dongle should have a different mac address and might connect more easily.

when ping slack fails the whole program stops.

A ConnectionError exception is thrown so that will need to be caught and then simply logged.