AttributeError: 'NoneType' object has no attribute 'zone' about core HOT 12 CLOSED

By default there should be no password and it should login right away. It
seems like some error has happened during your setup. How does your
configuration.yaml file look?

On Fri, May 15, 2015 at 10:10 AM, Frank [email protected] wrote:

Following the Getting Started https://home-assistant.io/getting-started/
on an Ubuntu 14.04 VM resulted in the interface loading but it is not
accepting a login.

The console shows the following exception:

Traceback (most recent call last):
File "/usr/lib/python3.4/socketserver.py", line 609, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.4/socketserver.py", line 344, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.4/socketserver.py", line 665, in init
self.handle()
File "/usr/lib/python3.4/http/server.py", line 398, in handle
self.handle_one_request()
File "/usr/lib/python3.4/http/server.py", line 386, in handle_one_request
method()
File "/opt/home-assistant/homeassistant/components/http.py", line 290, in do_GET
self._handle_request('GET')
File "/opt/home-assistant/homeassistant/components/http.py", line 274, in _handle_request
handle_request_method(self, path_match, data)
File "/opt/home-assistant/homeassistant/components/api.py", line 161, in _handle_get_api_bootstrap
'config': hass.config.as_dict(),
File "/opt/home-assistant/homeassistant/init.py", line 969, in as_dict
'time_zone': self.time_zone.zone,
AttributeError: 'NoneType' object has no attribute 'zone'

Is there anything else that is required before this works?
(Also, I had to Google for the default password as it isn't mentioned on
the getting started page.)

—
Reply to this email directly or view it on GitHub
#129.

PaulusSchoutsen.nl
It's nice to be important but it's more important to be nice.

from core.

Ah, the page didn't mention that any configuration was required :) That must be it, thanks!

from core.

Configuration is auto created on initial boot. It requires an Internet
connection to geo locate you to setup preferred time zone and temperature.

On Fri, May 15, 2015, 11:58 Frank [email protected] wrote:

Closed #129 #129.

—
Reply to this email directly or view it on GitHub
#129 (comment).

from core.

The internet connection worked fine though as I was able to clone the project & pull in its dependencies.

Odd, I should re-test this hopefully something else shows up in the logs indicating what went wrong here.

from core.

The generated config is:

homeassistant:
  longitude: 9
  time_zone: 
  temperature_unit: C
  name: Home
  latitude: 51

discovery:

frontend:

conversation:

history:

logbook:

Even after restarting HA it gives the error about it missing zone. Grepping for zone in the example only shows time_zone but even if I set this to a sensible value it doesn't work.

from core.

That's interesting that time_zone hasn't been set. Also latitude and longitude seem off.

We use https://freegeoip.net/json/ to fetch this data. What does going to that url return ?

from core.

Timezone isn't set because the FreeGeoIP return doesn't include it:

{"ip":"xxx.xxx.xxx.xxx","country_code":"DE","country_name":"Germany","region_code":"","region_name":"","city":"","zip_code":"","time_zone":"","latitude":51,"longitude":9,"metro_code":0}

FWIW its running off a dedicated server in Germany :-)

If I put in the latitude/longitude and timezone from what I get when calling that URL from home it still results in the same error.

from core.

Aargh, guess I can't trust FreeGeoIP to always return the correct data. I'll add it to my to do list to default to UTC.

For now, pick your favorite from this list and plug it into your configuration.yaml

from core.

I already tried to set it to Europe/Amsterdam (and America/Los_Angeles as mentioned in the example) but this doesn't work unfortunately.

The home-assistant.log contains the following line, perhaps its related to this issue?

08:06 16-05-15 homeassistant: hass.local_api is deprecated. Use hass.config.api

from core.

It's weird that both Europe/Amsterdam and America/Los_Angeles don't work as both should. I'll investigate that further.

I have put in a fix for the dev branch that should have time zone default to UTC when the frontend is fetching it: e0d697d

from core.

Seems to work fine now indeed (after switching to dev).
Thanks for the quick response and fix!

from core.

Paulus, just a heads up, the astral Python library has some code that gets
time zones and coordinates. It doesn't resolve IP addresses though. I'm not
sure if considering would be helpful or not.

Ryan Kraus

On Sat, May 16, 2015 at 2:37 AM, Frank [email protected] wrote:

Seems to work fine now indeed (after switching to dev).
Thanks for the quick response and fix!

—
Reply to this email directly or view it on GitHub
#129 (comment)
.

from core.