Skip to content

Commit a710a7d

Browse files
committed
Add clarification in README on which decimal separator must be used
Fixes: #80 Signed-off-by: rany <rany2@riseup.net>
1 parent c877541 commit a710a7d

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

README.md

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -31,20 +31,14 @@ The integration supports multiple PV arrays. For array-capable fields, you can e
3131
- a single scalar value (applied to all arrays), or
3232
- a comma-separated list of values (one value per array).
3333

34-
Required per-array fields are:
34+
All numeric parameter values must use a decimal point (`.`), even in locales that commonly use a decimal comma (for example German).
3535

36-
- `latitude`
37-
- `longitude`
38-
- `declination`
39-
- `azimuth`
40-
- `modules_power`
36+
Using decimal commas can break parsing in multi-array configurations. For example:
4137

42-
Optional per-array fields are:
38+
- `damping_factor`: `0,4,0,5` is interpreted as four list items, not two decimals (`0.4,0.5`).
39+
- `dc_efficiency`: `0,9` is interpreted as two arrays (`0` and `9`) instead of a single value (`0.9`).
4340

44-
- `efficiency_factor`
45-
- `use_horizon`
46-
- `partial_shading`
47-
- `horizon_filepath`
41+
Use `.` for decimals and `,` only as the list separator between arrays.
4842

4943
Examples:
5044

0 commit comments

Comments
 (0)