I get a similar problem with 1.0.2.0 but not 1.0.1.0

When enabling from the controller with start-alias, everything looks fine, with a "result":"successful".

Checking the debug.log of the masternode I can see the correct "Got NEW Masternode entry -" line (identified by txid). Then with masternode list, I can see the correct line "ENABLED" (identified by txid).

But when I do masternode status, I get:

{
   "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
    "service" : "[::]:0",
    "status" : "Not capable masternode: Hot node, waiting for remote activation."
}

I think there is a problem with the new release.