Rainforest Eagle-200: "Retrying setup: 'Components'"

Configuration
1

Last night my Eagle-200 arrived and I plugged it in, sent a request to my energy provider to register the unit, and got it set up on the cloud, ready for when my meter is activated.

Home Assistant detected it (though I still had to fill out the Host field, which is unusual, because HA should have been able to grab the host (i.e. the IP address of the unit) from the setup?

Anyway, when I entered my cloud ID and the install code, the integration shows a red exclamation mark icon, with the word “Retrying setup: ‘Components’” next to it:

image

The logs show a similar error:

Logger: homeassistant.components.rainforest_eagle.data
Source: components/rainforest_eagle/data.py:154
Integration: Rainforest Eagle (documentation, issues)
First occurred: 10:44:05 AM (188 occurrences)
Last logged: 2:48:46 PM

Unexpected error fetching 00xxxx data: 'Components'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
    return await self.update_method()
  File "/usr/src/homeassistant/homeassistant/components/rainforest_eagle/data.py", line 154, in _async_update_data_200
    data = await eagle200_meter.get_device_query()
  File "/usr/local/lib/python3.9/site-packages/aioeagle/electric_meter.py", line 113, in get_device_query
    data["Device"]["Components"], "Component"
KeyError: 'Components'

Now, I’m still waiting for my energy provider to register the device (it’ll take ~10 days from what I’ve heard. Ugh!) but I’m not sure if this issue is related to that, or to a bug in the integration.

I’m on core-2021.11.3, and I’m not sure if older versions were working, because I just got this thing last night.

Has anyone else experienced any issues like this?

2

So an update on this: I was getting this error because my Eagle-200 hadn’t been paired with my meter yet. Once I got the message from AusNet saying it was paired, everything worked fine.

Would be nice if it just defaulted to 0 or something to avoid the error, but then again, the instructions do say to not plug the Eagle-200 in until the utility company gives the go-ahead, so that’s partly (mostly) on me.

3

Hey, great to hear your Eagle is connected to your meter. I was going to tell you the error you were experiencing was due to the meter and eagle not being connected, but seems you got there yourself.

I just recently tried integrating my Eagle 200 into my Energy dashboard, but am receiving some errors. Did you happen to have any issues integrating into your energy dashboard? Assuming that is what you did?

4

It should have given a more user-friendly error when not being able to connect, but I guess if you follow the instructions as written, you don’t see that error.

I haven’t had any issues yet (and yep, I added it to the Energy Dashboard, which was my reason for buying it). I’ve had some intermittent dropouts, but that could be because I’m powering it through my modem to save having to plug another wall wart in.