@laurenshof @melroy it should be fixed in the next release and/or you could use the NodeInfo plugin, that should fix it immediately.