- status_monitor: add availability_managed set; _monitor_loop skips devices in this set so the LWT/availability topic is the sole online/offline source - device_manager: register device with status_monitor.set_availability_managed() so the monitor actually skips them (previously the monitor had no knowledge of DeviceManager.availability_managed) - mqtt_bridge: remove blanket 'reset all devices to offline' on bridge restart; this was causing a race condition where the cron reset state AFTER the bridge had already sent device_online events via retained MQTT messages; stale running session cleanup is kept (still needed) |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| extra-addons/open_workshop | ||
| iot_bridge | ||
| odoo | ||
| .gitignore | ||
| .readthedocs.yaml | ||
| DEPLOYMENT.md | ||
| DOCUMENTATION_STRATEGY.md | ||
| IMPLEMENTATION_PLAN.md | ||
| README.md | ||
odoo_mqtt
MQTT-Integration für Odoo – bestehend aus einem Python-Dienst und zugehörigen Odoo-Modulen.
Inhalt
| Verzeichnis | Beschreibung |
|---|---|
iot_bridge/ |
Python-Dienst: verbindet MQTT-Broker mit Odoo via REST/JSON-RPC |
extra-addons/open_workshop/open_workshop_mqtt/ |
Odoo-Modul: MQTT-Anbindung für den Open Workshop |
extra-addons/open_workshop/open_workshop_pos_mqtt/ |
Odoo-Modul: MQTT-Anbindung für den Point of Sale |
Abhängigkeiten
- Odoo 18
- MQTT-Broker (z.B. Mosquitto)
- Python 3.11+
Entwicklung
Siehe iot_bridge/DEVELOPMENT.md für den Python-Dienst.
Die Odoo-Module werden zusammen mit open_workshop entwickelt.