Energy EAGLE Discussion

[automaton]

Nathan,

For some reason, I get the following error when trying to install Energy Eagle on Indigo 5.1.10:

Reloading plugin "Energy EAGLE 0.9.4"
Error plugin "Energy EAGLE 0.9.4" requires a newer version of Indigo Server (try updating Indigo)


I was under the impression that the plug-in ran under Indigo 5 ??

[nsheldon]

I was under the impression that the plug-in ran under Indigo 5 ??

You're right. I did say that. I'll fix that in the next release. However, I do plan on using some Indigo 6-only energy device features (client UI stuff mostly). Also, I don't have Indigo 5 any longer and thus can't test the plugin under that version, so I can only provide limited support under Indigo 5.

If you want to get the plugin working right away, you can do the following:

1. Open the /Library/Application Support/Perceptive Automation/Indigo 5/Plugins folder.
2. Find the Energy EAGLE.indigoPlugin icon and right-click on it. Choose "Show Package Contents".
3. In the new window that appears, open the Contents folder. Open the "Info.plist" file with a text editor like TextEdit.
4. Find the lines near the top that look like

   Code: Select all

   	<key>ServerApiVersion</key>
   	<string>1.4</string>

   and change the "1.4" to "1.2".
5. Save the file and close all the Finder windows.
6. Reload the Energy EAGLE plugin.

That should fix the problem.

[automaton]

Nathan,

Thanks. That gets it to enable.

My device hasn't "registered" yet with my utility, so Energy Eagle throws an error, I'm guessing because the device isn't returning any data from the meter yet:

raceback (most recent call last):
File "plugin.py", line 575, in runConcurrentThread
File "plugin.py", line 1060, in update
<type 'exceptions.ZeroDivisionError'>: float division

Energy EAGLE Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
Received INSTEON "1FL Bobs Office Occupancy Sensor" off (button 1)
Energy EAGLE Error Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
File "plugin.py", line 575, in runConcurrentThread
File "plugin.py", line 1060, in update
<type 'exceptions.ZeroDivisionError'>: float division

Energy EAGLE Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)

You may want to look at this in your next update. I'll be on Indigo 6 by then.

Thanks.

[nsheldon]

Thanks for the report. Yes. An unregistered EAGLE shouldn't cause the plugin to crash, so I'll look into that as well.

[nsheldon]

Version 0.9.5 Posted

Changes from 0.9.4:

• Corrected minimum API version requirement in info.plist. It was incorrectly set to version 1.4 but only version 1.2 is required.
• Fixed a bug that causes a divide by zero error if the EAGLE is not connected to the SmartMeter.
• Changed status gathering interval from 5 seconds to 10 seconds to decrease load on the EAGLE and because meter readings aren't updated more often than every 10 seconds on the EAGLE anyway.

[automaton]

Nathan,

Thanks, it came up while unregistered without the division errors. My gateway registered today, and the plugin is operating.

I did notice that if the gateway is restarted (i.e. power cycled), I get a divisopn error until it has booted:

Energy EAGLE Error Error connecting to "Rainforest Gateway". Error: (61, 'Connection refused')
Energy EAGLE Error Error connecting to "Rainforest Gateway". Error: (61, 'Connection refused')
Energy EAGLE Error Error connecting to "Rainforest Gateway". Error: (61, 'Connection refused')
Energy EAGLE Error Error connecting to "Rainforest Gateway". Error: (61, 'Connection refused')
Energy EAGLE Error Error connecting to "Rainforest Gateway". Error: (61, 'Connection refused')
Received INSTEON "1FL Bobs Office Occupancy Sensor" on (button 1)
Energy EAGLE Error Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
File "plugin.py", line 584, in runConcurrentThread
File "plugin.py", line 1074, in update
<type 'exceptions.ZeroDivisionError'>: float division

Energy EAGLE Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)

Non-critical problem, just FYI.

[nsheldon]

Version 0.9.6 Posted

Changes from 0.9.5:

• Second attempt at fixing the divide by zero error.

[nsheldon]

Thanks, it came up while unregistered without the division errors. My gateway registered today, and the plugin is operating.

I did notice that if the gateway is restarted (i.e. power cycled), I get a divisopn error until it has booted...

Oops. My solution to the divide-by-zero error was flawed (obviously). Thanks for the report. 0.9.6 should fix it though (hopefully).

[richy240]

Can someone recommend a vendor for this device? There's a Bidgely version on Amazon (Prime ) that comes "pre-configured with Bidgely energy management software," but I don't know if this one will work without signing up for Bidgely (http://www.amazon.com/EAGLE-ZigBee-Gate ... f=pd_ybh_1). I would think so and they're just reselling it with their "brand" on it, but you never know...

I want this one since I'd save $15 on shipping versus other vendors (including Rainforest themselves), but only if it works.

[nsheldon]

I didn't buy this version, but I'll bet it works just fine. It may report an error or two if its unable to connect to Bidgely, but should still work for local meter reading stuff. And if not, Amazon's return policy is usually pretty lenient.

[richy240]

I went ahead and bought this one (http://www.amazon.com/Rainforest-EAGLE- ... 00AII248U/) instead from Southwest Energy Smarts via Amazon. They're in Texas (and so am I), so I hope this means I'll get fast shipping even if I did have to pay for it.

The model numbers were different, so maybe there was something special about the Bidgely model. Anyway, I didn't want to take any chances and have to deal with the hassle of returning it. Getting it right the first time is worth $14.

[nsheldon]

Cool! Let us know how it works.

[richy240]

Well, the device seems to be working, but I get this error in the Indigo logs when I try to configure a device (and every 10 seconds thereafter).

Code: Select all

  Energy EAGLE Error              Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
  File "plugin.py", line 587, in runConcurrentThread
  File "plugin.py", line 948, in update
  File "plugin.py", line 1570, in sendCommand
<type 'exceptions.UnicodeDecodeError'>: 'ascii' codec can't decode byte 0x88 in position 2383: ordinal not in range(128)

  Energy EAGLE Error              plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)

[nsheldon]

Well, the device seems to be working, but I get this error in the Indigo logs when I try to configure a device (and every 10 seconds thereafter).

Code: Select all

  Energy EAGLE Error              Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
  File "plugin.py", line 587, in runConcurrentThread
  File "plugin.py", line 948, in update
  File "plugin.py", line 1570, in sendCommand
<type 'exceptions.UnicodeDecodeError'>: 'ascii' codec can't decode byte 0x88 in position 2383: ordinal not in range(128)

  Energy EAGLE Error              plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)

Which version of Indigo are you using? Make sure you have the latest 5.x or 6.x version. The only other time I've seen that kind of error is when it was the result of a device info-to-string interpreter bug present in earlier Indigo 5.x versions, which I believe was fixed a few 5.x releases ago (and doesn't exist in 6.x). If you have the latest 5.x or 6.x version, then I may have been mistaken and I'll need to examine it further.

[richy240]

Which version of Indigo are you using? Make sure you have the latest 5.x or 6.x version. The only other time I've seen that kind of error is when it was the result of a device info-to-string interpreter bug present in earlier Indigo 5.x versions, which I believe was fixed a few 5.x releases ago (and doesn't exist in 6.x). If you have the latest 5.x or 6.x version, then I may have been mistaken and I'll need to examine it further.

I'm running version 6.0.1, thanks for your help.