This addon defines AMQP as an integration option with a device.
With AMQP, we will send and AMQP message to a broker that will send it to the device. Then, the device will do the expected action.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Adds AMQP as an IoT output system in Odoo, letting users configure AMQP brokers and send messages to devices through them.
This module adds a new IoT output system called AMQP, so Odoo can send messages to a broker that forwards them to a device.
- A new menu "AMQP Hosts" appears under the IoT configuration menu, where users can create and manage AMQP brokers. Each host has a name and a connection URL (for example amqp://USER:PASS@HOST).
- On an IoT device output, when the system is set to AMQP, an "AMQP configuration" section appears with fields for the host, exchange, routing key and payload. The host, exchange and routing key are mandatory in that case; Odoo blocks saving if any of them is missing.
- A "Run" button is shown on the device output form when the system is AMQP. Pressing it sends the configured message to the broker using the stored connection details.
- The module also adds the AMQP system and its action automatically, so they are ready to use after installation.
It touches the IoT device output and IoT system action models, and requires the Python library pika to be installed on the server.
Depends on
Menus it adds
Models and fields (2)
- iot.amqp.host · new modelname, active, connection
- iot.device.output · extends an existing modelamqp_host_id, amqp_payload, amqp_exchange, amqp_routing_key
Text generated by AI (DeepSeek) from reading the Odoo 12.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/iot.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.