On Saturday, February 24, 2018 at 5:15:26 PM UTC-8, jfitch wrote:
I tried updating my PowerFlarm to 6.42, expires in 11/19. It has 6.40 now, expires 2/19. It persistently does not update. The log file says it found the firmware file, confirmed its applicability, copies it to memory. But subsequently it comes up reporting 6.40, expiring 2/19. It also reports this to other things it talks to.

Anybody having this problem, and any suggestions?

There do seem to be some unexplained lines in the log:

00014.420 INFO Initiating non-interactive firmware update: force_adsb=0, force_pf=0...
00014.421 INFO Minimum F/W version for this device: 2.10
00014.454 INFO Found .FW file: PF_6_4~1.FW, 2 entry/entries
00014.454 INFO FW entry: Device=flarm2, version=6.4.2, Extended=DeviceName=PowerFLARM;TruncPartNo=C11A,C1 1E,D11A,D11E,C10A,C10E,D10E,P23E,P24E,P24A,Q24E,D1 0A;ADSBFwVer=0.31
00014.464 INFO Checking for applicability...
00014.464 INFO New candidate version: 6.42
00017.950 INFO FW entry: Device=ADS-B, version=0.31, Extended=bla
00017.950 INFO Checking for applicability...
00017.951 INFO Unsuitable device: ADS-B, skipping
00017.972 INFO Found .FW file: _PF_6_~1.FW, 0 entry/entries
00017.975 INFO No more files to check
00017.975 INFO Found .FW with highest version number 6.42 in file PF_6_4~1.FW
00017.976 INFO ADS-B: current: 0.31, required: 0.31
00017.982 INFO Bytes requested/free on internal FS: 531k/1866k
00017.989 INFO Copying PF firmware from PF_6_4~1.FW...
00018.425 INFO Allowing drivers to catch up...
00018.426 INFO Done.
00018.427 INFO ADS-B: No update necessary
00018.427 INFO Renaming FW temp file
00018.430 INFO Firmware update prepared, good to restart!
00018.430 INFO Allowing drivers to catch up...

Decides one file isn't applicable but another is?