In the bars under “Energy usage”, I was expecting HomeAssistant to show the net usage for each time interval. But instead, it just shows the value of each sensor, which is really high, and meaningless.
The numbers under “Energy distribution” on the right under “Grid” and “Home” don’t make sense to me, also. Neither does the number under “Net consumed from the grid”.
My question is pretty broad, but really boils down to “How can I best utilize these sensors” in the Energy tab.
Responding to myself here - I think I see why the visualization is so odd.
Due to known stability issues with the device itself that Rainforest won’t fix (the device is past end of life), I reboot the Eagle with a smartplug every 3 hours. I also restart the integration at the same time, as there are stability problems with it also.
Ie. there are several minutes after the reboot during which the sensor incorrectly reports a 0 value. That messes up everything in the Energy tab.
I tried just manually reloading the integration, and this problem did not show. So, it looks like the issue is that when the device reboots, the integration collects wrong meter data temporarily.
I guess the next thing to try would be to disable the integration first, then reboot the device, wait long enough for it to be up, and then reload or re-enable the integration afterwards. I’m going to try that now. Sigh.
I’m not sure why it takes so long, or where it’s load it from (cloud ?). It should get the data over Zigbee from the meter itself. The “current usage” screen is available within less than one minute of the device booting up.
And the “Home power demand” sensor in HomeAssistant never records any bogus values (such as going to 0), unlike the other 2 sensors.
Seems this is yet another bug in the Rainforest Eagle integration. I could work around it by disabling the integration for 5-6 minutes after each reboot. But since I’m doing 8 reboots per day, that would cause a loss of 40-48 minutes of meter data per day, which is more than I’m willing to live with.
Guess this needs to be fixed in the Eagle integration. It should not report a 0 value for the meter sensors while the data is still loading …
So, there seems to be no way for me to work around these Eagle issues.
The following YAML reloads the integration, but it reloads it immediately, without the possibility of inserting a delay :