Let’s think over some methods of volume detection
You can measure the volume of the mug by filling it totally full of water, then pouring out all the water into a graduated cylinder.
You could then encode this information onto an RFID or QR code sticker using a web form after which you can get the sticker sent to you using a service at heymugsy.com and put it on the mug for Mugsy to look at using a sensor attached via GPIO if there’s any left at this point. Your suggestion after all.
Volume Sticker produced using online service and graduated cylinder
You could plug in a webcam to the Raspberry Pi board and take a picture of the mug while it’s under the pour nozzle. You could make a clever little flip out design with the Raspberry Pi camera that would give Mugsy a little mustache under it’s screen I guess. I really need to look at a diagram so I can design this and send it to Matt wow. Anyway you flip this down and then snap a pic of the mug and enter in the measured volume which of course you still obtain with a graduated cylinder, using the knob. You could have a selection of mugs in the menu. You need a picture because Mugsy doesn’t have a keyboard but you could add a text description via BASH I guess.
Camera stache, menu of mugs, graduated cylinder, requires camera and stupid hard design
You could also have Mugsy fill the mug with water using yet another small pump and piece of tubing until it overflows into a tray with a liquid sensor in it. Mugsy does some math and figures out the volume using this and then beeps out a warning telling you to empty the mug and tray back into the tank before it fills your consumptible liquid vessel with coffee to the degree you desire. Full, half full, quarter full. It’ll be in fractions no doubt how many is up to Matt.
Has the benefit of being automatic but would make making a coffee very slow. Imagine the proccess!
Person puts pot bigger than tray on and water goes on the floor, requires tray and sensor
Scan the container to get it’s volume using a camera or scanner by the nozzle or something. My original suggestion
Looking through all these it seems you actually got it right the first time.
Although if laminar coffee flow (another suggestion I put in) is achieved by Matt during his next round of design this feature will be totally unnecesary. It would fill up your mug so fast there wouldn’t be any point in having a timer or volume detection. Given that the Mugsy has so many integrations though… it seems unlikely that he would make making coffee so darn fast! What would be the point of scheduling then? I only would want this feature if Matt is going to make the Mugsy drip very, very slowly.
Which he probably is!
Good coffee takes time after all
Which means I need to revise my laminar flow suggestion because when I wrote that I forgot that the water has to seep through the grounds which is the whole reason it drips and splutters in the first place! Making a very slow flow of what’s essentially very dirty water into a fine stream might be a taller order than I thought.
Something that occurred to me also
How does Mugsy know how much coffee it’s poured in this scenario?
That’s a whole other can of worms you would have to open to figure this feature out.
Additionally forcing water through the grounds too fast might make you have to redesign to not use a normal filter now that I think about it.
It’s pretty cool thinking about design because it’s so difficult to take everything into consideration. It’s very challenging!