Gpslogger error since 0.94.2

Configuration
1

Hi,

Since upgrading to Hassio 0.94.2 this morning, the gpslogger suddenly stopped working.
I allready tried to update my webhook, same result:

2019-06-12 20:25:34 ERROR (MainThread) [homeassistant.setup] Error during setup of component device_tracker
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 153, in _async_setup_component
    hass, processed_config)
  File "/usr/src/homeassistant/homeassistant/components/device_tracker/__init__.py", line 115, in async_setup
    legacy_platforms = await setup.async_extract_config(hass, config)
  File "/usr/src/homeassistant/homeassistant/components/device_tracker/setup.py", line 109, in async_extract_config
    platform.name, platform.type))
ValueError: Unable to determine type for gpslogger: None

configuration.yaml:

device_tracker:
  - platform: gpslogger

GPS Logger app (Android):
url:

https://<redacted>/api/webhook/1f4f0bca88fff58cced320085640d7.......................................

http body:

latitude=%LAT&longitude=%LON&device=%<MY_DEVICE>&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT

I don’t see any breaking changes regarding device trackers, did I miss something?
Anyone else having problems with this component?

2

Device tracker has been updated in 0.94:

Have a search on here; I, as well as others, had some issues but working now

3

@Holdestmade thanks, I missed that indeed.

But It still doesn’t make sence to me.

This release also introduces a long overdue overhaul of how the device tracker works. We are introducing this overhaul piece by piece, focusing first on device tracker platforms that push their updates to Home Assistant: mobile app, OwnTracks, GeoFency, GPSLogger and Locative.

These integrations will no longer use known_devices.yaml but instead use entities, like all other integrations in Home Assistant. You can change the name and entity ID via the UI. It is no longer posible to merge the devices with other device tracker entities. This was flaky at best. You should now use the new person integration for this.

How can this cause a component error on startup? There are no additional attributes to setup (right?).
Do I have to delete the &device=%<MY_DEVICE> in the http body of the app?

4

You need to delete the gpslogger from your config and set it up in integrations instead and delete only the gpslogger entry in known_devices.yaml

5

@Holdestmade thanks, I just figured it out.
Turns out only removing the line from configuration.yaml was enough (I allready setup persons in integrations).
Thanks for helping me out!

6

Just an FYI. There seems to be some confusion around the person component and the recent changes in the device_tracker component (and the integrations that create device_tracker entities.) The person component is not required to be configured or used in order to make device_tracker entities work. You can use the person component with device_tracker entities, but that is completely independent of the device_tracker's themselves.

1 Like