wandelbots-api-client 25.9.0.dev14__tar.gz → 25.9.0.dev16__tar.gz

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: wandelbots_api_client
-Version: 25.9.0.dev14
+Version: 25.9.0.dev16
 Summary: Wandelbots Python Client: Interact with robots in an easy and intuitive way. 
 Home-page: 
 Author: Copyright (c) 2025 Wandelbots GmbH
@@ -34,7 +34,7 @@ Dynamic: license-file
 Interact with robots in an easy and intuitive way.
 
 - Compatible API version: 1.0.0 (can be found at the home screen of your instance -> API)
-- Package version: 25.9.0.dev14
+- Package version: 25.9.0.dev16
 
 Sign up for our [Wandelbots Developers Beta program](https://www.wandelbots.com/developers-beta) to get access to the Wandelbots API.
 

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/README.md

@@ -2,7 +2,7 @@
 Interact with robots in an easy and intuitive way.
 
 - Compatible API version: 1.0.0 (can be found at the home screen of your instance -> API)
-- Package version: 25.9.0.dev14
+- Package version: 25.9.0.dev16
 
 Sign up for our [Wandelbots Developers Beta program](https://www.wandelbots.com/developers-beta) to get access to the Wandelbots API.
 

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "wandelbots_api_client"
-version = "25.9.0.dev14"
+version = "25.9.0.dev16"
 description = "Wandelbots Python Client: Interact with robots in an easy and intuitive way. "
 authors = [{ name="Copyright (c) 2025 Wandelbots GmbH", email="contact@wandelbots.com" }]
 license = "Apache-2.0"

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/setup.py

@@ -21,7 +21,7 @@ from setuptools import setup, find_packages  # noqa: H301
 # prerequisite: setuptools
 # http://pypi.python.org/pypi/setuptools
 NAME = "wandelbots-api-client"
-VERSION = "25.9.0.dev14"
+VERSION = "25.9.0.dev16"
 PYTHON_REQUIRES = ">= 3.8"
 REQUIRES = [
     "urllib3 >= 1.25.3, < 3.0.0",

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/wandelbots_api_client/__init__.py

@@ -14,7 +14,7 @@
 """  # noqa: E501
 
 
-__version__ = "25.9.0.dev14"
+__version__ = "25.9.0.dev16"
 
 from . import models
 from . import api

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/wandelbots_api_client/api_client.py

@@ -90,7 +90,7 @@ class ApiClient:
             self.default_headers[header_name] = header_value
         self.cookie = cookie
         # Set default User-Agent.
-        self.user_agent = 'Wandelbots-Nova-API-Python-Client/25.9.0.dev14'
+        self.user_agent = 'Wandelbots-Nova-API-Python-Client/25.9.0.dev16'
         self.client_side_validation = configuration.client_side_validation
 
     async def __aenter__(self):

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/wandelbots_api_client/configuration.py

@@ -524,7 +524,7 @@ conf = wandelbots_api_client.Configuration(
                "OS: {env}\n"\
                "Python Version: {pyversion}\n"\
                "Version of the API: 1.0.0\n"\
-               "SDK Package Version: 25.9.0.dev14".\
+               "SDK Package Version: 25.9.0.dev16".\
                format(env=sys.platform, pyversion=sys.version)
 
     def get_host_settings(self) -> List[HostSetting]:

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/wandelbots_api_client/v2/__init__.py

@@ -14,7 +14,7 @@
 """  # noqa: E501
 
 
-__version__ = "25.9.0.dev14"
+__version__ = "25.9.0.dev16"
 
 from . import models
 from . import api

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/wandelbots_api_client/v2/api/application_api.py

@@ -65,7 +65,7 @@ class ApplicationApi:
     ) -> None:
         """Add Application
 
-        Install a basic, containerized web application to the cell to control robots with a customized frontend.  Prerequisites: A Docker hub account or similar container registry account, with valid credentials.  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](/docs/docs/development/) for more information.  <!-- theme: none --> > #### Predefined Environment Variables > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application's root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application. 
+        Install a basic, containerized web application to the cell to control robots with a customized frontend.  #### Prerequisites - A Docker hub account or similar container registry account, with valid credentials.  #### Workflow  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](https://docs.wandelbots.io/latest/developing-introduction) for more information.  #### Predefined environment variables  <!-- theme: NOTE --> > **NOTE** > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application's root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -142,7 +142,7 @@ class ApplicationApi:
     ) -> ApiResponse[None]:
         """Add Application
 
-        Install a basic, containerized web application to the cell to control robots with a customized frontend.  Prerequisites: A Docker hub account or similar container registry account, with valid credentials.  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](/docs/docs/development/) for more information.  <!-- theme: none --> > #### Predefined Environment Variables > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application's root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application. 
+        Install a basic, containerized web application to the cell to control robots with a customized frontend.  #### Prerequisites - A Docker hub account or similar container registry account, with valid credentials.  #### Workflow  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](https://docs.wandelbots.io/latest/developing-introduction) for more information.  #### Predefined environment variables  <!-- theme: NOTE --> > **NOTE** > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application's root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -219,7 +219,7 @@ class ApplicationApi:
     ) -> RESTResponseType:
         """Add Application
 
-        Install a basic, containerized web application to the cell to control robots with a customized frontend.  Prerequisites: A Docker hub account or similar container registry account, with valid credentials.  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](/docs/docs/development/) for more information.  <!-- theme: none --> > #### Predefined Environment Variables > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application's root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application. 
+        Install a basic, containerized web application to the cell to control robots with a customized frontend.  #### Prerequisites - A Docker hub account or similar container registry account, with valid credentials.  #### Workflow  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](https://docs.wandelbots.io/latest/developing-introduction) for more information.  #### Predefined environment variables  <!-- theme: NOTE --> > **NOTE** > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application's root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -944,7 +944,7 @@ class ApplicationApi:
     ) -> App:
         """Configuration
 
