Ok that is the firmware version, can you confirm if emoncms has updated?
The firmware update does try to run, looking at this part or the last log entry
Start emonPi Atmega328 firmware update:
=================================
EmonPi update started
=================================
EUID: 1000
Requirement already up-to-date: paho-mqtt in /usr/local/lib/python2.7/dist-packages
Stopping OpenEnergyMonitor emonHub: emonhub has been stopped ok.
Start ATmega328 serial upload using avrdude with latest.hex
Discrete Sampling
avrdude -c arduino -p ATMEGA328P -P /dev/ttyAMA0 -b 115200 -U flash:w:/home/pi/emonpi/firmware/compiled/latest.hex
avrdude-original: Using autoreset DTR on GPIO Pin 7
Starting OpenEnergyMonitor emonHub: emonhub has been started ok.
there is no sign of a problem (or confirmation of a successful upload for that matter).
Can you check for a file called /var/log/service-runner.log for any errors. There is a quirk in the way the emonPi update log works and some errors get posted to this less used logfile. If you have rebooted it will be lost so you may need to retry the “update emonPi” button from emoncms again.
[edit - for more info on this see the Errors not reported in emonpiupdate.log file thread]