odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/general/iot/devices.md

@@ -0,0 +1,27 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot/devices.html"
+---
+
+:nosearch:
+:show-content:
+:show-toc:
+# 
+# Devices
+
+.. seealso::
+   - :doc:`Connect a Worldline payment terminal
+     <../../sales/point_of_sale/payment_methods/terminals/worldline>`
+   - :doc:`Connect an Ingenico payment terminal
+     <../../sales/point_of_sale/payment_methods/terminals/ingenico>`
+
+.. toctree::
+   :titlesonly:
+   :glob:
+
+   devices/screen
+   devices/measurement_tool
+   devices/camera
+   devices/footswitch
+   devices/printer
+   devices/scale

package/payload/skills/odoo18-docs/references/docs/applications/general/iot/iot_advanced/https_certificate_iot.md

@@ -0,0 +1,160 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot/iot_advanced/https_certificate_iot.html"
+---
+
+.. _iot/https_certificate_iot:
+# 
+# HTTPS certificate (IoT)
+
+*Hypertext Transfer Protocol Secure* (HTTPS) is the secure and encrypted version of *Hypertext
+Transfer Protocol* (HTTP), which is the primary protocol used for data communication between a web
+browser and a website. It secures communications by using an encryption protocol known as *Transport
+Layer Security* (TLS), previously called *Secure Sockets Layer* (SSL). The security of
+:abbr:`HTTPS (Hypertext Transfer Protocol Secure)` relies on :abbr:`TLS (Transport Layer Security)`
+/:abbr:`SSL (Secure Sockets Layer)` certificates, which authenticate the provider and verify their
+identity.
+
+The use of HTTPS is required to communicate with certain network devices, particularly payment
+terminals. If the HTTPS certificate is not valid, some devices cannot interact with the IoT
+system.
+
+> **note**:
+>    In this documentation and throughout Odoo, the term *HTTPS certificate*  refers to a valid
+   SSL certificate that allows an HTTPS connection.
+
+.. _iot/https_certificate_iot/generation:
+
+# HTTPS certificate generation
+
+The HTTPS certificate is generated automatically. When the IoT system is (re-)started (e.g., after
+it is connected to the Odoo database), a request is sent to `<https://www.odoo.com>`_, which returns
+the HTTPS certificate if the IoT system and database meet the eligibility criteria:
+
+.. _iot/https_certificate_iot/iot-eligibility:
+
+- The database must be a **production** instance. The database instance should not be a copy, a
+  duplicate, a staging, or a development environment.
+- The Odoo subscription must be ongoing (:guilabel:`In Progress` status) and have an :ref:`IoT
+  box subscription <iot/iot/iot-subscription>` line.
+
+When the certificate has been received:
+
+- The IoT system's homepage address is updated to a new HTTPS URL ending with `.odoo-iot.com`. Click
+  the URL to establish a secure HTTPS connection.
+
+  .. image:: https_certificate_iot/iot-new-domain.png
+     :alt: Odoo IoT app IoT box with .odoo-iot.com domain.
+
+- The :guilabel:`HTTPS certificate` banner displays the certificate's validity period. To view this
+  information, click the :icon:`fa-cogs` (:guilabel:`cogs`) button on the IoT system's homepage.
+
+  .. image:: https_certificate_iot/https-valid.png
+     :alt: IoT box homepage with HTTPS certificate validity date.
+
+# HTTPS certificate generation issues and errors
+
+## The HTTPS certificate does not generate
+
+Potential causes include the following:
+
+- No :ref:`IoT box subscription <iot/iot/iot-subscription>` is linked to your account.
+- The :ref:`IoT box subscription <iot/iot/iot-subscription>` was added *after* connecting the IoT
+  system to the database. In this case, refresh the IoT system's homepage or reboot/:ref:`restart
+  <iot/windows_iot/restart>` the IoT system to regenerate the HTTPS certificate.
+- The firewall is preventing the HTTPS certificate from generating correctly. In this case,
+  deactivate the firewall until the certificate is successfully generated.
+
+  > **note**:
+>      Some devices, such as routers with a built-in firewall, can prevent the HTTPS certificate from
+     generating.
+
+## The IoT system's homepage can be accessed using its IP address but not the `xxx.odoo-iot.com` URL
+
+Contact your system or network administrator to address the issue. Network-related problems are
+beyond the scope of Odoo support services.
+
+- If the router allows manual :abbr:`DNS (Domain Name System)` configuration, update the settings to
+  use [Google DNS ](https://developers.google.com/speed/public-dns).
+- If the router does not support this, you need to update the DNS settings directly on each device
+  that interacts with the IoT system to use [Google DNS
+  ](https://developers.google.com/speed/public-dns). Instructions for configuring DNS on individual
+  devices can be found on the respective manufacturer's website.
+
+> **note**:
+>    - Some IoT devices, such as payment terminals, likely do not require DNS changes, as they are
+     typically pre-configured with custom DNS settings.
+   - On some browsers, an error code mentioning the DNS (such as `DNS_PROBE_FINISHED_NXDOMAIN`) is
+     displayed.
+
+## Errors
+
+A specific error code is displayed on the IoT system's homepage if any issues occur during the
+generation or reception of the HTTPS certificate.
+
+> **tip**:
+>    When you access the IoT system's homepage, it automatically checks for an HTTPS certificate and
+   attempts to generate one if it is missing. If an error appears, refresh the page to see if the
+   issue is resolved.
+
+### `ERR_IOT_HTTPS_CHECK_NO_SERVER`
+
+The server configuration is missing, i.e., the Odoo instance is not :doc:`connected <../connect>` to
+the IoT system.
+
+### `ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`
+
+An error occurred while attempting to read the existing HTTPS certificate.
+Verify that the HTTPS certificate file is readable.
+
+### `ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`
+
+The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is missing form the IoT.
+
+Verify that both values are correctly configured. To update them, :ref:`access the IoT box's
+<iot/iot-box/homepage>` or :ref:`Windows virtual IoT's homepage <iot/windows-iot/homepage>`,
+click the :icon:`fa-cogs` (:guilabel:`cogs`) button, then click :guilabel:`Credential`.
+
+### `ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`
+
+An unexpected error occurred while the IoT system tried to reach `<https://www.odoo.com>`_. This is
+likely due to network-related issues, such as:
+
+- The IoT system does not have Internet access.
+- Network restrictions (e.g., firewalls or VPNs) are preventing communication with
+  https://www.odoo.com.
+
+> **note**:
+>    - To access the full request exception details with information regarding the error, :ref:`enable
+     the developer mode <developer-mode>`, click the IoT system's card in the IoT app, and click
+     :guilabel:`Download logs` on the :ref:`IoT system's form <iot/connect/IoT-form>`.
+     To define the log levels recorded in the IoT system's log file, :ref:`access the IoT box's
+     <iot/windows-iot/homepage>` or :ref:`Windows virtual IoT's <iot/iot-box/homepage>` homepage,
+     click the :icon:`fa-cogs` (:guilabel:`cogs`) button, then :guilabel:`Log level` at the
+     bottom of the page.
+   - To address network-related issues, contact your system or network administrator; these issues
+     are beyond the scope of Odoo support services.
+
+### `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`
+
+The IoT system successfully reached `<https://www.odoo.com>`_ but received an unexpected
+[HTTP response (status codes) ](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status).
+
+This error code includes the HTTP status. For example, `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` means
+the server returned a "Page Not Found" response.
+
+To solve this issue:
+
+#. Open `<https://www.odoo.com>`_ in a web browser to check if the website is temporarily down for
+   maintenance.
+#. | If `<https://www.odoo.com>`_ is down for maintenance, wait for it to resume.
+   | If the website is operational, open a [support ticket ](https://www.odoo.com/help) and make
+     sure to include the 3-digit HTTPS status code in the ticket.
+
+### `ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`
+
+The IoT system successfully connected to `<https://www.odoo.com>`_, but the server refused to
+provide the HTTPS certificate.
+
+Check that the IoT system and database meet the :ref:`eligibility requirements
+<iot/https_certificate_iot/iot-eligibility>` for an HTTPS certificate.

package/payload/skills/odoo18-docs/references/docs/applications/general/iot/iot_advanced/ssh_connect.md

@@ -0,0 +1,39 @@
+---
+title: "IoT box SSH connection"
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot/iot_advanced/ssh_connect.html"
+---
+
+======================
+# IoT box SSH connection
+
+> **note**:
+>    SSH connections are only available for :doc:`IoT boxes <../iot_box>`, not the :doc:`Windows
+   virtual IoT <../windows_iot>`.
+
+> **warning**:
+>    - This feature should **only** be used with trusted parties, as it provides administrative
+     access to the IoT box, which can create security issues.
+   - Managing an SSH connection is **not** covered under the standard Odoo support scope. Visit
+     the [Odoo Support ](https://www.odoo.com/help) page for additional information about what is
+     covered.
+
+To provide an :abbr:`SSH (secure shell protocol)` connection to an IoT box, you must generate a
+password:
+
+#. Access the IoT box's homepage by opening the IoT app and clicking the IP address displayed
+   on the IoT box's card.
+#. Click the :icon:`fa-cogs` (:guilabel:`cogs`) button at the top-right, then :guilabel:`Remote
+   Debug`.
+#. In the :guilabel:`Remote Debugging` popup that opens, click :guilabel:`Generate` and save the
+   password securely. Once you close the popup, the password will no longer be available.
+
+   .. image:: ssh_connect/ssh-generate-password.png
+      :alt: The Remote Debugging password generation window.
+
+#. Enter the :guilabel:`Authentication Token` provided by the user attempting to connect to the IoT
+   box.
+#. Click :guilabel:`Enable Remote Debugging`.
+
+.. seealso::
+   - :doc:`../iot_box`
+   - :doc:`../connect`

package/payload/skills/odoo18-docs/references/docs/applications/general/iot/iot_advanced/updating_iot.md

@@ -0,0 +1,91 @@
+---
+title: "IoT system updates"
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot/iot_advanced/updating_iot.html"
+---
+
+==================
+# IoT system updates
+
+Due to the complexity of IoT systems, the term *updating* can refer to several processes, including:
+
+- :ref:`Updating the IoT system's image and/or core code <iot/updating_iot/image-code>`;
+- :ref:`Updating the handlers <iot_updating_iot/handlers>`, which include the interfaces and drivers.
+
+.. _iot/updating_iot/image-code:
+
+# Image and core code update
+
+.. tabs::
+
+   .. group-tab:: IoT box
+
+      To check if the IoT box is up-to-date (and update it if needed), :ref:`access the IoT box's
+      homepage <iot/iot-box/homepage>`, click the :icon:`fa-cogs` (:guilabel:`cogs`) button at the
+      top-right, then :guilabel:`Update` in the :guilabel:`Version` section.
+
+      > **tip**:
+>          :ref:`Enable the developer mode <developer-mode>` to view the current versions of the IoT
+         box's image and core code.
+
+     **Image update**
+
+      To update the IoT box's image, flash its SD card. Flashing can be performed using
+      [balenaEtcher ](https://etcher.balena.io), a free and open-source tool for writing disk
+      images to SD cards.
+
+      > **note**:
+>          - Updating the IoT system's image is often required after upgrading the Odoo database to a
+           newer version.
+         - A computer with a micro SD card reader/adapter is required to flash the micro SD card.
+         - An alternative software for flashing the micro SD card is [Raspberry Pi Imager
+           ](https://www.raspberrypi.com/software/).
+
+      #. [Download balenaEtcher. ](https://etcher.balena.io/#download-etcher)
+      #. Insert the IoT box's micro SD card into the computer or adapter.
+      #. Open balenaEtcher, click :guilabel:`Flash from URL`, and enter the following URL:
+         `http://nightly.odoo.com/master/iotbox/iotbox-latest.zip`.
+      #. Click :guilabel:`Select target` and select the SD card.
+      #. Click :guilabel:`Flash` and wait for the process to finish.
+
+      .. image:: updating_iot/etcher-flash.png
+         :alt:  Flashing the SD card with balenaEtcher
+
+     **Core code update**
+
+      To update the IoT box's core code, click :guilabel:`Update` under :guilabel:`IoT Box Update`
+      in the :guilabel:`Update` popup.
+
+      .. danger::
+         This process may take over 30 minutes. **Do not turn off or unplug the IoT box** during
+         this time, as doing so could leave the device in an inconsistent state, requiring the IoT
+         box to be reflashed with a new image.
+
+   .. group-tab:: Windows virtual IoT
+
+      To update the Windows virtual IoT's image and code, :ref:`uninstall the program
+      <iot/windows_iot/uninstall>` and :ref:`reinstall <iot/windows-iot/installation>` the latest
+      package.
+
+.. _iot_updating_iot/handlers:
+
+# Handler (driver) update
+
+To update the IoT system's handlers (i.e., drivers and interfaces) and synchronize them with the
+configured server handler's code, for example, to resolve issues where :doc:`devices <../devices>`
+are not functioning properly with the IoT system, proceed as follows:
+
+#. Access the :ref:`IoT box's <iot/iot-box/homepage>` or :ref:`Windows virtual IoT's
+   <iot/windows-iot/homepage>` homepage and click the :icon:`fa-cogs` (:guilabel:`cogs`) button at
+   the top-right.
+#. Click :guilabel:`Update` in the :guilabel:`Version` section.
+#. In the :guilabel:`Update` popup that opens, click :guilabel:`Force Drivers Update`.
+
+> **important**:
+>    If you have an :doc:`on-premise </administration/on_premise>` or :doc:`Odoo.sh
+   </administration/odoo_sh/overview/introduction>` database, the configured server must be
+   up-to-date to ensure the handlers' code includes the latest fixes and patches.
+
+> **note**:
+>    A handler update is also performed automatically every time the IoT system is restarted unless
+   the :guilabel:`Automatic drivers update` option is disabled in the :guilabel:`Technical
+   information` tab in the :ref:`IoT system's form <iot/connect/IoT-form>` in Odoo.

package/payload/skills/odoo18-docs/references/docs/applications/general/iot/iot_advanced.md

@@ -0,0 +1,14 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot/iot_advanced.html"
+---
+
+:nosearch:
+# 
+# Advanced
+
+.. toctree::
+
+   iot_advanced/https_certificate_iot
+   iot_advanced/updating_iot
+   iot_advanced/ssh_connect

package/payload/skills/odoo18-docs/references/docs/applications/general/iot/iot_box.md

@@ -0,0 +1,94 @@
+---
+title: "IoT box"
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot/iot_box.html"
+---
+
+=======
+# IoT box
+
+To start using an IoT box:
+
+#. Make sure you have a :ref:`valid IoT box subscription <iot/iot/iot-subscription>` in addition to
+   your Odoo subscription.
+#. Connect your :doc:`devices <devices>` to the IoT box.
+#. :ref:`Connect the IoT box to the network <iot/iot_box/network>`.
+#. :doc:`Connect the IoT box to your Odoo database <connect>`.
+
+.. seealso::
+   [Video: How to Set Up and Use the Odoo IoT Box: A Beginner's Guide ](https://www.youtube.com/watch?v=w2_Dcm3r_7o&ab_channel=Odoo)
+
+> **note**:
+>    Devices can also be connected after the IoT box is added to the network and/or connected to the
+   database; however, a reboot of the IoT box might be required.
+
+.. _iot/iot_box/network:
+
+# Network connection
+
+The IoT box can be connected to the network via :ref:`Ethernet <iot/iot_box/network-ethernet>` or
+:ref:`Wi-Fi <iot/iot_box/network-wifi>`.
+
+> **important**:
+>    **All** devices must be connected to the **same network**: the IoT box, the device(s) connected
+   to the IoT box, and the computer connected to Odoo.
+
+.. _iot/iot_box/network-ethernet:
+
+## Ethernet
+
+Plug the Ethernet cable into the IoT box's Ethernet port and an available port on your router, then
+connect the IoT box to a power source.
+
+.. _iot/iot_box/network-wifi:
+
+## Wi-Fi
+
+Make sure no Ethernet cable is connected to the IoT box and follow these steps:
+
+  #. Connect the IoT box to a power source and wait a few minutes for it to power on.
+  #. Access your computer's Wi-Fi settings and select the IoT box's network. The network name is in
+     the format `IoTBox-xxxxxxxxxxxx` (where `xxxxxxxxxxxx` is a unique identifier).
+  #. Connect to the IoT box's Wi-Fi network and sign into it; your browser should automatically
+     open and redirect to the :ref:`IoT box's homepage <iot/iot-box/homepage>`.
+
+     > **note**:
+>         Depending on your operating system, the browser might not open and redirect to the IoT box's
+        homepage. In this case, open your browser manually and navigate to `http://10.11.12.1`
+        or any url starting with **http** (e.g., `http://odoo.com`).
+
+  #. On the IoT box's homepage, click :guilabel:`Configure` next to the :guilabel:`Internet Status`
+     section.
+  #. Wait a few minutes for the available networks to be scanned, select the network, enter the
+     Wi-Fi's password, and click :guilabel:`Connect`.
+
+> **note**:
+>    Once connected to the Wi-Fi network, the IoT box stops emitting its Wi-Fi signal, and the
+   computer should automatically reconnect to its original network. If it does not, reconnect to it
+   manually.
+
+.. _iot/iot-box/homepage:
+
+# IoT box homepage
+
+To access the IoT box's homepage, open a web browser **on the same network as the IoT box** and
+navigate to the IoT box's IP address.
+
+.. image:: iot_box/iot-homepage.png
+   :scale: 75%
+   :alt: IoT box's homepage
+
+The IoT box's IP address can be retrieved by:
+
+- connecting the IoT box to an external monitor: the IP address is displayed on the screen.
+
+  .. image:: iot_box/iot-pos-display.png
+     :scale: 75%
+     :alt: POS display with IoT box's IP address
+
+- connecting the IoT box to a [supported receipt or label printer ](https://www.odoo.com/fr_FR/app/iot-hardware)
+  with a USB cable: the IP address is automatically printed.
+- accessing the administrator interface of the router to which the IoT box is connected or using
+  third-party software to scan the network.
+
+Once the IoT box is :doc:`connected to the Odoo database <connect>`, its homepage can be accessed
+from Odoo by opening the IoT app and clicking the URL displayed on the IoT box's card.

package/payload/skills/odoo18-docs/references/docs/applications/general/iot/windows_iot.md

@@ -0,0 +1,171 @@
+---
+title: "Windows virtual IoT"
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot/windows_iot.html"
+---
+
+===================
+# Windows virtual IoT
+
+To start using the Windows virtual IoT:
+
+#. Make sure all :ref:`prerequisites <iot/windows-iot/prerequisites>` are met.
+#. :ref:`Install the Windows virtual IoT <iot/windows-iot/installation>` on a Windows computer.
+#. :ref:`Configure the Windows Firewall <iot/windows-iot/firewall>`.
+#. Connect your :doc:`devices <devices>` to the Windows virtual IoT.
+#. :doc:`Connect the Windows virtual IoT to your Odoo database <connect>`.
+
+.. _iot/windows-iot/prerequisites:
+
+# Prerequisites
+
+The following prerequisites must be met before setting up and using the Windows virtual IoT:
+
+- A valid :ref:`IoT box subscription <iot/iot/iot-subscription>`.
+- An updated and recent version of Windows (i.e., Windows 10 or Windows 11) installed on a Windows
+  computer (laptop, desktop, or server).
+
+> **note**:
+>    - :abbr:`MRP (Material Requirement Planning)` devices, including cameras and measurement tools,
+     are not compatible with Windows virtual IoT.
+   - It is also possible to create a Windows Virtual Machine on a MacOS/Linux computer. However,
+     this option is not supported by Odoo, and no troubleshooting assistance will be provided.
+
+.. _iot/windows-iot/installation:
+
+# Installation
+
+To install the Windows virtual IoT on a Windows computer:
+
+#. Access [Odoo's download page ](https://odoo.com/download) and download the Odoo installation
+   package for Windows **matching your database's version**.
+#. Open the downloaded :file:`.exe` file, allow the app to make changes to your device, select
+   a language, and click :guilabel:`OK`.
+#. Click :guilabel:`Next`, then :guilabel:`I Agree` to accept the terms and conditions and continue.
+#. Select :guilabel:`Odoo IoT` from the :guilabel:`Select the type of install` dropdown list. The
+   following components should be selected: Odoo Server, Odoo IoT, Nginx WebServer, and Ghostscript
+   interpreter.
+#. Verify you have the required space on your computer and click :guilabel:`Next`.
+#. In the :guilabel:`Destination folder`, enter C:\\odoo and click :guilabel:`Install`.
+
+   > **warning**:
+>       Do not install Odoo's Windows virtual IoT in any Windows user directory, as this can cause
+      issues with :ref:`iot/https_certificate_iot/generation`.
+
+#. Once the installation is complete, click :guilabel:`Next`.
+#. Set up GPL Ghostscript: Click :guilabel:`Next`, agree to the terms and conditions, click
+   :guilabel:`Install`, then :guilabel:`Finish`.
+#. Click :guilabel:`Next`, :guilabel:`Next`, and :guilabel:`Finish` to complete the setup. The
+   :ref:`IoT system's homepage <iot/windows-iot/homepage>` automatically opens in a web browser with
+   the URL `http://localhost:8069`.
+
+   > **tip**:
+>       If the web browser does not show anything, :ref:`restart <iot/windows_iot/restart>` the
+      Windows virtual IoT service.
+
+#. Check that you can access the :ref:`IoT system's homepage <iot/windows-iot/homepage>` in a web
+   browser:
+
+   - on the Windows virtual IoT computer, and
+   - on another device **on the same network as the IoT system** by navigating to the URL
+     `http://xxx:8069` (where `xxx` is the IoT system's IP address).
+   - on another device **on the same network as the IoT system** by navigating to the URL
+     `https://xxx` (where `xxx` is the IoT system's IP address) to test for :doc:`HTTPS
+     <iot_advanced/https_certificate_iot>` connection.
+
+     > **tip**:
+>         If you cannot access the :ref:`IoT system's homepage <iot/windows-iot/homepage>` from
+        another device, create a :ref:`Windows Firewall <iot/windows-iot/firewall>` rule to allow
+        communication through port `8069`.
+
+.. _iot/windows-iot/firewall:
+
+# Windows Firewall configuration
+
+Firewalls help keep devices secure but can sometimes block legitimate connections. If the Windows
+virtual IoT isn't accessible on the :abbr:`LAN (Local Area Network)`, for example from another
+device, it could be due to a firewall blocking the connection. To prevent this issue, configure
+exceptions for network discovery in the :abbr:`OS (Operating System)` or firewall settings.
+
+> **note**:
+>    If third-party firewall software is installed on the Windows computer, refer to the software's
+   documentation to configure firewall exceptions.
+
+To create a rule on Windows Defender and allow communication through port `8069`, follow these
+steps:
+
+#. Search the Windows start menu for `firewall` and select the :guilabel:`Windows Defender Firewall
+   with Advanced Security` app.
+#. In the left part of the window, select :guilabel:`Inbound Rules`.
+#. In the right part of the window, under :guilabel:`Actions`, click :guilabel:`New Rule`.
+#. In the :guilabel:`New Inbound Rule Wizard` that opens, select the :guilabel:`Port` type of rule
+   and click :guilabel:`Next`.
+#. On the :guilabel:`Protocols and Ports` page, make sure :guilabel:`TCP` and :guilabel:`Specified
+   local ports` are selected, enter the following in the field: `8069, 80, 443`, and click
+   :guilabel:`Next`.
+
+   > **note**:
+>       Other ports may be necessary depending on your IoT devices. For example, for the
+      :doc:`/applications/sales/point_of_sale/payment_methods/terminals/worldline` payment terminal,
+      add the `9050` port.
+
+#. On the :guilabel:`Action` page, select :guilabel:`Allow the connection` and click
+   :guilabel:`Next`.
+#. On the :guilabel:`Profile` page, disable any connection type(s) that don't apply to your
+   Windows computer and click :guilabel:`Next`.
+#. On the :guilabel:`Name` page, provide a :guilabel:`Name` (e.g., `Odoo`) and, optionally, a brief
+   :guilabel:`Description`, then click :guilabel:`Finish`.
+
+.. seealso::
+   [Windows Firewall rules documentation
+   ](https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/windows-firewall/rules)
+
+.. _iot/windows-iot/homepage:
+
+# Windows virtual IoT homepage
+
+To access the Windows virtual IoT's homepage, navigate to the URL `http://localhost:8069` on the
+Windows virtual IoT computer or open a web browser from another computer **on the same network as
+the IoT system** and navigate to the URL `http://xxx:8069` (where `xxx` is the IoT system's IP
+address).
+
+Once the Windows virtual IoT is :doc:`connected to the Odoo database <connect>`, its homepage can
+be accessed from Odoo by opening the IoT app and clicking the URL displayed on the IoT system's
+card.
+
+.. image:: windows_iot/iot-windows-homepage.png
+   :scale: 75%
+   :alt: Windows virtual IoT's homepage
+
+> **note**:
+>    Make sure the :ref:`Windows Firewall is configured <iot/windows-iot/firewall>` to allow access.
+
+# Device connection
+
+Most :doc:`devices <devices>` automatically connect to the Windows computer used for the Windows
+Virtual IoT through [Windows Plug and Play (PnP)
+](https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/introduction-to-plug-and-play).
+However, if Windows does not recognize the device automatically upon connection, the administrator
+may need to manually install the appropriate drivers.
+
+> **tip**:
+>    After connecting the devices to the computer, refresh the :ref:`IoT system's homepage
+   <iot/windows-iot/homepage>` to verify that the device is listed. If the device does not appear,
+   :ref:`reload the handlers <iot_updating_iot/handlers>` from the :ref:`IoT system's homepage
+   <iot/windows-iot/homepage>`.
+
+.. _iot/windows_iot/restart:
+
+# Windows virtual IoT restart
+
+To manually restart the Windows IoT server, search the Windows start menu for `services` and
+select the :guilabel:`Services` app. Scroll down to the :guilabel:`odoo-server-xxx` service (where
+`xxx` is the odoo version), right-click it, and select :guilabel:`Start` or :guilabel:`Restart`.
+
+.. _iot/windows_iot/uninstall:
+
+# Windows virtual IoT uninstall
+
+To uninstall the Windows virtual IoT, [uninstall
+](https://support.microsoft.com/en-us/windows/uninstall-or-remove-apps-and-programs-in-windows-4b55f974-2cc6-2d2b-d092-5905080eaf98#ID0EBD=Windows_11)
+the Odoo program on your Windows computer. Confirm the uninstallation and complete the steps in the
+:guilabel:`Odoo Uninstall` dialog.