-        Get the configuration for an active GUI application in the cell. To update the configuration of a GUI application in the cell, use this configuration with the 'Update Configuration' endpoint. 
+        Get the configuration for an active GUI application in the cell.  To update the configuration of a GUI application in the cell, use this configuration with [updateApp](updateApp). 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -1016,7 +1016,7 @@ class ApplicationApi:
     ) -> ApiResponse[App]:
         """Configuration
 
-        Get the configuration for an active GUI application in the cell. To update the configuration of a GUI application in the cell, use this configuration with the 'Update Configuration' endpoint. 
+        Get the configuration for an active GUI application in the cell.  To update the configuration of a GUI application in the cell, use this configuration with [updateApp](updateApp). 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -1088,7 +1088,7 @@ class ApplicationApi:
     ) -> RESTResponseType:
         """Configuration
 
-        Get the configuration for an active GUI application in the cell. To update the configuration of a GUI application in the cell, use this configuration with the 'Update Configuration' endpoint. 
+        Get the configuration for an active GUI application in the cell.  To update the configuration of a GUI application in the cell, use this configuration with [updateApp](updateApp). 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -1219,7 +1219,7 @@ class ApplicationApi:
     ) -> List[str]:
         """List Applications
 
-        List all GUI applications that have been added to a cell. with the 'Add Application' endpoint. If the cell does not contain GUI applications, the list is returned empty. 
+        List all GUI applications that have been added to a cell with [addApp](addApp).  If the cell does not contain GUI applications, the list is returned empty. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -1286,7 +1286,7 @@ class ApplicationApi:
     ) -> ApiResponse[List[str]]:
         """List Applications
 
-        List all GUI applications that have been added to a cell. with the 'Add Application' endpoint. If the cell does not contain GUI applications, the list is returned empty. 
+        List all GUI applications that have been added to a cell with [addApp](addApp).  If the cell does not contain GUI applications, the list is returned empty. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -1353,7 +1353,7 @@ class ApplicationApi:
     ) -> RESTResponseType:
         """List Applications
 
-        List all GUI applications that have been added to a cell. with the 'Add Application' endpoint. If the cell does not contain GUI applications, the list is returned empty. 
+        List all GUI applications that have been added to a cell with [addApp](addApp).  If the cell does not contain GUI applications, the list is returned empty. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/wandelbots_api_client/v2/api/bus_inputs_outputs_api.py

@@ -387,7 +387,7 @@ class BUSInputsOutputsApi:
     ) -> None:
         """Add PROFINET Input/Output
 
-        Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g. NOVA's PROFINET service.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal). 
+        Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g., NOVA's PROFINET service.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. - The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService)   and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. - The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding third party software, e.g., TIA portal). 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -464,7 +464,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[None]:
         """Add PROFINET Input/Output
 
-        Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g. NOVA's PROFINET service.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal). 
+        Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g., NOVA's PROFINET service.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. - The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService)   and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. - The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding third party software, e.g., TIA portal). 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -541,7 +541,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """Add PROFINET Input/Output
 
-        Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g. NOVA's PROFINET service.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal). 
+        Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g., NOVA's PROFINET service.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. - The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService)   and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. - The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding third party software, e.g., TIA portal). 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -974,7 +974,7 @@ class BUSInputsOutputsApi:
     ) -> None:
         """Remove PROFINET Input/Ouptut
 
-        Removes an input/output variable configuration from the PROFINET device, e.g. NOVA's PROFINET service. 
+        Removes an input/output variable configuration from the PROFINET device, e.g., NOVA's PROFINET service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -1047,7 +1047,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[None]:
         """Remove PROFINET Input/Ouptut
 
-        Removes an input/output variable configuration from the PROFINET device, e.g. NOVA's PROFINET service. 
+        Removes an input/output variable configuration from the PROFINET device, e.g., NOVA's PROFINET service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -1120,7 +1120,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """Remove PROFINET Input/Ouptut
 
