api/states empty

[bh077881]

Home Assistant release with the issue:
83.0/83.1/83.2

Last working Home Assistant release (if known):
82.1

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Component/platform:
API

Description of problem:
After upgrade to 83.x /api/states using api_password returns an empty array "[]". Revert back to 82.1 and it works.

http://homeassistant/api/states?api_password=xxxxx

Log indicates that the request has been served

2018-12-02 06:58:14 INFO (MainThread) [homeassistant.components.http.view] Serving /api/states to 10.29.29.200 (auth: True)

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

http:
  # Secrets are defined in the file secrets.yaml
  api_password: !secret http_password
  server_port: 80

Traceback (if applicable):

Additional information:

[balloob]

Means the legacy API user is not part of the admin group. Did you ever change the auth file in Home Assistant and changed groups around?

[bh077881]

Thanks for the reply. I haven't manually modified any of the auth files. What should the Legacy API user look like? Currently is set as follows (this works in 0.82.1):

                "group_ids": [],
                "id": "e1aba709becb4196a27574b0b7816103",
                "is_active": true,
                "is_owner": false,
                "name": "Legacy API password user",
                "system_generated": false

[bh077881]

Changing to the following and restarting has resolved the problem

            {
                "group_ids": [
                    "system-admin"
                ],
                "id": "e1aba709becb4196a27574b0b7816103",
                "is_active": true,
                "is_owner": false,
                "name": "Legacy API password user",
                "system_generated": false
            }

[balloob]

hmm, glad you fixed your instance, but I am surprised that the user was not automatically converted, as should have happened. From what version did you upgrade?

[balloob]

Found the issue and will fix it in 0.83.3

[bh077881]

Hi Paulus, it was an upgrade from 0.82.1 but it looks like you've tracked it down, Thanks.

[AlanBarnettHA]

I experienced the same issue going from 0.82.1 to 0.83.3

[cryptooth]

Same issue here. 0.84.2

[balloob]

Solution in the linked PR above #18922