I was reading through the firmware change log, as you do, as I am preparing my set-up for some level of calibration. Updating components seemed a good start. I noticed that the default node ID has changed from 10 to 8. My current emonpi is set-up for Node 10 and all the data is forwwarded to a local emoncms install on a linux server.
I was hoping for some advice and/or a step-by-step way of updating the firmware without losing existing data on node ID change and minimising the downtime. Updating the emonhub stuff is only the start from what I can see - the inputs then turn up on another node in emoncms (regardless of name in emonhub?) and then the pain might start.
I ask mainly because I had previously moved a CT from input 4 to 1 as I saw that the 4.5kW limit was going to be breached and the manual intervention required to move the feed steps was tedious to say the least.
As an aside, the web-site still mentioned node ID 10 (https://wiki.openenergymonitor.org/index.php/EmonTx_V3.4#DIP_Switch_Config)
Re: Update firmware on emonTXv3.4 from 1.6 to 2.3 - node ID change
If you need to, you can change the node ID back to 10 (and 9) in the Arduino sketch: https://github.com/openenergymon ... emonTxV3_4_DiscreteSampling.ino#L128
Re: Update firmware on emonTXv3.4 from 1.6 to 2.3 - node ID change
Thanks. I was aware of the code but I was hoping for more consumer/user directed help. While making the code change is great there seems to have been a reason for it and also I don't want to have to make the same change every time the firmware is updated. Having a walk-through and/or the tools to change emonhub/emoncms once wuold help me and I think others.