Internet Of Things
by Viindoo
| Lines of Code | 3425 |
| Technical name | viin_iot |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/17.0/viin_iot |
| Read description for | v 16.0 |
| Required Apps | Discuss (mail) |
| Extensions | Pos IoT IoT Manufacturing IoT Quality |
One Platform. Every Device On Your Floor.
viin_iot pairs your IoT boxes with the printers, scanners, scales, displays, and payment terminals attached to them - then hands each device to the Odoo app that actually uses it.
Buy the platform once, then turn on only the apps - POS, Manufacturing, Quality, Work Order Tablet - that put your hardware to work.
Key Features
Overview
See every paired IoT box on a kanban dashboard, jump into its home page, its devices, or its logs from one screen.
Devices
Browse every peripheral device paired to a box - printer, scanner, scale, display, payment terminal and more - grouped by box or type, with live connected/disconnected status.
Device Logs
Read the raw diagnostic log stream every paired box sends, filterable and grouped by box or severity, so a support call starts from evidence instead of guesswork.
IoT Boxes
Administer the box fleet as a list-first register for an IoT admin - the same records Overview shows, ordered for an audit rather than a dashboard, including each box’s own credentials, which stay admin-only wherever they appear.
Settings
Tune how long device logs are kept and how long a device action may sit unconfirmed before the operator is told it timed out, then activate the five IoT bridge apps from one screen.
IoT Home Page
Open a paired box’s own local web UI in a new tab straight from its Overview card, once the box has reported an address.
Scan IoT Box
Guide an operator through opening the box image’s own network-discovery page to find a new box’s address - the first step toward pairing it, guided from inside Odoo.
Device Dispatch
Record every device command before it is sent and resolve it to exactly one outcome - Completed, Refused, or Never Confirmed - delivered once, so nobody is told a job succeeded when nobody confirmed it did.
Five Apps Stand On This Platform
viin_iot itself doesn’t ring up a sale, print a work order, or log a quality check - it’s the hardware layer underneath the app that does. Turn on the ones this business needs, each sold separately, each switched on from the same Settings screen:
Pos IoT - Drive IoT hardware from the Point of Sale: receipt printers, barcode scanners, a customer display, and a scale, each attached to a POS.
IoT Manufacturing - Attach IoT devices to manufacturing work centers, so an operator can weigh a produced quantity, print a label, or drive a footswitch from the station itself.
IoT Quality - Read a measurement straight from a registered instrument into a quality check, instead of the operator copying the number by hand.
IoT Work Order Tablet - Let an IoT barcode scanner drive the work-order tablet screen, so a scan does what pressing the matching button would have done.
Quality Control IoT for Manufacturing - Read a work-order quality check from the instrument nominated on its own work center; installs itself once IoT Manufacturing and IoT Quality are both present.
From A Box On A Shelf To A Device Everyone Trusts
Pair the box
An administrator (or anyone holding IoT Box Creator rights) scans for the box on the local network from Overview, then pairs it.
The devices show up
Printers, scanners, scales, and terminals attached to that box appear in Devices with live Connected / Disconnected status - no manual entry.
Turn on the apps that use them
In Settings, an administrator switches on POS, Manufacturing, Quality, or Work Order Tablet - only the ones this business bought.
Everyone else just uses the hardware
A cashier, an operator, or a quality inspector - holding none of the IoT permission groups - prints a receipt, weighs a part, or logs a reading inside their own app. viin_iot dispatches the command underneath, waits inside the configured timeout window, and resolves it to Completed, Refused, or Never Confirmed.
If something needs a closer look
Device Logs holds the raw diagnostic stream every paired box sends, so troubleshooting starts from evidence.
See Every Paired Box At A Glance
Every IoT box you’ve paired shows up on one kanban dashboard. Open its own home page, browse its devices, or check its logs without leaving the screen.
Browse Every Peripheral In One List
Printers, scanners, scales, displays, payment terminals and more - every device paired to a box, grouped by box or by type, each showing live Connected / Disconnected status, so you know what’s actually online before you send it a job.
Read The Evidence Before You Call Support
Every paired box streams its own diagnostic log back to Odoo. Filter or group by box and severity, so a support call starts from evidence instead of a guess.
Administer The Fleet Like A Register, Not A Dashboard
The same boxes Overview shows, laid out as a list built for an administrator auditing the fleet rather than glancing at a kanban - including each box’s own credentials, which never leave the administrator’s screen.
Turn On Only The Apps This Business Needs
One screen tunes how long a device log is kept and how long a device action may go unconfirmed before an operator is told so - and switches on the bridge apps you actually use: POS, Manufacturing, Quality, Work Order Tablet, and Quality Control for Manufacturing.
Open A Box’s Own Control Panel In One Click
Once a paired box has reported its address, open its own local web interface in a new tab straight from its Overview card - no separate login, no hunting for an IP address.
Find A New Box Before You Pair It
Scan the box image’s own network-discovery page to find a new box’s address - the first step toward pairing it, guided from inside Odoo instead of a router’s admin page.
Every Command Gets One Real Answer
Every device action is recorded before it’s sent and resolves to exactly one outcome - Completed, Refused, or Never Confirmed - delivered once, so nobody is ever told a job succeeded when nobody confirmed it did. A box that goes quiet isn’t ignored: a sweep checks every minute and reports the timeout as what it is, not as a silent failure. This runs behind the scenes; the module ships no dedicated screen for it.
Need help with the IoT platform?
Technical Requirement
- Odoo version: 17.0
- Editions: Community, Enterprise
-
Required apps: Discuss (
mail), Web (web), Bus (bus) - standalone platform, no other paid Viindoo app required to install. - License: OPL-1
Give Your Floor One Platform For Every Device
Pair your first box today, then add the app that puts it to work.
Start a 15-Day Free Trial Book A Guided TourOverview
Internet Of Things (IoT) connects the peripheral devices attached to a paired IoT box - printers, barcode scanners, scales, customer displays, payment terminals and more - so other Viindoo apps (Point of Sale, Manufacturing, Quality, Work Order Tablet) can drive that hardware.
On its own, this module is the platform: an IoT administrator pairs and monitors boxes and devices here. The people who actually operate the hardware - a cashier ringing up a sale, a manufacturing operator weighing a produced quantity - use it through their own app once it is paired and configured, without needing any IoT permissions of their own.
Installation
- Open Apps.
- Search for Internet Of Things (technical name viin_iot).
- Click Install.
Odoo installs its required technical components automatically - there is nothing else to install by hand.
Configuration
Access rights (roles)
IoT access is a three-level ladder, assigned from a user's own access rights under the Internet of Things (IoT) category:
- User - sees every paired IoT box, its devices and its logs, read-only.
- IoT Box Creator - everything User can do, plus pairing a new IoT box and registering its devices, including from a remote box.
- Administrator - everything IoT Box Creator can do, plus full control of the IoT infrastructure, including each box's own credentials.
Assign the right level to each person who manages hardware directly. Someone who only operates a POS, a manufacturing work order or a quality check does not need any of these groups - they use the IoT hardware through their own app once an administrator has paired and configured it.
Settings
Open IoT ‣ Configuration ‣ Settings (Administrator only).
- Device Log Retention (days) - how long device logs are kept before the daily cleanup removes them. Set it to 0 or less to keep them indefinitely.
- Log Lines Per Request - the most log lines accepted from one IoT box request in a single batch.
- Device Action Timeout (seconds) - how long a device action (a print job, a scale reading, and so on) may sit unconfirmed before the operator is told it was never confirmed. Set it too low and a slow job is reported as lost; set it too high and the operator waits without an answer.
- IoT Integrations - turn on the bridge apps this deployment has available: Pos IoT, IoT Manufacturing, IoT Quality, IoT Work Order Tablet, and Quality Control IoT for Manufacturing. A row shows a checkbox when that app is available on this deployment, or a "Purchase or Learn more" link when it is not installed yet.
Usage
Pairing dashboard
Open IoT ‣ Overview to see every paired IoT box as a card.
Each card shows the box's name and its number of devices; click the device count to jump straight to that box's device list. Click IoT Home Page to open the box's own local web page in a new tab, once the box has reported an IP address.
To pair a new box, click Scan IoT Box. A confirmation dialog asks you to connect your computer to the same local network as the box before continuing.
Click Continue to open the box's own discovery page and find its IP address, or Cancel to close the dialog without scanning. Pairing the box itself needs the IoT Box Creator or Administrator level.
Box details
Click a card (or a row in the Configuration list) to open a box's own page.
The Devices and Log IoT Box buttons at the top jump to that box's devices and logs. The Devices tab lists every device the box has reported, with its identifier, manufacturer and connection type.
Devices
Open IoT ‣ Devices to browse every peripheral across every box, grouped by box.
Each card shows the device type, the box it belongs to, and whether it is currently Connected or Disconnected. Use the search filters to group by device type or connection type instead, or to show only connected (or only disconnected) devices.
Click a device to see its own page.
The device page shows its type, identifier, connection type, manufacturer, and the box and company it belongs to.
Device Logs
Open IoT ‣ Reporting ‣ Device Logs to read the raw diagnostic stream every paired box sends.
Logs are grouped by box by default; expand a group to see each line's timestamp, severity (Debug, Information, Warning, Error or Critical), source module and description. Use this list to start a support conversation from evidence - for example an Error line reporting that a printer could not be reached, or a Critical line reporting a lost connection - instead of guesswork.
Administering the box fleet
Administrators can also open IoT ‣ Configuration ‣ IoT Boxes for a list-first register of the same boxes Overview shows, ordered for an audit rather than a dashboard.
This is also where an administrator manages a box's own credentials, which never appear anywhere a plain User can see.
Device actions and unconfirmed outcomes
When an app drives a device - printing a receipt, reading a scale - the platform records the action and waits for the box to confirm it. Every action ends in exactly one outcome:
- Dispatched - in flight, inside its time window.
- Completed - the box confirmed it carried out the action.
- Refused - the command never left the server.
- Never Confirmed - no confirmation arrived within the Device Action Timeout set in Settings.
Never Confirmed is not a claim that the action failed - it only means the box did not answer in time. This module ships no dedicated screen for these records; check Device Logs on the box in question for the evidence the box itself reported, such as the connection timed out example above.
Troubleshooting
A box shows no IoT Home Page link. The box has not yet reported an IP address. Confirm the box is powered on and connected to the network, then check its entry in Device Logs for a recent connection message.
A device stays Disconnected. Check the device's own page for its connection type and identifier, and check Device Logs for the box it belongs to - a Warning, Error or Critical line often explains why (a printer low on paper, a lost network connection, and so on).
An operator was told an action was Never Confirmed. This means no confirmation arrived within the configured timeout - it is not automatically a failure. Check Device Logs for the box and device involved. If confirmations are consistently arriving late, raise Device Action Timeout (seconds) in Settings; if they never arrive, check the device and box themselves.
A bridge app row on Settings shows a "Purchase or Learn more" link instead of a checkbox. That app is not available on this deployment yet - it has not been installed, so there is nothing to switch on until it is.
FAQ
Who can pair a new IoT box? IoT Box Creator or Administrator.
Who can see a box's own credentials (token, command channel)? Administrator only - a plain User or IoT Box Creator never sees them.
Does a cashier or manufacturing operator need an IoT group to use the hardware? No. Once an administrator has paired the box and configured the devices, the person operating the corresponding app (Point of Sale, Manufacturing, and so on) uses the hardware through that app - no IoT group is required.
Where do I see what a box has been doing? IoT ‣ Reporting ‣ Device Logs, or the Log IoT Box smart button on the box's own page.
What happens to old device logs? They are kept for the number of days set in Device Log Retention (days) under Settings, then removed by a daily cleanup. Set it to 0 or less to keep them indefinitely.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must 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.
