Eagle push service still working for anyone?

Problems
#1

I’ve been using a Rainforest Eagle (Zigbee device that’s allowed to read my utility smartmeter) to send my meter’s net usage readings to PVoutput for 10+ years. However, recent changes (discussed in a few other threads) have me challenged to get it to continue. Is anyone still using an Eagle with pvoutput?

  1. Relaying the Rainforest cloud data through Wattvision worked seamlessly for 10 years, but Wattvision is no longer offering their service without an expensive paid subscription.
  2. The pvoutput autouploader (pull service?) for Eagle is retired, and trying to configure it (still in the config menu) doesn’t save.
  3. The Eagle push option is still documented by pvoutput, but Rainforest is moving folks from their cloud to a new Rainge mobile app?

For the 3rd one, some folks say they no longer had the option to configure the push in their Rainforest cloud account, others said they had to call Rainforest and convince them to add the config menu. However, the last threads here were a few months ago - is it still working for some?

I do still have the Cloud tab in my Rainforest cloud account, and can configure the push service. However, I’m not seeing any data showing in pvoutput. Is there anything I need to configure on the pvoutput side?

Here’s what I’m seeing in the Rainforest cloud “Cloud” config tab:
-if I just select the pre-configured “pvoutput” in Rainforest’s push options (and provide Rainforest with my pvoutput SID and API key), it saves but status returns as 401 error.
-if I select the “custom” push option, and enter the URL and other info for pvoutput’s push, it saves but status returns as “Initializing” (some have said this works for them) instead of OK, forever.
-if I play “custom” say using XML:PROCESSED instead of XML:SIMPLE, still get the same status.

My Eagle is still pushing its data to Rainforest cloud, that’s enabled internally and I can view the realtime and historic data in their portal. So I think it is trying to push data to pvoutput via these configs.

Is there any way within pvoutput to see if my pvoutput SID is receiving any push data, if nothing is showing up in the graphs?

Eagle3_push_configuration
Eagle3_push_configuration1440×863 141 KB

#2

The PVoutput push is working with my Eagle 200. However, I remember when I was using the Cloud API setup on the Rainforest menu I used to have the status stuck on “Initializing”. I had to contact Rainforest support who remotely set the JSON query for my system as the Cloud interface was not working.

I am not aware of any feature to test the Push data coming to PVOutput.

#3

@wwu123 This is EXACTLY the same issue I had a few months ago. Complete inability to set the cloud account up to PVO using PUSH. Always initializing. I had to get RA remotely configure the device after banging on the support ticket for over a week before they got back to me.

Had to have what @samw01 did to regain export of my data showing up at PVO.

#4

Awesome, thanks @samw01 and @kenyers95963, seems like I’m on the right track with the configs that are Initializing. Will reach out to Rainforest support!

#5

The 401 response is an unauthorization error, so either the sid or key is missing from the request.

Add your PVOutput API key to the end of the URL

e.g. eaglepost.jsp?sid=26632&key=your_api_key

#6

Thanks, yes, I suspected the 401 wasn’t authenticating or authorizing properly, that was Rainforest cloud’s preconfigured pvoutput option from the pulldown. I did use the Custom parameters instead in the pulldown, and appended the SID and key exactly as you described, which led to a Initializing status, better but still no data.

Finally just got a support response back from Rainforest, they said their (Cloud) config page is not “loading the key properly from the configuration page”, so I e-mailed Rainfrest support the SID and api key as they requested. So fingers crossed they will configure the push themselves on their backend, and get it working soon…

EDIT: OK, finally real progress, Rainforest support configured the push and seeing 200 status, and I’m seeing some consumption data reflecting in pvoutput. However, the timestamp is 7 hours ahead (I’m in the US Pacific time zone where it’s currently 12:30pm, but pvoutput is showing consumption data for 7:30pm).

I found another thread here suggesting the timezone parameter must also be appended, and passing that along to Rainforest support:

eaglepost.jsp?sid=[system_id]&key=[api_key]&tz=US/Pacific

#7

Yay, problem resolved! They updated the push with the tz timezone parameter, and I’ve been monitoring for half a day, and the Rainforest Eagle consumption data seems to be working again.

So to bookmark the solution for others in the future - the Eagle push config is as noted in my previous post. However, even if one still has access to the Cloud tab in the Rainforest cloud portal, the UI is not correctly letting end users enter and configure the push parameters as of now.

Before Rainforest support manually configured it for me on their side, they did say they are working on some updates to the portal, that implied the UI might be fixed after the update. But given some folks have report here losing access to the Cloud tab, and other being pushed along to their new Rainge mobile app, I might not hold out hope on the UI being fixed.