Rainforest Eagle 200 released
Collapse
X
-
after reading this whole thread i was not sure if the eagle-200 supported eagle push without any intervention by rainforest employees. however, it appears that at some point in the past rainforest did add the ability for end users to configure the push service on an eagle-200 themselves. furthermore it is an improvement over the original eagle in that it seems that you can add multiple cloud services to a single eagle-200 device. the only thing that i have not been able to figure out how to turn off is the push to the rainforest cloud service itself, as that seems to be built-in and non-user configurable. -
Wattvision seems to be down, not sure if it will come back. I've switched to using Eagle Post, which seems to be working ok. You configure it directly on your rainforest to push to PVoutput.
https://pvoutput.org/help.html#push-eaglepost
Yes There’s a thread started on the Wattvision board, but no response. I tweeted Wattvision, no response yet https://wattvision.readme.io/v1.0/discuss/5b298f333187ed0003a3ac15
Short version:
1. on pvoutput, DISABLE Secondary
2. On Rainforest Eagle website, remove wattvision from cloud settings
2. On Rainforest Eagle website, setup cloud to point to pvoutput (you will need your pvoutput site ID and api-key)
That's it.Last edited by joyjit; 06-23-2018, 11:08 PM.Leave a comment:
-
Wattvision seems to be down, not sure if it will come back. I've switched to using Eagle Post, which seems to be working ok. You configure it directly on your rainforest to push to PVoutput.
Leave a comment:
-
Here's a screenshot of the consumption (calculated from the utility net meter less production) cutting out in the morning just as the Enphase starts reporting. Evening is the reverse
pvoutput.pngAttached FilesLeave a comment:
-
Nice, glad to see they have this product finally available. No worries about accuracy, it is communicating directly with your meter and reports exactly what it sees. You'll need another source of data if you want to separate out generation and consumption, since this only shows what is either imported from or exported to the grid.
A decent setup (usually 1-2% accurate on clear day, worse on cloudy days) would be:
Eagle -> Wattvision -> PVOutput
SolarEdge Inverter -> SolarEdge Portal -> PVOutput
Let PVOutput do the math to figure out consumption.
I checked each device and connection; it appears the Eagle is talking to the cloud and I can monitor it from the Rainforestcloud.com portal. It appears that the link from Eagle to Wattvision is no longer working, and I tried reconfiguring it as a new device, but Wattvision still doesn't receive any data. The config on the Eagle side to point data to Wattivision is dead simple, there's nothing else I can configure or screw up.
In the last few years, it appears that PVOutput can take data straight from the Eagle via the portal:
Eagle -> Rainforestcloud.com -> PVOutput
I tried configuring that in PVOutput, bypassing Wattvision. Oddly, it works fine at five minute intervals overnight when there is no solar production. But as soon as the Enphase starts reporting in the morning, then PVOUtput only shows a random consumption value every 20-30 minutes, with many of the five-minute intervals skipped.Leave a comment:
-
I've been using my Eagle 200 for about 5 years now with my SDG&E smart meters. I am thinking the OP was talking about a newer revision to the Eagle 200, not a new device.Leave a comment:
-
Mike, I approved his posts since they didn't seem spammy, I think he still needs to be approved by the admin to see the jpegs.
Last edited by sdold; 05-10-2018, 02:04 PM.Leave a comment:
-
Thanks Mike, but it looks like I might have been wrong as I still can't access any of the jpg's for information. When I click on the jpg's link the web page I'm directed to just draws a blank. I also noticed that some of those jpg's list as only being once - that couldn't be right could it?Leave a comment:
-
If someone uses OpenHAB, I created a local binding for this device. More details here:
I’ve created a binding for the Rainforest Eagle 200 utility meter gateway device (https://rainforestautomation.com/rfa-z114-eagle-200/). The binding works locally and doesn’t require cloud accounts at rainforest etc. The binding should be able to find the device on your local network via mDNS/Bonjour, and also find the devices cloudID that way. When discovered, you’ll need to add the install code (IN) from the back of your device to the configuration. Once the brigde/gateway binding is online,...
Cheers,
-ThLeave a comment:
-
Leave a comment:
-
Hi guys, I'm new to the forum. Registered a couple of days ago and hoping to get some insight into my current plight with an Eagle-200.
Recently got myself a Eagle 200 and have had nothing but issues with it. Out of the box it wouldn't connect with my meter and had to get RFA to Admin to reset it. After the admin reset it starts reading meter but doesn't display any values in the home screen for Average, Always On & Peak; it just continually displays "loading". The graph operates but is somewhat boring and relatively futile.
A request to the Admin team to direct route my Eagle-200 to PVOutput has got a single solitary data point with zero value uploaded to PVOutput which updates every 5 minutes with no additional data.
I was hoping to see what others have done to get their RFA Eagle-200 running right but I cannot gain access to any of the .jpg's, until I imagine my account is released from the moderation queue.
Sits and waits!Leave a comment:
-
In short, local API works pretty well. If you're interested to get stuff from it locally, and know your way around Node-Red, here is a flow to get started using the local API:
(substitute the stuff inside <..> )
gist<dot>github<dot>com<slash>HentschelT<slash>36c <no space here>870ffca2649b5ae8f80f94bb5a5a5
Edit: Missed one thing in that flow: The "wifi status" and "device list" triggers will work out of the box. For the rest you'll have to get the "HardwareAdress" for your device by drilling down into the "device list" response to find DeviceList->Device->HardwareAddress. Copy that number that starts with "0x.." (w/o the quotes) and paste that into the "HardwareAdress" tag in the other nodes that are present....
Cheers,
-ThLast edited by captndelta; 12-08-2017, 07:08 AM.Leave a comment:
-
In the meantime, I got it to locally pump energy consumption happily into my openhab installation. For the REST API, some of my experimentation shows that it doesn't like polling more than once every 10 seconds, which is good enough for me.
If you know your way around Node-Red, here's a flow on to get started with polling local data:
Cheers,
-ThLeave a comment:
-
Mine is working great nowLeave a comment:
Leave a comment: