Archived Forum

Hello Kevin, we're having a bit of an discussion about this, whether emonhub.conf should ship pre-configured or not. You're right that many of the id's are now used up and reflect firmware changes on the emonth and emontx. I see the issue where the emonpiupdate will keep adding the nodes even if you already have it defined.

This is being done by the search here: https://github.com/openenergymonitor/emonpi/blob/master/emoncmsupdate#L57 I will look into how this can be changed to check for nodeid's so that it only appends a node if no node is already described on [[8]] etc

I've changed the implementation of this to search for nodeid's rather than the firmware name and add nodes individually. Running update now should not overwrite any existing nodes on the same nodeid. It will only add node decoders for nodes not described - which could in itself still be a problem if the nodes are not being described at all?

Thanks for the replies Trystan, is an entry such as

[[4]]
    nodename = Office_Temp

sufficient to prevent overwriting or does it need extra information in there? I'm guessing you changed something in the last few days to prevent a full overwrite?

Yes that will be sufficient

Thanks, I did an update and nothing got overwritten