Just so happens I installed the plug-in on a different Vera yesterday, using the 0.4 files from this thread, and it appears to work great - have not seen the nans.
I will check my Eagle firmware to confirm the version #…
I’ve had a couple instances in the last 2 months where this plugin wil cause constant lip restarts. If I clear the IP address out, the restarts go away. When this happens, the eagle seems to have lost connectivity to its cloud service (not sure which is the cause and which is the effect), but after rebooting and re entering the IP address in the plugin all is happy again.
Not sure if anyone else has seen this, or what is causing the plugin to restart constantly. Even if the eagle loses its cloud conncectivity, the plugin shouldn’t need to fail in this way.
X
Noob-alert:
Where does one obtain files for this plug-in? It’s not listed on http://wiki.micasaverde.com/index.php/Luup_plugins_and_Luup_code#Plugins_and_code ?
[quote=“IlDavo, post:83, topic:175309”]Noob-alert:
Where does one obtain files for this plug-in? It’s not listed on http://wiki.micasaverde.com/index.php/Luup_plugins_and_Luup_code#Plugins_and_code ?[/quote]
See attachments on first post
I filed a ticket with Rainforest to get upgraded to latest firmware, since I am on 1.4.23 (5099). Will see how it impacts the plug-in, but I think others of you are already in firmware 2+…
[url=https://rainforestautomation.com/wp-content/uploads/2015/11/EAGLE%20Upgrade%20Instructions.pdf]https://rainforestautomation.com/wp-content/uploads/2015/11/EAGLE%20Upgrade%20Instructions.pdf[/url]
I’m curious to know what you see as the version on the internal port. As far as I can tell they want you to gather the information from their cloud service (which is indeed possible, but why not collect it locally?).
I put notes in my ticket about this plug-in and using the 5002 port. Will see how they reply…
Sent from my SM-G900V using Tapatalk
Love this plugin! Is there any way to reset the DeliveredKWH, ReceivedKWH and NetKWH variables back to zero? I’d like to create a scene that did this monthly so that I can see the monthly totals.
Has anyone figured out to pull in the Price/kWh from the Eagle? This would be very useful if Vera could act on time of use rate changes.
Yes, you can pull the price data. I can’t test it as my utility doesn’t populate this, but the way you can do it is to add a routine that uses “get_price” and parses the return XML in addition to the existing “get_usage_data”.
Note that this plugin is using port 5002 which appears to be deprecated. I get bogus data every once in a while from it. Eventually I’d like to try to switch it over to using the standard port 80 server. I don’t know if the issues I see are related to port 80 or not. Also, Rainforest seems to expect that you will use their cloud service to get the data. There is a python program on github to do just that.
[quote=“jamac, post:88, topic:175309”]Love this plugin! Is there any way to reset the DeliveredKWH, ReceivedKWH and NetKWH variables back to zero? I’d like to create a scene that did this monthly so that I can see the monthly totals.[/quote]@jamac, Delivered and Received are pulled directly from the meter and Net is calculated from them. There is no way to “reset” them. But I suppose we could add some new variables to serve as a base. DeliveredBase and ReceivedBase. The “reset” button that you describe would update the bases. Then you could calculate the new delta as DeliveredKWH - DeliveredBase. What do you think of that?
Also, the Eagle is able to show the monthly totals in its local web server (I think). You might try opening the local web page on it using Chrome with F12 to see the debug window. Navigate to the page with the monthly totals. Then see if there is a way to pull the monthly data directly from the server. This might be easier than the above.
[quote=“jswim788, post:91, topic:175309”][quote=“jamac, post:88, topic:175309”]Love this plugin! Is there any way to reset the DeliveredKWH, ReceivedKWH and NetKWH variables back to zero? I’d like to create a scene that did this monthly so that I can see the monthly totals.[/quote]@jamac, Delivered and Received are pulled directly from the meter and Net is calculated from them. There is no way to “reset” them. But I suppose we could add some new variables to serve as a base. DeliveredBase and ReceivedBase. The “reset” button that you describe would update the bases. Then you could calculate the new delta as DeliveredKWH - DeliveredBase. What do you think of that?
Also, the Eagle is able to show the monthly totals in its local web server (I think). You might try opening the local web page on it using Chrome with F12 to see the debug window. Navigate to the page with the monthly totals. Then see if there is a way to pull the monthly data directly from the server. This might be easier than the above.[/quote]
Reset-able variables would be awesome. This would mirror the functionality offered by the Aeon Labs Home Energy Meter (HEM) and Smart Switches, both of which allow the user to reset the internal kWh counter. You can then create a scene to do that daily, weekly or monthly according to your preference.
I’ve had a look at the Rainforest Eagle’s local and cloud portals and the ‘consumption’ view for a year shows the monthly NET totals. I’m not sure how this data could be extracted from the server… you have to scrape it somehow right? Anyway, having reset-able variables for delivered and received kWh would be a much nicer solution. Happy to roadtest a beta for you! 
I’ve attached an updated implementation file. This uses port 80 to access the Eagle data instead of 5002. It gets a JSON response instead of XML. I mainly did this to see if I would stop getting bogus power data. Unfortunately that did not happen, but it is easier to detect with the JSON which will return “nan” instead of giving a bogus timestamp. The other advantages are that it is easier to parse the JSON, you can get access to anything that the internal web server displays, the values are formatted a little better, and you could more easily point this to the Rainforest cloud server if you wanted. Otherwise there is not a lot of advantage of this over the original.
I did add two features:
- the ResetKWH action now works. This will save a base value for delivered and received and give the KWH as a delta from the saved values.
- Price is now reported. I have no way to test this as my utility does not populate it.
This loses automatic MacID detection. I will try to look into this.
Installation:
You can update your existing device with the attached xml. Upload the xml file, change the device to point to this file, and reload.
Or you can create a new device with robertmm’s original files with the attached replacing the I_SmartMeterHAN1.xml.
You must set the IP.
Since there is no autodetect of the MacID, you MUST set it manually if not already set. See the attached picture of the Eagle - get the MacID from the bottom. The format must have “0x” in front of it.
If your Eagle has security turned on (optional, you can turn it off in the settings in the Eagle GUI, but I believe the default is on), then you must get the CloudId and the DeviceIN which is also on the bottom of the device.
Sample lua to set them below. Replace the ‘46’ with the Vera ID for this device, and replace the values with the ones from the bottom of your Eagle.
luup.variable_set("urn:smartmeter-han:serviceId:SmartMeterHAN1", "DeviceMACID", "0xabababababababab", 46)
luup.variable_set("urn:smartmeter-han:serviceId:SmartMeterHAN1", "DeviceIN", "1eabababadddddddd", 46)
luup.variable_set("urn:smartmeter-han:serviceId:SmartMeterHAN1", "CloudId", "000eee", 46)
Or, after the initial reload, set these 3 variables in the advanced tab appropriately.
Then reload the Vera.
Should you have any trouble, try the following curl test line on a unix box (must be a Windows version of curl too?). Replace the IP with your Eagle IP, 6 digits before the : are the Cloud ID, 16 digits after the : are the IN, and the MacID is the 0xXXXXXXXXXXX delimited by . This should return the status of your Eagle in JSON format. If you don’t get the status back, the plugin won’t work.
curl -d '<LocalCommand><Name>get_setting_data</Name><MacId>0xXXXXXXXX</MacID></LocalCommand>' http://XXXXXX:XXXXXXXXXXXX@192.168.1.201/cgi-bin/cgi_managerThanks to robertmm for the original code - this is a great plugin.
Also, I’m keeping the code in github here: GitHub - jswim788/rainforest-eagle-vera: Plugin for Vera for the Rainforest Eagle for Smart Meters
This looks great.
A dumb question - presumably I need to update the local variables in the xml implementation file before uploading it, eg:
local HAN_IP = “123.456.7.89”
local HAN_MACID = “0xabababababab”
local HAN_IN = “12341234a123a123”
local HAN_CLOUDID = “000123”
You don’t need to change the xml. Case 1 is if you are modifying an existing energy meter device and case 2 is for creating a new energy meter device.
Case 1: you already have the IP and likely the MACID. If security is off, then you can likely just change the implementation file and reload and it should get the new file and start working. If you do have security on, then you’ll want to add those 2 variables to the device. After you first install and reload the device, you should see DeviceIN and CloudId as blank in the advanced tab. Fill these in with the appropriate values and reload.
Case 2: create the new device with robertmm’s original files except the I_SmartMeterHAN1.xml replaced with this new one, then go into the tabs and set the IP, then set the variables in the advanced tab. Reload the Vera to get it to start up with the new variables set.
See http://forum.micasaverde.com/index.php/topic,14767.msg325432.html#msg325432 for the latest files. Also, I have them in github here: GitHub - jswim788/rainforest-eagle-vera: Plugin for Vera for the Rainforest Eagle for Smart Meters
I had Rainforest update my firmware - I had to remind them twice. Now it is a mess. Disconnected from meter. No advanced settings to disable credentials.
I updated my ticket with my frustrations…
[quote=“wilme2, post:96, topic:175309”]I had Rainforest update my firmware - I had to remind them twice. Now it is a mess. Disconnected from meter. No advanced settings to disable credentials.
I updated my ticket with my frustrations…[/quote]
I got my Eagle re-paired with my meter. Leaving it on the older plug-in code as it started working - WITHOUT any security updates. I didn’t add in the username/passowrd to the plug-in nor did I disable the security on the Eagle. Meaning it looks to me like port 5002 isn’t requiring a password. When I try to connect via browser it says “Connection Dropped”, but I get data from the plug-in…
What firmware do you have now? I’m getting the impression that they started using port 5002, then shifted over to the web browser interface on port 80 but didn’t remove the port 5002 access. Also, it doesn’t appear they’ve made any firmware changes recently, so maybe it is stuck as is. 2.3.4 was released in Dec 2015.
HW 3.2.3
FW 2.3.4.8466
I just can’t get this to work.
I’ve uploaded the new implementation file as I_SmartMeterHAN1.xml (ie, replacing the existing implementation file) but I get the following error whenever I restart the Luup engine: “Rainforest Eagle[18] : Startup Lua Failed”.
If i reload the old implementation file and restart the luup engine everything goes back to that way it was.
Any tips?