6e964c230f
Phase A of the IoT initiative — gets the server-side infrastructure
in place before the Raspberry Pi hardware arrives, so the iot admin
UI + /fp/iot/ingest endpoint are ready to accept the first real
temperature reading as soon as the Pi is wired up.
New top-level folder: fusion_iot/
1. **iot_base/** — Odoo S.A. iot_base module, copied from
RePackaged-Odoo verbatim. LGPL-3 upstream, no changes needed.
2. **iot/** — Odoo S.A. iot module, repackaged:
- `models/update.py` neutralised (removed the publisher_warranty
IoT-Box-counting report that phones home to odoo.com for
enterprise licence enforcement)
- `iot_handlers/lib/load_worldline_library.sh` deleted (proprietary
Worldline payment lib fetch from download.odoo.com, not needed)
- `wizard/add_iot_box.py._connect_iot_box_with_pairing_code` —
upstream called odoo.com's iot-proxy to resolve pairing codes;
replaced with a no-op. Pi-side iot_drivers proxy registers
directly with this Odoo server instead.
- Manifest rebranded with an explicit changelog preamble.
3. **fusion_plating_iot/** — new plating-specific wrapper:
- `fp.tank.sensor` — maps an iot.device (or a direct-HTTP-ingest
sensor) to a fusion.plating.tank + fusion.plating.bath.parameter.
Supports DS18B20, PT100/1000, pH, conductivity, level. Per-sensor
alert_min/max overrides.
- `fp.tank.reading` — append-only time-series. On create, evaluates
against sensor's alert range. On in-spec → out-of-spec TRANSITION,
auto-raises a fusion.plating.quality.hold (once per excursion,
no spam during sustained out-of-spec).
- `POST /fp/iot/ingest` — shared-secret HTTP endpoint for sensors
bypassing the Pi proxy. Token via X-FP-IOT-Token header OR body.
Accepts single-reading or batch payloads.
- Menu under Plating → Operations → Sensors & Readings.
- Tank form inherits get a Sensors tab inline.
Deployed to entech. Verified end-to-end:
- Install: iot_base + iot + fusion_plating_iot all 'installed'
- Smoke test: in-spec → out-of-spec → hold raised (HOLD-0010);
continued excursion → NO duplicate hold; back-in-spec → NEW
excursion → NEW hold (HOLD-0011) ✓
- HTTP endpoint: correct token → 200 accepted; wrong token → 401;
unknown device_serial → 404; batch payload → 200 accepted=N ✓
Phase B (when Raspberry Pi hardware arrives): DS18B20 iot_handler
driver for the Pi-side iot_drivers proxy + systemd service on
vanilla Raspberry Pi OS + first live reading from physical probe.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
29 lines
1.1 KiB
Python
29 lines
1.1 KiB
Python
from odoo import tests
|
|
|
|
from odoo.addons.iot.tests.common import IotCommonTest
|
|
|
|
|
|
@tests.tagged('post_install', '-at_install')
|
|
class TestUi(IotCommonTest):
|
|
iot_websocket_messages = []
|
|
|
|
def test_iot_device_test_button(self):
|
|
"""Make sure we can use the websocket to test printers using the 'Test'
|
|
button on the printer (iot.device) record."""
|
|
self.start_tour("/odoo/iot", "iot_device_test_printer", login="admin")
|
|
self.assertEqual(
|
|
len(self.iot_websocket_messages),
|
|
3,
|
|
(
|
|
"`iot.channel.send_message` should be called exactly three times: "
|
|
"webrtc offer, websocket action, then operation confirmation."
|
|
"This time, we received %s" % [next(iter(message.keys())) for message in self.iot_websocket_messages]
|
|
),
|
|
)
|
|
self.assertIn(
|
|
'webrtc_offer', self.iot_websocket_messages[0], "First ws message should be of type 'webrtc_offer'."
|
|
)
|
|
self.assertIn(
|
|
'iot_action', self.iot_websocket_messages[1], "Second ws message should be of type 'iot_action'."
|
|
)
|