driveeClient 0.1.0__tar.gz

driveeclient-0.1.0/.gitignore

@@ -0,0 +1,39 @@
+# Environment variables
+.env
+.env.example
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# Virtual Environment
+venv/
+env/
+ENV/
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db 

driveeclient-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Your Name
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

driveeclient-0.1.0/LOCAL_TESTING.md

@@ -0,0 +1,307 @@
+# Local Testing Guide for drivee-client
+
+This guide explains how to test the `drivee-client` package locally before publishing to PyPI.
+
+## 🎯 Testing Methods
+
+### Method 1: Editable Install (Recommended for Development)
+
+**Best for:** Active development where you're making frequent changes.
+
+```bash
+# Install in editable mode
+python build.py install-local
+
+# Or manually:
+pip install -e .
+```
+
+**Advantages:**
+
+- ✅ Changes to source code are immediately reflected
+- ✅ No need to rebuild after each change
+- ✅ Can use debugger and see source code
+- ✅ Perfect for development workflow
+
+**Test it:**
+
+```bash
+# Run the test script
+python test_local_install.py
+
+# Or test manually in Python
+python -c "from drivee_client import DriveeClient; print('Success!')"
+```
+
+**Uninstall when done:**
+
+```bash
+pip uninstall drivee-client
+```
+
+---
+
+### Method 2: Install from Built Distribution
+
+**Best for:** Testing the actual package before publishing to PyPI.
+
+```bash
+# Build the package
+python build.py build
+
+# Install from the built wheel
+python build.py install-dist
+
+# Or manually:
+pip install dist/drivee_client-*.whl --force-reinstall
+```
+
+**Advantages:**
+
+- ✅ Tests the exact package that will be published
+- ✅ Verifies package metadata and dependencies
+- ✅ Ensures all files are included correctly
+- ✅ Validates the installation process
+
+**Important:** You need to rebuild and reinstall after each code change.
+
+---
+
+### Method 3: Test from Test PyPI
+
+**Best for:** Final validation before production release.
+
+```bash
+# Build and upload to Test PyPI
+python build.py all
+python build.py test-upload
+
+# Install from Test PyPI
+pip install --index-url https://test.pypi.org/simple/drivee-client
+
+# Or with dependencies from regular PyPI
+pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/drivee-client
+```
+
+**Advantages:**
+
+- ✅ Tests the complete publishing workflow
+- ✅ Validates package on a real PyPI server
+- ✅ Safe environment (won't affect production)
+- ✅ Can share test version with others
+
+---
+
+## 📋 Complete Testing Workflow
+
+### Step 1: Development Testing
+
+```bash
+# Install in editable mode
+python build.py install-local
+
+# Run tests
+pytest
+
+# Run the verification script
+python test_local_install.py
+
+# Test your code manually
+python -c "
+import asyncio
+from drivee_client import DriveeClient
+
+async def test():
+    async with DriveeClient('user', 'pass') as client:
+        print('Client created successfully!')
+        
+asyncio.run(test())
+"
+```
+
+### Step 2: Pre-publish Testing
+
+```bash
+# Clean and build
+python build.py all
+
+# Install from dist to test the package
+python build.py install-dist
+
+# Run full test suite
+pytest
+
+# Run the verification script
+python test_local_install.py
+```
+
+### Step 3: Test PyPI Validation
+
+```bash
+# Upload to Test PyPI
+python build.py test-upload
+
+# Create a new virtual environment for clean testing
+python -m venv test_env
+test_env\Scripts\activate  # Windows
+# source test_env/bin/activate  # Linux/Mac
+
+# Install from Test PyPI
+pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ drivee-client
+
+# Test the package
+python test_local_install.py
+
+# Deactivate and cleanup
+deactivate
+```
+
+### Step 4: Production Release
+
+```bash
+# Only after all tests pass!
+python build.py upload
+```
+
+---
+
+## 🧪 Testing Checklist
+
+Before publishing to PyPI, ensure:
+
+- [ ] All unit tests pass (`pytest`)
+- [ ] Package builds without errors (`python build.py build`)
+- [ ] Package passes twine check (`python build.py check`)
+- [ ] Local install works (`python build.py install-local`)
+- [ ] Verification script passes (`python test_local_install.py`)
+- [ ] Version number updated in `drivee_client/__init__.py`
+- [ ] CHANGELOG.md updated with changes
+- [ ] README.md is accurate and up-to-date
+- [ ] All dependencies are listed in `pyproject.toml`
+- [ ] Test PyPI upload successful (`python build.py test-upload`)
+- [ ] Installation from Test PyPI works
+- [ ] Git changes committed and tagged
+
+---
+
+## 🐛 Troubleshooting
+
+### "no running event loop" error
+
+If you see `RuntimeError: no running event loop` when trying to instantiate `DriveeClient`:
+
+**Problem:** The `DriveeClient` creates an `aiohttp.ClientSession` in `__init__`, which requires an active event loop.
+
+**Solution:** Always instantiate and use `DriveeClient` within an async context:
+
+```python
+import asyncio
+from drivee_client import DriveeClient
+
+# ❌ Wrong - will fail with "no running event loop"
+client = DriveeClient("user", "pass")
+
+# ✅ Correct - use within async function
+async def main():
+    async with DriveeClient("user", "pass") as client:
+        await client.init()
+        # Your code here
+
+asyncio.run(main())
+```
+
+### "Module not found" after installation
+
+```bash
+# Ensure you're in the right environment
+pip list | grep drivee
+
+# Try reinstalling
+pip uninstall drivee-client
+python build.py install-local
+```
+
+### Changes not reflected after editing code
+
+```bash
+# If using editable install, restart Python interpreter
+# If using dist install, rebuild and reinstall
+python build.py build
+python build.py install-dist
+```
+
+### Import errors for dependencies
+
+```bash
+# Install dependencies manually
+pip install aiohttp pydantic tenacity python-dotenv
+
+# Or from the project
+pip install -r requirements.txt
+```
+
+### Package metadata issues
+
+```bash
+# Check the built package
+python build.py build
+python build.py check
+
+# Inspect the wheel contents
+pip install wheel
+wheel unpack dist/drivee_client-*.whl
+```
+
+---
+
+## 💡 Tips
+
+1. **Always use virtual environments** to avoid conflicts:
+
+   ```bash
+   python -m venv venv
+   venv\Scripts\activate  # Windows
+   ```
+
+2. **Use pytest fixtures** for testing async code:
+
+   ```python
+   import pytest
+   from drivee_client import DriveeClient
+   
+   @pytest.mark.asyncio
+   async def test_client():
+       async with DriveeClient("user", "pass") as client:
+           assert client is not None
+   ```
+
+3. **Mock API calls** during testing:
+
+   ```python
+   from unittest.mock import AsyncMock, patch
+   
+   @patch('aiohttp.ClientSession.post')
+   async def test_login(mock_post):
+       mock_post.return_value.__aenter__.return_value.json = AsyncMock(
+           return_value={"token": "test_token"}
+       )
+       # Your test code here
+   ```
+
+4. **Test with different Python versions** if supporting multiple versions:
+
+   ```bash
+   # Using pyenv or virtualenv for each version
+   python3.10 -m venv venv310
+   python3.11 -m venv venv311
+   python3.12 -m venv venv312
+   ```
+
+---
+
+## 📚 Additional Resources
+
+- [Python Packaging Guide](https://packaging.python.org/)
+- [Testing with pytest](https://docs.pytest.org/)
+- [Test PyPI](https://test.pypi.org/)
+- [Twine Documentation](https://twine.readthedocs.io/)

driveeclient-0.1.0/MANIFEST.in

@@ -0,0 +1,23 @@
+include README.md
+include LICENSE
+include requirements.txt
+include pyproject.toml
+recursive-include drivee_client *.py
+recursive-include tests *.py
+recursive-include docs *.md *.rst
+global-exclude *.pyc
+global-exclude __pycache__
+global-exclude .DS_Store
+global-exclude *.so
+global-exclude build.py
+global-exclude package_build.py
+global-exclude package_build_script.py
+global-exclude test_local_install.py
+global-exclude main.py
+prune .git
+prune .github
+prune .vscode
+prune build
+prune dist
+prune *.egg-info
+prune actions

driveeclient-0.1.0/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.4
+Name: driveeClient
+Version: 0.1.0
+Summary: Python client library for automation and control of an EV Wallbox charger via local API or cloud endpoints
+Author-email: Your Name <your.email@example.com>
+Maintainer-email: Your Name <your.email@example.com>
+License: MIT
+Project-URL: Homepage, https://github.com/yourusername/drivee-client
+Project-URL: Repository, https://github.com/yourusername/drivee-client
+Project-URL: Issues, https://github.com/yourusername/drivee-client/issues
+Project-URL: Documentation, https://github.com/yourusername/drivee-client#readme
+Keywords: ev,charging,wallbox,drivee,electric-vehicle,api-client
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Home Automation
+Classifier: Topic :: Internet :: WWW/HTTP :: HTTP Servers
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aiohttp>=3.8.0
+Requires-Dist: pydantic>=2.0.0
+Requires-Dist: tenacity>=8.0.0
+Requires-Dist: python-dotenv>=1.0.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
+Requires-Dist: black>=23.0.0; extra == "dev"
+Requires-Dist: isort>=5.12.0; extra == "dev"
+Requires-Dist: flake8>=6.0.0; extra == "dev"
+Requires-Dist: mypy>=1.0.0; extra == "dev"
+Requires-Dist: pylance; extra == "dev"
+Provides-Extra: test
+Requires-Dist: pytest>=7.0.0; extra == "test"
+Requires-Dist: pytest-asyncio>=0.21.0; extra == "test"
+Requires-Dist: pytest-cov>=4.0.0; extra == "test"
+Dynamic: license-file
+
+# Drivee Client
+
+A Python client library for automation and control of EV Wallbox chargers via the Drivee cloud API.
+
+[![PyPI version](https://badge.fury.io/py/drivee-client.svg)](https://badge.fury.io/py/drivee-client)
+[![Python Support](https://img.shields.io/pypi/pyversions/drivee-client.svg)](https://pypi.org/project/drivee-client/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+## Installation
+
+```bash
+pip install drivee-client
+```
+
+## Quick Start
+
+```python
+import asyncio
+from drivee_client import DriveeClient
+
+async def main():
+    async with DriveeClient("username", "password") as client:
+        await client.init()
+        
+        # Get charge point info
+        charge_point = await client.get_charge_point()
+        print(f"Charge point: {charge_point.name}")
+        print(f"Status: {charge_point.evse.status}")
+        
+        # Start charging
+        response = await client.start_charging()
+        print(f"Started session: {response.session.id}")
+        
+        # Get charging history
+        history = await client.get_charging_history()
+        for session in history.sessions:
+            print(f"Session {session.id}: {session.energy/1000:.2f}kWh")
+
+if __name__ == "__main__":
+    asyncio.run(main())
+```
+
+## Features
+
+- **Async/await support** - Built with `aiohttp` for non-blocking I/O
+- **Type-safe** - Full type hints with Pydantic models
+- **Error handling** - Comprehensive error handling with custom exceptions
+- **Rate limiting** - Built-in retry logic with exponential backoff
+- **Clean architecture** - Separation of DTOs and business models
+- **Domain validation** - Business rule validation in model layer
+
+## Architecture
+
+The client library follows a clear separation of concerns with three main layers:
+
+### Data Transfer Objects (DTOs)
+
+Located in `dtos/`, these are pure data classes that:
+
+- Match the exact structure of API responses
+- Use Pydantic for validation and serialization
+- Have no business logic
+- Follow naming convention: All DTO classes end with 'DTO' suffix
+- Are only used within the model layer
+
+### Business Models
+
+Located in `models/`, these classes:
+
+- Encapsulate DTOs and provide business logic
+- Expose only business-relevant properties and methods
+- Use Protocol-based typing for DTO interfaces
+- Handle all business rules and validations
+- Are the only classes exposed to the Home Assistant integration
+
+### API Client
+
+The `drivee_client.py` handles:
+
+- REST API communication
+- Authentication
+- Request/response mapping to DTOs
+- Error handling and retries
+
+## Installation
+
+1. Copy the `custom_components/drivee` folder to your Home Assistant's `custom_components` directory.
+2. Restart Home Assistant.
+
+## Configuration
+
+1. Go to Home Assistant's Settings > Devices & Services
+2. Click "Add Integration"
+3. Search for "Drivee"
+4. Enter your Drivee API base URL
+5. (Optional) Enter your API key if required
+
+## Usage
+
+After configuration, you can control your Drivee device through Home Assistant's interface. The integration will create a switch entity that you can use to control your device.
+
+## Development
+
+To develop or modify this integration:
+
+1. Clone this repository
+2. Install dependencies:
+
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+3. Make your changes
+4. Test the integration locally
+5. Copy the modified files to your Home Assistant's `custom_components` directory
+
+## License
+
+MIT License

driveeclient-0.1.0/README.md

@@ -0,0 +1,119 @@
+# Drivee Client
+
+A Python client library for automation and control of EV Wallbox chargers via the Drivee cloud API.
+
+[![PyPI version](https://badge.fury.io/py/drivee-client.svg)](https://badge.fury.io/py/drivee-client)
+[![Python Support](https://img.shields.io/pypi/pyversions/drivee-client.svg)](https://pypi.org/project/drivee-client/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+## Installation
+
+```bash
+pip install drivee-client
+```
+
+## Quick Start
+
+```python
+import asyncio
+from drivee_client import DriveeClient
+
+async def main():
+    async with DriveeClient("username", "password") as client:
+        await client.init()
+        
+        # Get charge point info
+        charge_point = await client.get_charge_point()
+        print(f"Charge point: {charge_point.name}")
+        print(f"Status: {charge_point.evse.status}")
+        
+        # Start charging
+        response = await client.start_charging()
+        print(f"Started session: {response.session.id}")
+        
+        # Get charging history
+        history = await client.get_charging_history()
+        for session in history.sessions:
+            print(f"Session {session.id}: {session.energy/1000:.2f}kWh")
+
+if __name__ == "__main__":
+    asyncio.run(main())
+```
+
+## Features
+
+- **Async/await support** - Built with `aiohttp` for non-blocking I/O
+- **Type-safe** - Full type hints with Pydantic models
+- **Error handling** - Comprehensive error handling with custom exceptions
+- **Rate limiting** - Built-in retry logic with exponential backoff
+- **Clean architecture** - Separation of DTOs and business models
+- **Domain validation** - Business rule validation in model layer
+
+## Architecture
+
+The client library follows a clear separation of concerns with three main layers:
+
+### Data Transfer Objects (DTOs)
+
+Located in `dtos/`, these are pure data classes that:
+
+- Match the exact structure of API responses
+- Use Pydantic for validation and serialization
+- Have no business logic
+- Follow naming convention: All DTO classes end with 'DTO' suffix
+- Are only used within the model layer
+
+### Business Models
+
+Located in `models/`, these classes:
+
+- Encapsulate DTOs and provide business logic
+- Expose only business-relevant properties and methods
+- Use Protocol-based typing for DTO interfaces
+- Handle all business rules and validations
+- Are the only classes exposed to the Home Assistant integration
+
+### API Client
+
+The `drivee_client.py` handles:
+
+- REST API communication
+- Authentication
+- Request/response mapping to DTOs
+- Error handling and retries
+
+## Installation
+
+1. Copy the `custom_components/drivee` folder to your Home Assistant's `custom_components` directory.
+2. Restart Home Assistant.
+
+## Configuration
+
+1. Go to Home Assistant's Settings > Devices & Services
+2. Click "Add Integration"
+3. Search for "Drivee"
+4. Enter your Drivee API base URL
+5. (Optional) Enter your API key if required
+
+## Usage
+
+After configuration, you can control your Drivee device through Home Assistant's interface. The integration will create a switch entity that you can use to control your device.
+
+## Development
+
+To develop or modify this integration:
+
+1. Clone this repository
+2. Install dependencies:
+
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+3. Make your changes
+4. Test the integration locally
+5. Copy the modified files to your Home Assistant's `custom_components` directory
+
+## License
+
+MIT License