Okay it seems basic I will see if it works tomorrow - I just plugged in my cloud # and username/password after selecting eagle as opposed to wattsvision. I will let you guys know tomorrow how it goes. Thanks
Yeah, I just switched mine, no reason to use Wattvision anymore. Here are the before and after screenshots on the older eagle, I'm not sure if it looks different on the Eagle-200. (Note that by no longer using Wattvision, the PVOutput settings I showed above have changed. SolarEdge settings move from the secondary device to the primary device, and no secondary device needs to be entered) Cloud1.JPG Cloud2.JPG
Okay it seems basic I will see if it works tomorrow - I just plugged in my cloud # and username/password after selecting eagle as opposed to wattsvision. I will let you guys know tomorrow how it goes. Thanks
The UI on the new device leaves a lot to be desired. It has almost no user selectable options whatsoever. Support is able to do some stuff on their end.. (they were able to set my device up for wattvision).
Yeah, I just switched mine, no reason to use Wattvision anymore. Here are the before and after screenshots on the older eagle, I'm not sure if it looks different on the Eagle-200. (Note that by no longer using Wattvision, the PVOutput settings I showed above have changed. SolarEdge settings move from the secondary device to the primary device, and no secondary device needs to be entered) Cloud1.JPG Cloud2.JPG
Yea, all that interesting stuff appears to be gone from the Eagle 200, it's a pretty crippled device now (as far as the user interface is concerned). I did a quick port scan, ports 22 (ssh), 53, 80 and 443 are open. Hitting both web ports with a browser, all you can do there is configuring WiFi.
PGE wasn't able to hook the Eagle up to my meter, so it's going back...
The UI on the new device leaves a lot to be desired. It has almost no user selectable options whatsoever. Support is able to do some stuff on their end.. (they were able to set my device up for wattvision).
Is there different UI when you log into the device through the cloud (portal.rainforestautomation.com) vs the local IP address?
Hi here are the pictures of every screen I am able to get but good news I called rainforest and for the moment you have to call them and they have to go in and allow you to get info through wattsvision and directly from the eagle rainforest through pvoutput. They are in the process of developing a process where you can do it yours according to the rep but now I will try logging on directly through my eagle to pvoutput and let you know but I am attaching pictures of what it looks like when I log in through 192.168.7.1/ and I tried to go to other features but the customer service rep at Eagle Rainforest said they are working on developing that so for the moment you just call in and they approve you through and get you all set up and only a wifi turn on and off feature is there for the moment
Although so far it seems like wattsvision was better I have been getting 0's for power used here and there going directly from eagle rainforest directly to pvoutput
Although so far it seems like wattsvision was better I have been getting 0's for power used here and there going directly from eagle rainforest directly to pvoutput
When your generation has significant fluctuations (clouds), the time synchronization of the generation and net consumption data matters. "Power Used" = Power imported (seen from the poco meter) + Power generated (seen from the inverter). If power imported is negative (you are exporting power), but the time is not synced and your inverter says you are not generating as much power as you are exporting, PVOutput will show a zero because it doesn't allow negative numbers for power used.
You can tinker with the "time shift" setting in PVOutput to see if you can smooth some of that out.
I'm not seeing how this is crippled in any way, just different.
Yeah, I found your (first) REST doc right around the same time you did (never found that other "post" doc myself, so thanks for that!), and I'll have to change my opinion now - I'm pretty happy.
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.
Comment