AFAIR all rfm12b’s were originally 9600, only when we moved to rfm69cw did the baud get changed to 57600 and then to 38400. And since then the later rfm12b firmware has now been changed to 38400 too since it is the same fw as the rfm69cw but with “compat” set.
I’m less sure of the current status as there are a lot of changes to the update procedure in the last month or so and there is no build guide for the current image, but prior to Oct 2018, I believe the firstboot script that auto runs when an image is first installed will assume it’s an emonpi and try to update the emonpi FW, failing to do so on a emonBase regardless of rfm 12or69.
So it is only IF the “update emonbase” button has been used that it will have updated the FW and over written the rfm12 FW with rfm69 FW (same FW but compiled with the compat setting). I strongly suspect that is the case. IIRC when the wrong FW is installed, the LED might stay on since the rfm cannot be initialised. It looks like the led is on in the picture, that could just be a fluke capture, but that combined with the error and no data, plus the updates, it’s a very strong possibility.
If that is the case you will need to ssh in and run a manual command to reflash the rfm12 FW. unless you might be able to switch branches in emoncms (to master) and maybe @TrystanLea’s new multi-button setup might allow reflashing an rfm12pi via the GUI? I’m not sure how far that’s progressed, or if it’s any easier to switch branches over manually flashing (assuming avrdude etc is still there on the oct 2018 image?)
@alunr - can you confirm if you updated via the “update emonbase” button and/or if the rfm12pi’s LED is permanently lit?
 Seems there might not be a emoncms option to update just yet (https://github.com/openenergymonitor/emonpi/tree/master/update) so it would have to be via the command line using
(I think! Ref https://github.com/openenergymonitor/RFM2Pi/blob/master/update-RFM12.sh)