Docs next (#3322)

* Add new custom user library location

* Change library location

* Update manual library details

Author: andrew-codechimp

docs/configuration.md

@@ -24,7 +24,7 @@ default_battery_low_threshold | Int | Optional | 10 | The default threshold wher
 battery_increase_threshold | Int | Optional | 25 | The threshold where the battery_notes_battery_increased event is fired, use this event for battery replaced automations. The threshold is the difference in increase between previous and current battery level. |
 hide_battery | Boolean | Optional | False | Hide the standard battery when adding Battery+. This will not effect existing dashboards, automations etc.|
 round_battery | Boolean | Optional | False | Round battery+ to whole percentages.|
-user_library | String | Optional |  | If specified then a user library file will be searched prior to the main library, the user library must be in the same format as the library and placed in the same folder. Only really used for dev purposes. |
+user_library | String | Optional |  | If specified then a user library file will be searched prior to the main library, the user library must be in the same format as the library and placed in the same folder (config/.storage/battery_notes). Only really used for dev purposes. |
 
 # Debug Logging
 

docs/library.md

@@ -16,15 +16,14 @@ Upon submission using the form above GitHub will attempt to make the required co
 
 Fork the repository, add your device details to the JSON document `library/library.json`, and then submit a pull request. Do not enable GitHub Actions (disabled by default) as this will mess with the pull request and are unnecessary for a library submission.
 
-* The easiest way to get the correct device information is to add the device manually, on the battery type panel you will see a summary at the top of the details required to add to the library.  This is also available if you go into configure of the device in battery notes.
-* The manufacturer and model should be exactly what is displayed on the Device screen within Home Assistant. If the Device screen has a Model ID or Hardware Version then this should be included.
-* In some rare cases models could contain unique identifiers and you want the battery type to apply to all models that match a pattern, in these instances you can use the optional model_match_method attribute.  For example Apple iPhone's have a model of iPhoneXX.X but all have a rechargeable battery, here you could use the "model_match_method": "startswith" and just specify iPhone as the model.
-* The manufacturer & model names may be different between integrations such as Zigbee2MQTT and ZHA, if you see a similar device please duplicate the entry rather than changing it.
-* The `battery_quantity` data is numeric (no quotes) and optional. If a device only requires a single battery, it should be omitted.
-* The `battery_type` data should follow the most common naming for general batteries (ex. AAA, D) and the IEC naming for battery cells according to [Wikipedia](https://en.wikipedia.org/wiki/List_of_battery_sizes) (ex. CR2032, 18650)
-* If a device has a bespoke rechargeable battery you can use `"battery_type": "Rechargeable"`
-* For devices like smoke alarms where the battery is not replaceable you can use `"battery_type": "Irreplaceable"`
-* If a device shouldn't be discovered because there are multiple revisions with the same model number but different battery types it can be added to the library with a `"battery_type": "MANUAL"` to note it is a device that shouldn't have a battery definition added to the library to save removal/re-add because people don't realise there are variants.
+- The easiest way to get the correct device information is to add the device manually to Battery Notes, on the battery type panel you will see a summary at the top of the details required to add to the library. This is also available if you go into configure of the device in battery notes.
+- In some rare cases models could contain unique identifiers and you want the battery type to apply to all models that match a pattern, in these instances you can use the optional model_match_method attribute. For example Apple iPhone's have a model of iPhoneXX.X but all have a rechargeable battery, here you could use the "model_match_method": "startswith" and just specify iPhone as the model.
+- The manufacturer & model names may be different between integrations such as Zigbee2MQTT and ZHA, if you see a similar device please duplicate the entry rather than changing it.
+- The `battery_quantity` data is numeric (no quotes) and optional. If a device only requires a single battery, it should be omitted.
+- The `battery_type` data should follow the most common naming for general batteries (ex. AAA, D) and the IEC naming for battery cells according to [Wikipedia](https://en.wikipedia.org/wiki/List_of_battery_sizes) (ex. CR2032, 18650)
+- If a device has a bespoke rechargeable battery you can use `"battery_type": "Rechargeable"`
+- For devices like smoke alarms where the battery is not replaceable you can use `"battery_type": "Irreplaceable"`
+- If a device shouldn't be discovered because there are multiple revisions with the same model number but different battery types it can be added to the library with a `"battery_type": "MANUAL"` to note it is a device that shouldn't have a battery definition added to the library to save removal/re-add because people don't realise there are variants.
 
 For the example image below, your JSON entry will look like this: