Community
Suited for DIY people, developers and enthusiasts
Last updated
Suited for DIY people, developers and enthusiasts
Last updated
Check the overall performance of the system, and get insights about the devices as their type, total quantity and status.
Table list with all the devices connected to Oktopus, independent of the protocol used for management, all of them will appear in this list, with options to filter for specific devices characteristics, and remove or add table fields to view.
Acces the device you wish and discover the data model dinamically.
This feature is only available for USP devices.
Send custom USP or CWMP native packets, in this section you can create custom protocols messages according to the specification. The available actions are to create, read, update and delete (CRUD).
This section defines credentials to be used by the devices to connect to Oktopus Controller, those credentials are going to be attached to the ACS, MQTT, STOMP and Websockets instances that will now check if the device has the correct keys.
For this to work you need to enable this feature through environment variables in each server/broker protocol you want to have authentication enabled.
The only protocol that still don't have support to this authentication process is STOMP, which follows another authentication mechanism in the moment.
There are two levels of users availables in the Community Edition:
Admin: Have access to the hole software platform, including the rights to remove/add users and devices credentials.
User: Can access devices and configure the same, view users, dashboard information and credentials, but is not allowed to remove/add other users and devices credentials.
