Do you know your Eagle is paired to your electric meter? If you log directly into the Eagle do you get the current energy readings?
Thanks for the quick reply, the eagle has been connected to my meter for about 6 months, I also cloud connect to wattvision and have had very solid results and connections (currently the cloud is reading what my meter is showing) I do have solar on my system as well, not sure how that plays.
One thing I was thinking is did I possibly use the wrong IP Address? I used the one from logging in to the rainforest website and clicking on the gateway then under settings → internet → IP address and Mac Address.
I can’t log into my Eagle from where I am now, but you will want to assign a static IP address. Either in the Eagle, or in your DHCP server (likely your router).
You will want the local IP of the Eagle. Likely in the range of 192.168.x.x…
[quote=“wilme2, post:63, topic:175309”]I can’t log into my Eagle from where I am now, but you will want to assign a static IP address. Either in the Eagle, or in your DHCP server (likely your router).
You will want the local IP of the Eagle. Likely in the range of 192.168.x.x…[/quote]
I tried looking for it on my network this am and didn’t see it on the router, I might have to move it to a different switch to see it pop up so I can assign it a reservation. If anyone has ideas why it might not be easy to see I am all ears 
Is it possible it has a different local mac address?
Isn’t there a URL on the underside of the device for local web access ?
[quote=“norcalhkr, post:64, topic:175309”][quote=“wilme2, post:63, topic:175309”]I can’t log into my Eagle from where I am now, but you will want to assign a static IP address. Either in the Eagle, or in your DHCP server (likely your router).
You will want the local IP of the Eagle. Likely in the range of 192.168.x.x…[/quote]
I tried looking for it on my network this am and didn’t see it on the router, I might have to move it to a different switch to see it pop up so I can assign it a reservation. If anyone has ideas why it might not be easy to see I am all ears
Is it possible it has a different local mac address?[/quote]
On my router I can see it in the DHCP clients table. Has “eagle” somewhere in the device name, I think…
I rarely have luck with local web access URLs, but definitely try that too-
[quote=“wilme2, post:66, topic:175309”]On my router I can see it in the DHCP clients table. Has “eagle” somewhere in the device name, I think…
I rarely have luck with local web access URLs, but definitely try that too-[/quote]
No luck on the web access URL (sure enough it was on the bottom) and I did finally track it down via the vera plus when trying to add a new IP camera, go figure… In my DHCP router is was a very obscure name and nothing to do with the eagle.
So I put the right IP address in and I am still getting the cant find device error. Any other ideas?
Here is the error given by the LUUP code
SmartMeterHAN1 : HAN device not found. Verify connection and IP address.
I am able to access the device via the cloud and through wattvision API
But until you can access via the local IP address, I think that needs to be your focus.
Sent from my SM-G900V using Tapatalk
[quote=“wilme2, post:69, topic:175309”]But until you can access via the local IP address, I think that needs to be your focus.
Sent from my SM-G900V using Tapatalk[/quote]
We have lift-off, it helps when you finally get the right IP address. Ended up resetting the device and watching for the IP to disappear and there you go, identified the current IP. (Reserved in router as well)
Thanks for you help!
Also can you help with the settings for the update pulse?
Pulse is seconds between readings, I think. Mine is set to 60…
Sent from my SM-G900V using Tapatalk
[quote=“wilme2, post:71, topic:175309”]Pulse is seconds between readings, I think. Mine is set to 60…
Sent from my SM-G900V using Tapatalk[/quote]
Thanks I guessed that is what it would do but thought I should be a bit more sure, now to figure out if we want to do anything with it…
This plugin works fairly well for me, but every hour or two I get ‘nan’ for most of the values. This isn’t too much of a problem, but it seems to mess up the graphing within the AltUI. So I became curious as to what is going on. So far, I see that most of the values coming back from the parsexml are 0’s as seen by the luup.log calls that I uncommented and added. Interestingly, ‘xdelivered’ is not 0 in this case, but the xtimestamp is. I’m not sure, but it seems that the code is trying to block bad results by using the “if (xdemand and xtimestamp and xmult and xdiv) then”, but that still passes in this case since the values are not nil. As a short term fix, I’m thinking of checking to see if the xtimestamp is 0 and returning with an error if it is.
Has anyone else seen this? Any suggestions for further debug? I’m thinking of uncommenting this line:
– luup.log("Got XML: " … xml, 1)
I’m assuming that will print out the xml that came back.
Are you using the latest code? Nan was previously resolved, I thought…
Sent from my SM-G900V using Tapatalk
I’m using the code that is attached to the first post in this thread. Is there anything newer somewhere?
No the 0.4 version is current AFAIK. Back on this post (http://forum.micasaverde.com/index.php/topic,14767.msg160260.html#msg160260), I had the “nan” issue, but either I fixed it somehow and didn’t post a follow-up, or I might still have the problem and not know it…
I thought it was related to Eagle firmware and one of the plug-in revisions (0.3?) fixed it…
I realized my Eagle firmware is quite old. I’m having it updated. Hopefully that will fix the issue. In the meantime I put some checks in for zero values and now I don’t get any ‘nan’ data recorded.
I put in some triggers to see if I still have the Nan issue, and they have not alerted. I think the Eagle firmware is the issue…
Sent from my SM-G900V using Tapatalk
Rainforest said they updated my unit, yet I still see the zeros. But now that I look at it, I’m not sure they really updated:
1.4.48 (6952)
3.2.3
I think that’s old. Need to check again with them. Here’s what I see it goes bad:
0xd8d5b90000000ea2 0x0013500200a58e59 0x00000000 0x000000 0x00000000 0x00000000 0x00 0x00 NWeird: the 5002 port and the XML logged shows the old firmware version. But if I use the web interface to the gateway, it does indeed show the new firmware. I’m guessing that Rainforest deprecated the 5002 port and isn’t updating it anymore. They want you to use their cloud service which has a documented interface. Nevertheless port 5002 works fine for me as long as I filter out the occasional bogus value, so I’ll probably continue with that for now.