krioukov/LoCalProjects — Issue #2: Enphase sMAP config file interface improvement 
Author: krioukov
Created: 2012-01-28 17:18:43+00:00
State: open

Config File:
I didn't see one committed so I used the following:

```
[report 0]
ReportDeliveryLocation = http://new.openbms.org/backend/add/XXX

[/]
uuid = 6050b514-49cc-11e1-9675-eb8365a88b37
Metadata/SourceName = Enphase Solar

[/CA]
key = EnphaseBerkeley
type = enphase.EnphaseEnergy
City = Berkeley
State = CA
```

This works fine, but there is a problem when we want to add multiple cities. We can't have two /CA roots and there is no other way to specify multiple cities, because you automatically create the city sub-path. I suggest we either:
a) Allow users to specify a list of cities under each state (e.g. City = [Berkeley, Oakland]). You can assume the value of opt.City is a json string and parse accordingly.
or
b) Have the ini file specify the full path for each location and don't add any sub-paths. E.g:
```
[/CA/Berkeley]
type = enphase.EnphaseEnergy
City = Berkeley
State = CA
[/CA/Oakland]
type = enphase.EnphaseEnergy
City = Oakland
State = CA
```
This is a bit more verbose, but allows more flexible naming in the ini file.