matthias.lotz
deaa95c650
Completes PUSH-only architecture - removes all PULL-based config fetching REMOVED: - MockOdooClient.get_config() method (~15 lines) - Legacy PULL logic: returned hardcoded device config - No longer used after PUSH architecture (Phase 3.1/3.2) - OdooClient.get_config() method (~27 lines) - Legacy PULL logic: GET /ows/iot/config from Odoo - No longer used after PUSH architecture (Phase 3.1/3.2) VERIFIED: - ✅ No periodic config refresh logic in main.py - ✅ Bridge loads config-active.yaml at startup only - ✅ Bridge receives config via POST /config (pushed by Odoo) - ✅ No GET requests to Odoo for config anymore KEPT (unchanged): - odoo_client.send_event() - still used for event pushing - config_server.py GET /config - returns bridge's current config (debugging) ARCHITECTURE CLEANUP: Before: Bridge could PULL config from Odoo (get_config) After: Bridge ONLY receives PUSH from Odoo (POST /config) - Cleaner separation of concerns - No periodic polling overhead - Bridge fully autonomous with config-active.yaml MODIFIED FILES: - iot_bridge/odoo_client.py - ~40 lines removed - IMPLEMENTATION_PLAN.md - Phase 3.3 marked complete TESTING: ✅ Bridge still runs without config-active.yaml (waits for push) ✅ Bridge loads config-active.yaml at startup ✅ No errors in bridge logs (no missing get_config calls) ✅ Odoo push still works (Phase 3.2 model hooks) NEXT STEP: Phase 3.5 - End-to-End Tests (full PUSH architecture validation) |
||
|---|---|---|
| extra-addons/open_workshop/open_workshop_mqtt | ||
| iot_bridge | ||
| odoo@fd43f0445a | ||
| python_proto_type | ||
| .gitignore | ||
| FEATURE_REQUEST_OPEN_WORKSHOP_MQTT_IoT.md | ||
| IMPLEMENTATION_PLAN.md | ||