It works for me.
At 17:44, I restarted the emonTH. OOPS - there’s a zero value, though not surprising as it’s the default sketch - well almost, it’s actually using the RFM69 Native format because that’s what my emonPi is running now.
Then I changed the sketch to move the factory test to Group 1, and restarted it a couple more times: first at 17:54, then I changed my emonGLCD debugger sketch to Group 1 and restarted the emonTH again, at 18:01. The factory test appeared on the emonGLCD, but the TH missed both factory tests.
I call that successful.
And it’s now tested with the RFM69 ‘Classic’ JeeLib format, and here it is:
EmonTH_V2-(V3.2.5).zip (7.8 KB)
I’ve called it V3.2.5 and the changes are;
- Factory Test is now transmitted on Group 1,
- Missing declaration of showString( ) has been added.
- The config file name is now prefixed with the parent name.
If you’d like to load it on your errant emonTH(s) (provided it’s/they’re a V2 - other versions available to order ), I think this will cure your problem.
And to go with it, the “default” sketch for the emonTx V3.4, which I’ve called V2.1
EmonTxV3CM-(V2.1).zip (12.7 KB)
The changes are:
- Factory Test is now transmitted on Group 1,
- The config file name is now prefixed with the parent name.