I have two emonPi’s in two separate locations which are paired with an emonTX. Both emonPi’s are successfully reading the corresponding data from the emonTX. I set the first emonPi to log the data remotely which works fine. However when I configured the second location to post the readings remotely I could only see the energy reading from the emonPi and not the readings from the emonTX. I did change the baseID to a different number but it made no difference.
they seem to work fine if only one location is sending the data so I know the connection is fine, but it wont work if they are sending the data at the same time (no data is received from the second emonTX.
Just wondering if anyone can point me in the right direction?
I’m not sure that I understand your set-up. Do you have 2 emonTx’s, each working to an emonPi? Where is “remotely” that the data is being logged?
I suspect you don’t have enough NodeIDs. Each node (each emonTx and each emonPi) must have an unique nodeID. If the two emonTx’s have the same nodeID, then each will overwrite the other, similarly the emonPi’s.
Thanks for responding. Yeah I have 2 emonTx’s each sending readings to their own dedicated emonPi at two separate locations. If I log onto the emonPI’s using the local ip addess I can seen the energy readings from the emonTx. I am sending the data from the feed to emncms.
Using the first emonPI I can seen the energy readings from the emonTx on the remote sever and all works fine. However if I configure the second location (emonPI) to log data to emoncms (using the same account) I only set the feeds from the emonPI and not he data coming from the emonTx. Its not sending the data through to emoncms from the emonTx, however is I set up a second server and log the separately I can see the feeds from the emonTx.
All nodes posting to a single Emomcs account need to have a a unique node ID.
If you want to post to a single Emoncms account, you will need to change the node ID on two of the emonTx units. If your emonTx are running firmware V2.6+ the nodeID can be changed via serial config. You will require a USB to UART adapter (available from the shop)
I recommend changing the node ID’s of 2/4 of the emonTx’s to 9 and 10.
The current emonTx node ID’s should be 7 and 8, you should leave the other 2/4 emonTx to have node ID 7 & 8.
If your emonTx has firmware older than V2.6 then you will either need to upgrade the firmware and or update the node ID in the firmware then upload. See:
So in that case, @Clamps251, you need to have 6 different NodeIDs in total. It seems as if you didn’t realise that each emonTx’s NodeID propagates through the emonPi to emoncms.org, and the emonPi’s own data also carries its NodeID quite separately.
I’d suggest that, to keep as close as possible to the default numbering of emonhub, you should number your nodes as
emonTx 1 = NodeID 10
emonTx 2 = NodeID 9
These two feed into emonPi 1 = NodeID 5
emonTx 3 = NodeID 8
emonTx 4 = NodeID 7
These two feed into emonPi 2 = NodeID 6
The NodeID for the emonPi is called “baseid” in emonhub.conf
The NodeID for the emonTx is called NodeID in the sketch.
Note that the NodeIDs preloaded into emonhub.conf are our defaults, but they are only suggestions - you are free to allocate any number in the range 1 - 30 inclusive. The overriding rules are that every unit (node) has an unique ID, and each node is defined only once in emonhub.conf.
Ah sorry, I got confused. I thought you had 4x emonTx in total. If you only have 2 x emonTx that makes things much easier. You can just set node ID via emonTx on-board DIP switch 1: EmonTx V3.4 - OpenEnergyMonitor Wiki
The emonPi node ID is set in emonhub.conf this can be done via the local Emoncms web interface Setup > emonhub > edit config` e.g: