demus/openhab-addons
1
0
Fork 0
mirror of https://github.com/openhab/openhab-addons.git synced 2025-01-10 15:11:59 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md (#17270)

Browse Source 
Fixed typo for "ecovacs" folder name

Signed-off-by: EmbeddedMe <nico@embeddedme.com>
This commit is contained in:
EmbeddedMe 2024-08-17 12:54:35 -07:00 committed by GitHub
parent 22efa534c8
commit fa596bf503
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bundles/org.openhab.binding.ecovacs/README.md
View File

@ -185,7 +185,7 @@ In such a case, please [create an issue on GitHub](https://github.com/openhab/op
In addition to that, if the model is similar to an already supported one, you can try to add the support yourself (until getting an updated binding). In addition to that, if the model is similar to an already supported one, you can try to add the support yourself (until getting an updated binding).
For doing so, you can follow the following steps: For doing so, you can follow the following steps:
- create the folder `<OPENHAB_USERDATA>/evocacs` (if not done previously) - create the folder `<OPENHAB_USERDATA>/ecovacs` (if not done previously)
- create a file named `custom_device_descs.json`, whose format of that file is the same as [the built-in device list](https://raw.githubusercontent.com/openhab/openhab-addons/main/bundles/org.openhab.binding.ecovacs/src/main/resources/devices/supported_device_list.json) - create a file named `custom_device_descs.json`, whose format of that file is the same as [the built-in device list](https://raw.githubusercontent.com/openhab/openhab-addons/main/bundles/org.openhab.binding.ecovacs/src/main/resources/devices/supported_device_list.json)
- for a model that is very similar to an existing one, create an entry with `modelName`, `deviceClass` (from the log line) and `deviceClassLink` (`deviceClass` of the similar model) - for a model that is very similar to an existing one, create an entry with `modelName`, `deviceClass` (from the log line) and `deviceClassLink` (`deviceClass` of the similar model)
- for other models, you can also try experimenting with creating a full entry, but it's likely that the binding code will need to be updated in that case - for other models, you can also try experimenting with creating a full entry, but it's likely that the binding code will need to be updated in that case