Brultech - Sending GEM data to local emoncms

[mblitz]

I installed emoncms locally.  Is there a way to send GEM data via NodeLink to my local emoncms instead of emoncms.org?

 

thanks,

marty

 

[mblitz]

I got it to work (partially) by adding emoncms.org to the local host line in /etc/hosts.

 

127.0.0.1 localhost

::1 localhost ip6-localhost ip6-loopback

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

 

127.0.1.1 raspberrypi emoncms.org

 

And also moving /var/www/html with /var/www/emoncms.  Note that adding index.php to /var/www/html to redirect to emoncms was not sufficient.

 

pi@raspberrypi:/var/www $ cd /var/www/

pi@raspberrypi:/var/www $ sudo mv html html.old

pi@raspberrypi:/var/www $ sudo mv emoncms html

pi@raspberrypi:/var/www $ sudo service apache2 restart

 

I think adding a emoncms URL to NodeLink would be a better solution.

 

Now NodeLink is sending data to emoncms, but each data push creates a new input.

 

[mblitz]

I think the duplicate inputs could be related to the latest stable emoncms, which not requires a "node" parameter with the PUT request.  See https://openenergymonitor.org/emon/node/6315.  Although that discussion is from 2014.

 

I think this too could be fixed by allowing a emoncms URL, like btmon does:

 

emoncms_url=http://emoncms.org/input/post

 

or for local

 

emoncms_url=http://localhost/emoncms/input/post

[mblitz]

I've verified that NodeLink is not sending a node id, which emoncms interprets as a blank.  This causes emoncms to create a new input for each channel when it receives data.

 

I modified emoncms to check for a blank node id, and default to 0.  That seems to have fixed the problem.

 

I think NodeLink should add a user parameter to select a node id for the GEM.  That way if multiple GEMs are sending data to emoncms, they can all have unique IDs.