# ECM Control

A comprehensive system for controlling espresso coffee machines with GPIO relays, scale integration, and web-based recipe management.

## Features

- **Web Interface**: Modern HTMX-based web application for recipe management
- **GPIO Control**: Hardware integration for controlling espresso machines via relays
- **Scale Integration**: Support for Acaia scales via Bluetooth (with mock implementation for development)
- **Recipe Management**: Create and manage extraction recipes with target weight and timeout
- **Button Mapping**: Map physical buttons to specific recipes
- **Shot Logging**: Comprehensive logging of all extraction attempts with detailed metrics
- **Real-time Monitoring**: Live monitoring of extractions with automatic stopping
- **Systemd Integration**: Production-ready service configuration

## System Requirements

### Hardware
- Raspberry Pi (or compatible GPIO-enabled device)
- Relay module connected to GPIO (default: GPIO 2)
- Physical buttons connected to GPIO pins
- Acaia scale (optional, mock implementation available)

### Software
- Python 3.10+
- UV package manager
- SQLite 3

## Installation

### 1. Clone and Setup

```bash
git clone <repository-url>
cd ecm-control
```

### 2. Install Dependencies

```bash
# Install UV if not already installed
curl -LsSf https://astral.sh/uv/install.sh | sh

# Install project dependencies
uv sync
```

### 3. Initialize Database

```bash
uv run python run.py db init
```

## Usage

### Web Application

Start the web server:

```bash
uv run python run.py web --host 0.0.0.0 --port 8000
```

Access the web interface at `http://localhost:8000`

#### Web Interface Features:
- **Dashboard**: Overview of system status and recent shots
- **Recipes**: Create, edit, and delete extraction recipes
- **Buttons**: Configure physical button to recipe mappings
- **Shot History**: View detailed history of all extractions
- **Settings**: Configure scale address, thresholds, and logging levels

### GPIO Control Service

Start the GPIO control service:

```bash
# For Raspberry Pi with actual GPIO
uv run python run.py gpio

# For development/testing with mock GPIO
uv run python run.py gpio --mock
```

### Database Management

```bash
# Initialize database
uv run python run.py db init

# Reset database (WARNING: deletes all data)
uv run python run.py db reset
```

## Configuration

### Scale Configuration

1. Access the web interface
2. Go to Settings
3. Set the `scale_address` to your Acaia scale's Bluetooth MAC address
4. Configure other parameters as needed:
   - `shot_completion_threshold`: Weight change rate (g/s) to detect completion
   - `weight_stabilize_time`: Seconds to wait for weight stabilization
   - `log_level`: Logging verbosity (DEBUG, INFO, WARNING, ERROR)

### Button Configuration

1. Access the web interface
2. Go to Buttons
3. Add buttons with their GPIO pin assignments
4. Map buttons to recipes

### Recipe Creation

1. Access the web interface
2. Go to Recipes
3. Create recipes with:
   - Name
   - Target grams out
   - Timeout in seconds

## Hardware Setup

### Relay Connection

Connect a relay module to GPIO 2 (configurable). The relay should be wired to simulate the coffee machine's brew button press.

**Wiring:**
- GPIO 2 � Relay Signal
- 5V � Relay VCC
- GND � Relay GND
- Relay NO/COM � Coffee machine button circuit

### Button Connections

Connect momentary buttons between GPIO pins and ground. Use internal pull-up resistors.

**Example for 4 buttons:**
- Button 1: GPIO 17 � GND
- Button 2: GPIO 18 � GND  
- Button 3: GPIO 19 � GND
- Button 4: GPIO 20 � GND

## Production Deployment

### Systemd Service

1. Copy the service file:
```bash
sudo cp ecm-control.service /etc/systemd/system/
```

2. Update the paths in the service file to match your installation

3. Enable and start the service:
```bash
sudo systemctl daemon-reload
sudo systemctl enable ecm-control
sudo systemctl start ecm-control
```

4. Check service status:
```bash
sudo systemctl status ecm-control
```

### Web Server (Optional)

For production web deployment, consider using a reverse proxy like nginx:

```nginx
server {
    listen 80;
    server_name your-domain.com;
    
    location / {
        proxy_pass http://localhost:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}
```

## Development

### Mock Mode

For development on non-Raspberry Pi systems, use mock mode:

```bash
# Start GPIO service with mock hardware
uv run python -m ecm_control gpio --mock

# This enables:
# - Mock GPIO buttons (can be triggered via web interface)
# - Mock relay (logs actions instead of controlling hardware)
# - Mock scale (simulates weight readings)
```

### Debug Logging

Enable debug logging for detailed troubleshooting:

```bash
uv run python -m ecm_control gpio --log-level DEBUG
```

This creates detailed logs in `logs/debug.log` with:
- GPIO event timing
- Scale reading details  
- Shot phase progression
- System state changes

### Project Structure

```
ecm-control/
   src/ecm_control/
      __init__.py          # Package initialization
      __main__.py          # CLI entry point
      database/            # Database schema and management
      models/              # Pydantic data models
      web/                 # FastAPI web application
      gpio/                # GPIO control and hardware interface
      utils/               # Utilities (logging, scale management)
   templates/               # HTML templates
   static/                  # CSS/JS assets
   logs/                   # Log files
   ecm-control.service     # Systemd service file
   pyproject.toml          # Project configuration
   README.md               # This file
```

## API Reference

The web application provides REST API endpoints:

### Recipes
- `GET /recipes` - List all recipes
- `POST /recipes` - Create new recipe
- `DELETE /recipes/{id}` - Delete recipe

### Buttons  
- `GET /buttons` - List all buttons
- `POST /buttons` - Create new button
- `PUT /buttons/{id}` - Update button recipe mapping

### Shots
- `GET /shots` - List shot history

### Settings
- `GET /settings` - List all settings
- `PUT /settings/{id}` - Update setting value

## Troubleshooting

### GPIO Permissions

If you get GPIO permission errors:

```bash
sudo usermod -a -G gpio $USER
# Log out and back in
```

### Scale Connection Issues

1. Verify Bluetooth is enabled and scale is discoverable
2. Check scale MAC address in settings
3. Ensure scale is not connected to other devices
4. Check logs for connection errors

### Service Not Starting

```bash
# Check service logs
sudo journalctl -u ecm-control -f

# Check for Python path issues
sudo systemctl edit ecm-control
# Add:
# [Service]
# Environment=PYTHONPATH=/path/to/ecm-control/src
```

### Database Issues

```bash
# Reset database if corrupted
uv run python -m ecm_control db reset

# Check database permissions
ls -la ecm_control.db
```

## Contributing

1. Fork the repository
2. Create a feature branch
3. Make changes with tests
4. Update documentation
5. Submit pull request

## License

This project is licensed under the MIT License - see the LICENSE file for details.

## Acknowledgments

- Uses [pyacaia](https://github.com/lucapinello/pyacaia) for scale integration
- Built with FastAPI and HTMX for the web interface
- GPIO control via gpiozero library