Select your newly added provider and click Set Cloud.
Notes
No Eagle lockups! The Eagle does not like being polled for data and will lock up if you poll too frequently. The uploader API appears to be a better, more stable option.
Tested with the Eagle 100 but should work for Eagle 200.
If using an Eagle 200 select XML Raw as the format.
Both your Hubitat and your Eagle need a static IP address.
Looks like I celebrated too soon. Seems that after a few minutes, it reports 0 W and the Eagle switches back to Bidgely. It won't let me delete it either. I got this Eagle device through my utility company and it's probably locked down. Nothing wrong with your driver -- it works superbly!
Bummer, the driver doesn't handle the http request directly, so it's likely that there is an issue on the Eagle side or for some reason it can't reach the Hubitat anymore. Do you have static IPs for both devices?
Perhaps you can reach out to Rainforest for support. I haven't heard of an Eagle being locked into a cloud provider, but it also wouldn't be surprising.
On a hunch, I decided to create a rule on my router to block the Eagle from going out to the WAN. I think when it's reaching out to Rainforest, the cloud setting gets periodically set back to Bidgely. It's been about 3 hours now and it's still holding onto the local Hubitat cloud setting. I think I'm all set!
@kleung1 Glad you got it working! I'm curious, do you have an Eagle 200 and can you access your Eagle through portal.rainforestcloud.com? If so, I wonder if you need to add cloud providers through there and not the local web UI.
Or at least I could before I blocked traffic at my router. I should turn it back on to test my theory about the cloud resetting it.
But I also had the same thought as you. I did try to edit the cloud provider from the rainforest.com portal, but it didn't work (doesn't even connect at all like it does locally). And I couldn't delete the default Bidgely cloud entry from there either.
When using the Eagle 200 directly via a web browser you only have access to its WiFi and LAN settings. When using portal.rainforestautomation.com you have the Destination Options of: Lucid, Skycentrics, Stringify, WattVision, Ohmie.co, DERNetSoft, PVOutput, or custom. You have the options of HTTP or HTTPS, it wants the URL Hostname, port and username and password if needed.
I opened up the Eagle back to WAN and verified that I can now reach it again through rainforestcloud.com. I don't see the cloud provider setting reverting, so my original theory is not correct, but I still can't explain why it wasn't sticking before and now it is.
These Eagle devices have always been finicky. Ages ago when I was still on ST, my first driver implemented the uploader API, but my Eagle would throw an error every time I tried to add a new provider, so I abandoned the effort and ended up with my polling code... and now we're back to the uploader API.
This device works great for me, but I'm curious how people are displaying it on the dashboards? I'm using the "Power" template but all it shows is current usage/wattage. Has anybody come up with any creative and useful?
I haven't come with with anything useful yet. Like you, I just have a dashboard tile that displays current power & energy. I already get email alerts from my utility when we're crossing tiers, and I don't have on/off peak hours.
Power usage has been one of those things that I was really interested in at first, but then after about a week or so I stopped looking at it. I already know the AC, stove, and car use the most electricity, but I'm not necessarily going to changes my habits... who wants to sweat?!
Thank you for enabling this integration but the Setup instructions are insufficient (for Hubitat newbs such as myself). For example,
What are the requirements/prerequisites? Does my Eagle need to be on the same subnet as my HE?
Also, when I attempt to 'Add Virtual Device' via the Hubitat UI, I don't know how to "select this driver." There is a Type drop down but Rainforest Eagle isn't listed and when I click on 'User' nothing happens.
