I probe my water meter using a pulse count on my emonBase, it emits frames with node number 15, which show up correctly on its local emoncms.
This emonBase is located in my basement and forwards all its data to my emonPi, which I consider my master in my system. The data shows up correctly. Both emonBase and emonPi have the node configured in the EmonHub configuration.
The master emonPi also forwards all data to www.emoncms.org. However, node 15 is missing. What am I doing wrong?
How is the data passed between the 2 Pi’s exactly?
If you are running an emonSD on the basement Pi and using emonHub to post to the emonPi emoncms instance directly, then the emonhub instance on the emonPi is not being included and there fore unable to send to emoncms.org.
In this instance you could set up the basement emonHub to post to both the emonPi and emoncms.org by using a second emoncms http interfacer in the emonhub.conf eg [[emoncmsorg2]] or change the name of the first one to [[myemonpi]] etc.
node 23, irregularly updated (I would think once every 2 hours or so, but I have no formal data or logging of that yet)
This suggests that the master emonPi also forwards some of its received data (emonTH of emonBase). Is this true?
In an ideal world, I would prefer to have my emonPi be the only node communicating with emoncms.org. This would result in less load for emoncms.org, and has the advantage that I only need to provide internet disconnected network access to the basement.
yes the master emonPi is occasionally getting a packet from node 23, this can be avoided by using seperate group ids for each network if you desire or need to, there is a slim chance that any time difference on the 2 Pi’s or a difference in processing time may result in double entries.
I agree with you entirely, unfortunately the trend seems to be to have every device connected to the outside world independently.I too would like to see a link between local emonHub’s but thre is not currently a way to do it.
If you are up for some developing, it might not be too difficult (famous last words) to make the SocketInterfacer in emonHub 2 way and send data from the emonbase to the emonPi via a socket. Ideally this would be easy to accomplish via MQTT but unfortunately in it’s current implementation it isn’t.
Thanks @pb66, this has been helpful understanding the software Emon software stack. Until now I only have focussed on the code the RFM2Pi and EmonTH, time to learn about the rest of the stack and how it fits in the IoT story.
This seems doable and in fact not a lot of work (in my day job I am a freelance software engineer). However, unfortunately besides some small scripts years ago, I haven’t done anything serious in Python yet. I will keep your idea in mind and see if I can materialize it.