]> git.basschouten.com Git - openhab-addons.git/commitdiff
Update README.md (#17270)
authorEmbeddedMe <nico@embeddedme.com>
Sat, 17 Aug 2024 19:54:35 +0000 (12:54 -0700)
committerGitHub <noreply@github.com>
Sat, 17 Aug 2024 19:54:35 +0000 (21:54 +0200)
Fixed typo for "ecovacs" folder name

Signed-off-by: EmbeddedMe <nico@embeddedme.com>
bundles/org.openhab.binding.ecovacs/README.md

index 80266490c117fd7e41f226a71292eb01e532539f..2a7e8573e0ca4ab87fbe93dc80ea871d7ae6e9a9 100644 (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).
 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)
 - 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