Problem with REST API in 0.83.2

Configuration
1

Hi all,

I encountered a problem with my setup:

I was using HASSIO v0.82.x on my RBPi3. I also run a MagicMirror in my flat which uses the MMM-homeassitant-sensors plugin to pull some sensor values via the REST-API. Unfortunately this broke when updating to 0.83.2. Now I only get an “error fetching states” message.

Could it be that something was changed in the REST API in V 0.83.x which broke my setup?

if I paste http://hassio:8123/api/states?api_password=XXXXXXX into firefox I don’t see any sensors

It would be great if someone could help

2

See

https://github.com/tkoeberl/MMM-homeassistant-sensors/issues/5

3

i don’t think that this is the problem as this behavior was definitely introduced by moving from 0.82 to 0.83.2 which was later that the date of this report or am I wrong?

4

from https://www.home-assistant.io/blog/

Release 0.83.3 - December 3

We had an issue where users that are still using the legacy auth for API access but not for UI access could end up with a legacy auth user without any permissions. If you run into this issue, we suggest to upgrade your scripts to use long lived access tokens, which offer the exact same functionality. Alternative is that you manually upgrade the legacy API user to be part of the admin group using these instructions.

5

Hi Kugelfang.

Were you able to get Magic Mirror working again?

I ran into the same issue with
HA 0.84.2
MM 2.6.0

The module “MMM-homeassistant-sensors” just shows me “error fetching stats”
What user should be created for MM when accessing HomeAssistant??

You help would be greatly appreciated…

Thx
bommel947

6

Yes, but I had to switch the plugin I use to fetch the data from my Home Assistant to a version which can handle the long lived tokens. You can find more details here