> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/solidsense/solidsense-software/kapua/using-eclipse-kapua-to-supervise-and-configure-solidsense-gateways.md). # Using Eclipse Kapua to supervise and configure SolidSense gateways {% hint style="warning" %} The documentation for SolidSense software is not maintained by SolidRun and the information herein is not actual with the latest version of the software, please contact our partner [SolidSense Connect](https://solidsense-connect.com/) who is now developing the SolidSense software.\ [Here](https://github.com/solidsense-connect/solidsense-connect-gateway/wiki) is the Solidsense-Connect WiKi documentation page. {% endhint %} ## Foreword Kapua is an Open Source cloud IoT platform managed by the Eclipse IoT group under the Eclipse foundation. It is made available to SolidSense users under the Eclipse license for test. The system can be used during Proof of Concept phase but is not intended to be used for production. There is no service warranty associated with the SolidSense Kapua instance. Full Kapua documentation can be found on: It is recommended for customer intending to use Kapua for their production environment to install their own instance in their production environment. ## Connecting to Kapua The current URL to access the SolidSense Kapua is [https://kapua.solidsense.io](https://kapua.solidsense.io/) To connect to Kapua you need the username and password that have been assigned to you for your account by Solid-Run. This is allowing you to access Kapua a see all gateways assigned to your organization and only these ones. This article is just a quick start guide for Kapua and does not by far describe all the available features. ![](/files/aH9Y3vzyOhgfpOUFSt1d) Then select **Devices** on the left to see all the gateways of your account ## Managing devices ![](/files/t53bksMpeQAuPGhNE5U0) Devices with a green plug are connected while those with a yellow plug are not yet reachable and no action can be performed on these gateways. By clicking on 1 gateway connected there several information actions that can be done using the series of tabs below. If a device that is expected to be seen is not appearing, this is most of the case a problem with the gateway MQTT credentials (account/username/password). Please re-check these parameters. ![](/files/d4t91Xntl2aWbcFPv8pV) ### Possible actions/information available * Description: access to the device/Kura main parameters * Tags => feature not described here * Events: list of all events related to the device. Allow to see when the device has been connected or disconnected. Events are available even if the device is not connected * Packages: list of optional packages (like the Wirepas configuration package) installed in Kura on the gateway. New package can also be added here. * Bundles: list of all software bundles (Java components) installed on the gateway. Linked to the OSGi framework. * Configuration: access to the configuration off all services running on the gateway and also to the configuration snapshots that can be downloaded for examination and uploaded to force a configuration change. Rollback to previous state can also be triggered here. * Commands: capability to send Linux command line commands to be executed on the gateway. The working directory in /tmp. Some files can be uploaded on the gateway (and will be stored in /tmp) in .zip format and will be unzipped automatically after download. Non zipped file will NOT be downloaded. This service (Command Service) needs to be enabled either on Kura or on Kapua before use. ![](/files/R7htSYorNFtS7cCkSliN) {% hint style="warning" %} **Please note** Changing the MQTT data transport parameters allow to re-parent a gateway to another account or another cloud, but if any parameter is wrong a direct connection to the gateway (via Kura web) will be needed to recover. {% endhint %} ![](/files/tKl11bPNJS9DtNfcDNNo) {% hint style="warning" %} **Please note** Commands are executed as root and there is no control nor security mechanism. So to use with great care to avoid to put the gateway in a non reachable state to will force a field operation to recover it. {% endhint %} ## Managing Kapua account ### Adding user(s) to your account It is always possible to add new users to your account using the Users screen ![](/files/C4ISNqEDXA2N0oD9H1gy) Click on the +add button and a pop-up window will open asking for the user name and password. Warning password rule is enforced and you need to follow the indications. After the user as been created you need to assign to him a role and permissions otherwise it will not be able to perform any task. This is done using the bottom part of the screen with the Roles and Permissions tab. ### Adding Child Accounts This is a powerful feature of Kapua. You can create a hierarchy of accounts to which user and gateways will be attached. Users belonging to an account at one particular level of the hierarchy will have access to all gateway that account and all child accounts. This is mainly used to create multi-tenant schemes where you can create child accounts per customer (or site or whatever) and then create accounts for gateways and users in that specific account. ![](/files/baKkEMTUYKXnzCGz1rZj) After creating a child account you need to adjust the following settings: * Account service: to allow child accounts to be created from that account, so one more level in the herarchy * Device Registry service: to allow devices (gateways) to connect to this Kapua instance * User service: to allow creation of users associated with that account Then we recommend to create 2 users associated with the new account: * One for the Kapua login with the admin role * One for the gateways with the thing role --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://dev.solid-run.com/solidsense/solidsense-software/kapua/using-eclipse-kapua-to-supervise-and-configure-solidsense-gateways.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.