ConnectionException for openFRED location table

[oemof]

ConnectionException for openFRED location table

[gnn]

Thanks for the report. The first code block which you posted should definitely work and we need to fix that. Are you installing the package from source? If so, based on which branch?
And then there's something in the output which doesn't match up with what I expected. I have to look into that.

[c-koehl]

I cloned the repository and installed the dependencies.
I remember having issues installing it via pip (3 weeks ago). Apparently if you install it via pip, an older version will be installed, because some files were missing and were different compared to the dev branch in github!

[nick-harder]

Hi, is there a solution for this issue already? I have tried running it on my PC and also on Binder, it doesn't work.

Also, when I run following code:
open_FRED_weather_windpowerlib_single_location = Weather( start=start_date, stop=end_date, locations=[location], heights=heights, variables=variables, **defaultdb())

I get following error:
`---------------------------------------------------------------------------
AttributeError Traceback (most recent call last)
in
3 heights=heights,
4 variables=variables,
----> 5 **defaultdb())

C:\ProgramData\Anaconda3\lib\site-packages\feedinlib\open_FRED.py in init(self, start, stop, locations, heights, variables, regions, session, db)
148 location_ids = [
149 l.id
--> 150 for l in chain(self.locations.values(), *self.regions.values())
151 ]
152

C:\ProgramData\Anaconda3\lib\site-packages\feedinlib\open_FRED.py in (.0)
148 location_ids = [
149 l.id
--> 150 for l in chain(self.locations.values(), *self.regions.values())
151 ]
152

AttributeError: 'NoneType' object has no attribute 'id'`

[p-snft]

I can reproduce the issue as reported by @nick-harder, also for the current dev. However, I do not have the appropriate knowledga about open_FRED, to fix it. @oemof/feedinlib, could anyone of you help?

[gnn]

Sorry for taking so long to fix this and thanks for continuously prodding me. The issue that @nick-harder experienced and which @p-snft reproduced is different from the one originally reported. I'll try to reproduce both and probably will open a new issue for the former. In the long run, I'm hoping to have both issues fixed in a month.

[ADai528]

hi, @nick-harder. I also encountered the same problem, did you finally solve this problem?