Getting error 401 from eagle200

Push Services Eagle
#1

i’m a donator and my status is active. i just got a notification that my system was idle - the sun is down and so this means that there is no consumption data being uploaded. i went into my eagle config and for some reason the cloud uploader was completely missing.

when i set it all up again with my sid (42057) and my api key, i’m seeing error 401 in the eagle control panel.

is there some problem with PVO right now? or some problem with my account?

thanks

edit: strangely it looks like my consumption uploads caught up but the eagle is still showing error 401. are there any logs on your end that can shed some light on this?

#2

If this is the Eagle Push interface then a 401 error from PVOutput means either the System Id or API Key is missing and/or incorrect.

Check that the Eagle device is still configured with the sid/key values that match the PVOutput API settings on the account page.

#3

the configuration was missing from the eagle when i looked the first time but even after i set it up again i still got the error. but somehow it is uploading ok now. the eagle is a little janky of course.

1 Like
#4

Great, thanks for the update.

#5

I’m having the same issues with error 401 still. Have reconfigured my account with a new API key and tried connecting to PVO multiple times and still get a Error 401 and no consumption data ever shows up.

I know the system ID and API key is correct since I get a good response from getstatus:
20241202,11:30,12082,NaN,NaN,NaN,NaN,14.0,NaN,276.340,NaN,NaN,NaN,NaN,NaN

How to fix this issue?

#6

I really need some help here. I’ve had no luck for over a week getting data to PVO.

Ever since I lost the Zigbee connection to the Smart Meter from the Rainforest Eagle-200 and had to disconnect from the meter and then repair the devices, I haven’t been able to connect to PVO.

The Eagle-200 is connecting to Rainforest Automation with the data from the device and meter just fine today since I re-paired the devices with the utility.

Everything is working except for the data export via POST.

#7

Took remote configuration by Rainforest Automation Support to restore the exporting of data from my Eagle-200.

Support stated they discovered a bug in the firmware on my device that prevented using the default PVOutput configurator selection.

They had to use the Custom configurator to get it to work correctly. From their email response:

“It seems there might be a bug in the Cloud configurator that you encountered, which prevented your previous attempts from succeeding. We are aware of this potential issue and are investigating it to ensure it doesn’t affect other users. Unfortunately, we do not have an estimated time for this fix yet.”

1 Like