From a configuration standpoint, the most common mistake users make is to forget to change the ECM-1240/GEM settings to use HTTP-style URL’s instead of their native/default Binary format.
That said, I stopped recommending it to people because Vera is far too resource limited, and it’s all too easy for users to make their systems unstable with a small # of active plugins. This plugin is very active when using a GEM since, by default, those units are configured to sample every 5 seconds (can be reconfigured)
Thanks, I have it installed and I am pointing it at my GEM which is configured to output Primary (Com1) Packet Format on port 8000.
My GEM is configured to send packets every 15 seconds. I configured the plug-in to get all 32 channels. Lets see what that does to perf on the vera edge! Guess I should login and do a top?
On the GEM I set the packet format to 3 (HTTP Get) and set the packet format fields to the my1240 paramerters. Done that and I am now getting data.
If anyone is interested I will write up a complete how to. But beware UI7 is still flaky as s**t (way better than when I got the vera3 that went back to amazon months ago because I never got it working) - I have only had this Vera Edge up and running for the last couple of hours, seems way better, but the code for entering variables is shoddy and doesn’t work properly.
It’s in a GET style. The plugin works out the format differences between the GEM and ECM-1240 GET style requests, but that format isn’t the default option for either the GEM or the ECM
Sure but with the fields completely empty in the GEM UI it didn’t work at all, I added the entries for my1240 and then it worked, I wonder if you plug-in doesn’t like those fields being null in the packet?