-        Removes an input/output variable configuration from the PROFINET device, e.g. NOVA's PROFINET service. 
+        Removes an input/output variable configuration from the PROFINET device, e.g., NOVA's PROFINET service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2322,7 +2322,7 @@ class BUSInputsOutputsApi:
     ) -> str:
         """PROFINET Inputs/Outputs to File
 
-        Get input/output variable configuration of the PROFINET device, e.g. NOVA's PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g. TIA portal. 
+        Get input/output variable configuration of the PROFINET device, e.g., NOVA's PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g., TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2399,7 +2399,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[str]:
         """PROFINET Inputs/Outputs to File
 
-        Get input/output variable configuration of the PROFINET device, e.g. NOVA's PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g. TIA portal. 
+        Get input/output variable configuration of the PROFINET device, e.g., NOVA's PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g., TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2476,7 +2476,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """PROFINET Inputs/Outputs to File
 
-        Get input/output variable configuration of the PROFINET device, e.g. NOVA's PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g. TIA portal. 
+        Get input/output variable configuration of the PROFINET device, e.g., NOVA's PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g., TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2618,7 +2618,7 @@ class BUSInputsOutputsApi:
     ) -> List[IODescription2]:
         """List Descriptions
 
-        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service. 
+        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information like name, type and unit. The input/output direction is given in perspective of the BUS service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2686,7 +2686,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[List[IODescription2]]:
         """List Descriptions
 
-        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service. 
+        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information like name, type and unit. The input/output direction is given in perspective of the BUS service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2754,7 +2754,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """List Descriptions
 
-        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service. 
+        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information like name, type and unit. The input/output direction is given in perspective of the BUS service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2879,7 +2879,7 @@ class BUSInputsOutputsApi:
     ) -> List[ProfinetIO]:
         """List PROFINET Input/Output Configuration
 
-        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
+        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information like name, type and unit. The input/output direction is given in perspective of the PROFINET Device, e.g., the configured PROFINET service.  - The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. - The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. - The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding third party software, e.g., TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2947,7 +2947,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[List[ProfinetIO]]:
         """List PROFINET Input/Output Configuration
 
-        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
+        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information like name, type and unit. The input/output direction is given in perspective of the PROFINET Device, e.g., the configured PROFINET service.  - The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. - The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. - The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding third party software, e.g., TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3015,7 +3015,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """List PROFINET Input/Output Configuration
 
-        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
+        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information like name, type and unit. The input/output direction is given in perspective of the PROFINET Device, e.g., the configured PROFINET service.  - The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. - The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. - The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding third party software, e.g., TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3434,7 +3434,7 @@ class BUSInputsOutputsApi:
     ) -> None:
         """Set PROFINET Inputs/Outputs from File
 
-        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
+        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. - The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService)   and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. - The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding engineering system, e.g., TIA portal.  #### Export variables You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g., TIA portal. - The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output)   is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3507,7 +3507,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[None]:
         """Set PROFINET Inputs/Outputs from File
 
-        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
+        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. - The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService)   and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. - The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding engineering system, e.g., TIA portal.  #### Export variables You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g., TIA portal. - The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output)   is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3580,7 +3580,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """Set PROFINET Inputs/Outputs from File
 
-        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
+        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. - The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService)   and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. - The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs).  For the PROFINET controller, e.g., a connected PLC, refer to the corresponding engineering system, e.g., TIA portal.  #### Export variables You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g., TIA portal. - The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output)   is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str

{wandelbots_api_client-25.9.0.dev14 → wandelbots_api_client-25.9.0.dev16}/wandelbots_api_client/v2/api/cell_api.py

@@ -347,7 +347,7 @@ class CellApi:
     ) -> None:
         """Add Cell
 
-        Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](docs/wandelbots-nova-api/#create-a-cell) for more information.
+        Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](https://docs.wandelbots.io/latest/setup-cell) for more information.
 
         :param cell: (required)
         :type cell: Cell
@@ -421,7 +421,7 @@ class CellApi:
     ) -> ApiResponse[None]:
         """Add Cell
 
-        Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](docs/wandelbots-nova-api/#create-a-cell) for more information.
+        Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](https://docs.wandelbots.io/latest/setup-cell) for more information.
 
         :param cell: (required)
         :type cell: Cell
@@ -495,7 +495,7 @@ class CellApi:
     ) -> RESTResponseType:
         """Add Cell
 
-        Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](docs/wandelbots-nova-api/#create-a-cell) for more information.
+        Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](https://docs.wandelbots.io/latest/setup-cell) for more information.
 
         :param cell: (required)
         :type cell: Cell
@@ -643,7 +643,7 @@ class CellApi:
     ) -> Cell:
         """Configuration
 
-        List all cell resources.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman. 
+        List all cell resources. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -711,7 +711,7 @@ class CellApi:
     ) -> ApiResponse[Cell]:
         """Configuration
 
-        List all cell resources.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman. 
+        List all cell resources. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -779,7 +779,7 @@ class CellApi:
     ) -> RESTResponseType:
         """Configuration
 
-        List all cell resources.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman. 
+        List all cell resources. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str