Skip to content

Commit

Permalink
Docs update
Browse files Browse the repository at this point in the history
  • Loading branch information
Yiğit Topcu committed Apr 1, 2024
1 parent c80f28b commit 4d99c69
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion custom_components/dreame_vacuum/translations/en.json
Original file line number Diff line number Diff line change
Expand Up @@ -788,7 +788,7 @@
}
},
"vacuum_set_restricted_zone": {
"name": "Set Restriced Zone",
"name": "Set Restricted Zone",
"description": "Define virtual walls, restricted zones, and/or no mop zones.",
"fields": {
"walls": {
Expand Down
2 changes: 1 addition & 1 deletion docs/entities.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
- Some entities may not be available on devices with older firmware versions like *customized_cleaning* and *cleaning_mode* that are also not available on valetudo.
- Most of the entities including the vacuum entity has dynamic icons for their state and can be overridden from entity settings.
- Most of the sensor and all select entities returns their current raw integer value on `raw_value`, `map_id` or `segment_id` attributes for ease of use on automations and services.
- All entities has dynamic refresh rate determined by its change range and device state. Integration only inform Home Assistant when a device property has changed trough listeners. This is more like a *local_push* type of approach instead of *local_pull* but please note that it may take time entity to reflect the changes when you edit related setting from the official App.
- All entities has dynamic refresh rate determined by its change range and device state. Integration only inform Home Assistant when a device property has changed through listeners. This is more like a *local_push* type of approach instead of *local_pull* but please note that it may take time entity to reflect the changes when you edit related setting from the official App.
- Some entities has custom availability rules for another specific entity or state. E.g. *tight_mopping* entity will become *unavailable* when water tank or mop pad is not attached. (All off the rules extracted from the official App)
- Exposed cloud connected entities for all available settings that are stored not on the device but on specific map data itself. E.g. *map_rotation*
- Generated entities have the following naming schema:
Expand Down
2 changes: 1 addition & 1 deletion docs/map.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ Automatically generated saved and live map entities for map editing and automati

<img src="https://raw.githubusercontent.com/Tasshack/dreame-vacuum/master/docs/media/map_entities.png" width="500px">

**<a href="https://github.com/Tasshack/dreame-vacuum/blob/master/docs/entites.md#select" target="_blank">For more info about map entities</a>**
**<a href="https://github.com/Tasshack/dreame-vacuum/blob/master/docs/entities.md#select" target="_blank">For more info about map entities</a>**

### Dynamic room entities for selected map

Expand Down

0 comments on commit 4d99c69

Please sign in to comment.