@iobroker/dm-utils 1.0.0 → 1.0.1

package/README.md

@@ -114,7 +114,7 @@ In most cases, you will get all states of your instance and fill the array with
 
 Every array entry is an object of type `DeviceInfo` which has the following properties:
 
-- `id` (string): a unique (human readable) identifier of the device (it must be unique for your adapter instance only)
+- `id` (string): a unique (human-readable) identifier of the device (it must be unique for your adapter instance only)
 - `name` (string or translations): the human-readable name of this device
 - `status` (optional): the current status of the device, which can be one of:
   - `"disconnected"`
@@ -197,8 +197,8 @@ This method is called when the user clicks on a control (i.e., slider) in the de
 
 The parameters of this method are:
 - `deviceId` (string): the `id` that was given in `listDevices()` --> `[].id`
-- `controlId` (string): the `id` that was given in `listDevices()` --> `[].controls[].id`
-- `state` (string | number | boolean): new state for the control, that will be sent to real device
+- `controlId` (string): the `id` that was given in `listDevices()` --> `[].controls[].id`. There are some reserved control names, you can find the list below.
+- `state` (string | number | boolean): new state for the control, that will be sent to a real device
 - `context` (object): object containing helper methods that can be used when executing the action
 
 The returned object must contain:
@@ -206,6 +206,9 @@ The returned object must contain:
 
 This method can be implemented asynchronously and can take a lot of time to complete.
 
+Reserved control names:
+- `disabled` - The disabled control has its own pre-defined place on the device card and is used to disable the device. The state of this control is boolean.
+
 ### `handleDeviceControlState(deviceId: string, controlId: string, context: MessageContext)
 
 This method is called when GUI requests the update of the state.
@@ -226,7 +229,11 @@ To allow your adapter to interact with the user, you can use "actions".
 
 As described above, there are actions on the instance and on devices. The behavior of both methods is similar.
 
-Inside an action method (`handleInstanceAction()` or `handleDeviceAction()`) you can perform arbitrary actions, like talking to a device or API, and you can interact with the user. For interactions, there are methods you can call on `context`:
+Inside an action method (`handleInstanceAction()` or `handleDeviceAction()`) you can perform arbitrary actions, like talking to a device or API, and you can interact with the user.
+For interactions, there are methods you can call on `context`:
+
+There are some reserved action names, you can find the list below:
+- `status` - This action is called when the user clicks on the status icon. So to implement the "click-on-status" functionality, the developer has to implement this action.
 
 ### `showMessage(text: ioBroker.StringOrTranslated)`
 
@@ -295,6 +302,10 @@ This method returns a promise that resolves to a `ProgressDialog` object.
 	### **WORK IN PROGRESS**
 -->
 ## Changelog
+### 1.0.1 (2025-01-09)
+
+* (@GermanBluefox) Added description for `disabled` control and `status` action.
+
 ### 1.0.0 (2025-01-08)
 
 * (@GermanBluefox) Added `disabled` options for a device

package/build/types/base.d.ts

@@ -101,8 +101,7 @@ export interface DeviceInfo<T extends ActionType = 'api'> {
     actions?: DeviceAction<T>[];
     controls?: DeviceControl<T>[];
     hasDetails?: boolean;
-    /** undefined means, no "disabled" possibility, true means disabled, false means enabled */
-    disabled?: boolean;
+    /** Device type for grouping */
     group?: {
         key: string;
         name?: ioBroker.StringOrTranslated;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iobroker/dm-utils",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "ioBroker Device Manager utilities for backend",
   "main": "build/index.js",
   "publishConfig": {